[linux-audio-user] Re: Jack and Callbacks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>
>
>>My understanding is that apps need to follow a certain model (call-back
>>base processing vs. block processing, iiuc) in order to function 
>>properly within the jack graph to meet it's low-latency and synchornous
>>execution requirements. There were some pre-existing apps that fit this
>>model and some that didn't. The authors of some of those that didn't fit
>>rewrote their apps or wrote new ones. Some other authors either didn't
>>care about jack's goals or disagreed with them and so their apps aren't
>>jackable. I don't think there are any behind the scenes political
>>maneuvers going on to keep certain apps out of the jack family.
>>    
>>
Personally, I hate programming with callbacks.
But, the callback thread has to do something really quick with each 
block, and return anyway.
It is really easy to write the main processing thread as a 'block 
processing' program, which waits on a semaphore or mutex set by the 
callback.




[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux