|
From: Matthias W. <mat...@in...> - 2002-11-08 22:00:38
|
On Thu, Nov 07, 2002 at 07:32:16PM +0100, Benno Senoner wrote: > > > Regarding the JACK issues that Matthias W raised: > > > I'm no JACK expert but I hope that JACK supports running a JACK client > > > directly in it's own process space as it were a plugin. > > > This would save unnecessary context switches since there would be only > > > one SCHED_FIFO process runnnig. > > > (Do the JACK ALSA I/O modules work that way ? ) > > > > Yes, but there is currently no mechanism for loading an in process client > > once the engine has started, however that is merely because the function > > hasn't been written. Both the ALSA and Solaris i/o clients are in process, > > but they are loaded when the engine starts up. > > Ok, at least the engine is designed to work that way (so I guess for > maximum performance some extensions for JACK will be required but I > assume that will not be a big problem) Having jackd loading plugins, that would also mean if a plugin crashes, it takes with it the daemon, right? matthias |