From: Luc Tanguay <lucus@sympatico.ca>
To: alsa-devel@alsa-project.org
Subject: Re: porting 0.5 to 0.9 app
Date: Fri, 10 May 2002 23:11:15 -0400 [thread overview]
Message-ID: <3CDC8BD3.8010404@sympatico.ca> (raw)
In-Reply-To: 200205090405.g4945Cv27985@post2.fast.net
Paul Davis wrote:
>>I'm in the process of porting a 0.5.x app to 0.9.x. The application is
>>Soundtracker. In this GTK app, I was able to retrieve the file
>>descriptor using the 'snd_seq_file_descriptor' function. The file
>>descriptor was then used to establish a callback to process MIDI events.
>>
>
>btw, i wanted to note that this is a poor design. using a GUI event
>loop to process real-time MIDI input subjects the MIDI data to
>theoretically unbounded delays before it is processed. you should be
>handling MIDI input in its own thread, ideally. using the sequencer
>with timestamps makes things a bit better, but its still not ideal.
>
I don't think it's poor design... It's no design at all :-) Anyway
thanks for the hint. I'll see what I can do but can you explain more on
why using the seq. with timestamps would make things better. ALSA
documentation for sequencer is so thin (or I need more hours in a day)
that it is difficult to get the idea on where it is going (client,
subscription, port, event, etc.). I don't have the time to read source
code of other programs to understand how ALSA could be use in my own
project and knowing the names of every function and parameters available
in the library won't do no good.
Luc
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
prev parent reply other threads:[~2002-05-11 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 3:49 porting 0.5 to 0.9 app Luc Tanguay
2002-05-09 4:04 ` Paul Davis
2002-05-09 4:06 ` Paul Davis
2002-05-11 3:11 ` Luc Tanguay [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CDC8BD3.8010404@sympatico.ca \
--to=lucus@sympatico.ca \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.