|
From: Steve H. <S.W...@ec...> - 2003-01-20 23:46:26
|
On Mon, Jan 20, 2003 at 11:52:47 +0100, David Olofson wrote: > > > - Linux still breaks JACK out-of-process latency... :-( > > Seems to be a scheduler issue, but I don't have first hand experience > with this. I don't know if it's been fixed yet, but Paul have been > complaining about it every now and then. Oh, I see, thats not specific to JACK, it affects all SCHED_FIFO programs. The intention is that linuxsampler wil be inprocess anyway. > > - Each point in the overall graph will be a different > > instance > > Yes, but that applies to JACK and applications as well. I don't see > what you mean. No, beacuse a JACK application can export ports to all other jack applications, whereas a plugin is only available to its host app. > > - Making the threading work well with all hosts will be > > hard > > Possibly. Do you have some details on this? (Conflicts with what the > host is doing or whatever.) Nothing concrete, but I can imagine how hard it would be to get it working reliably in LADSPA and this isnt really any different. > > - No direct JACK i/o > > Why would you need that if you're a XAP plugin? It's the host that > decides where your audio ports are connected. That's one of the few > really significant differences between JACK and LADSPA, XAP, VST etc. The JACK audio routing system is just more powerful than plugin hosting. Obviously you need that too, but for something as potentially sophisticated as a sampler I'd really want it available drectly to JACK. More layers of overheard and shims would kinda defeat the point. - Steve |