On Sun, Aug 18, 2002 at 05:57:40AM -0300, Juan Linietsky wrote:
> Hi! I wanted to ask, how about forcing
> an absolute timestamp for _every_ midi event?
It's not 100% clear to me wat you mean. When using the sequencer api you
already have a timestamp (either tick/clock) for every event scheduled. Midi
data captured from eg. the midi input port is timestamped upon receive IRQ.
what is missing?
> I think this would be great for softsynths,
> so they dont need to work with root/schedfifo/lowlatency
> to have a decent timing. Not allways you are willing
> to process midi at the lowest latency possible.
> I say because you dont really need all that if you
> sequence in the computer and control softsynths and maybe
> some external device.
> This way, the softsynth gets the event with the timestamp,
> gets the current time, substracts the audio delay (latency) to that
> and just mixes internally in smaller blocks processing each
> event in the right time.
agreed; this is the whole concept of providing scheduling information
(ie timestamp) with the events. One hairy bit is the handling of time based
events versus tick based events in case your sequencer needs to cope with
a variable tempo or sync to midi clock sources.
Frank
--
+---- --- -- - - - -
| Frank van de Pol -o) A-L-S-A
| [EMAIL PROTECTED] /\\ Sounds good!
| http://www.alsa-project.org _\_v
| Linux - Why use Windows if we have doors available?
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
