<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - pulseaudio jack modules drop samples on low fragment sizes" href="https://bugs.freedesktop.org/show_bug.cgi?id=92148#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - pulseaudio jack modules drop samples on low fragment sizes" href="https://bugs.freedesktop.org/show_bug.cgi?id=92148">bug 92148</a> from <a class="email" href="mailto:superquad.vortex2@gmail.com" title="Raymond <superquad.vortex2@gmail.com>"> Raymond</a> <pre>(In reply to Alexander E. Patrakov from <a href="show_bug.cgi?id=92148#c2">comment #2</a>) > Raymond, let's not reiterate over the relationship between the sink's > minimum wakeup period and the client latency. PulseAudio cannot reject this > case, because it can also appear because of stream-moving in pavucontrol. > Please see <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - early request mode breaks with high latency sink" href="show_bug.cgi?id=66962">bug 66962</a> (wrongly closed as fixed, even though it is only worked > around). The long-term plan in description there (about timer-based > emulation) is spot on, and that suggestion has never been implemented. <a href="http://jackaudio.org/files/docs/html/index.html">http://jackaudio.org/files/docs/html/index.html</a> calling jack_client_open() to connect to the JACK server. registering "ports" to enable data to be moved to and from your application. registering a "process callback" which will be called at the right time by the JACK server. telling JACK that your application is ready to start processing data. it is JACK server call jack_process callback and pulseaudio server have to supply enough frames</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>