Am Freitag, den 03.04.2009, 20:15 +0200 schrieb Fons Adriaensen: > On Fri, Apr 03, 2009 at 12:49:29PM -0500, Gabriel M. Beddingfield wrote: > > > On Fri, April 3, 2009 10:38 am, hermann meyer wrote: > > ... > > > > > Isn't it common open 2 Clients ? > > > > I don't think so. > > I can make sense to do that, but not for the purpose you > explained. > > Your process callback is called by a thread created by > the client side of the jack library. You could in theory > change its priority but I don't think you're supposed to > do that. And it would not help - in each jack cycle *all* > process callbacks have to run and to finish in time, if > they don't jack will throw out your client. > > In other words you can't delay execution of a callback. > > So if you want to delay processing MIDI, the only option > is to copy the MIDI data (via a ringbuffer or a similar > system) to a lower priority thread that you create yourself. > If you do that, you can as well do it in the same client that > handles the audio. > > Ciao,
okay, get it you are absolutly right, do the processing in one client and check for cpu useage and frame time make more sence and work like I wont to have it. thanks hermann _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
