10 Mar
2004
10 Mar
'04
4:40 a.m.
On ons, 2004-03-10 at 09:08, Steve Harris wrote:
On Wed, Mar 10, 2004 at 07:49:29 +0100, Jens M
Andreasen wrote:
Well, the documentation only mentions "a small amount of time". If the
host thinks that 1024 samples at 44.1 is "a small amount", then whatever
happened in the midistream won't take effect before the next request for
samples. I think it is not my problem?
On mån, 2004-03-08 at 10:00, Steve Harris wrote:
But it causes a lot more. You need some way to guarantee that the timing
is consistent between plugins and host to make sure that automation
effects are deterministic.
In LADSPA the host handles MIDI mapping.
Would it be OK if my plugin listened to a named pipe instead of the
default /dev/midi? If so, then a sequencer could write a midistream to
the pipe just like any other midi device, and the problem ceases to
exist. In practice, having the host do the MIDI binding is
good, it means you get
a consistent interface across all plugins and makes things a lot simpler.
If your host of choice doesnt support MIDI mapping then petition the
author :)
- Steve
Uhmm .. So where do I find the midistream?
/jens