Re: [Jack-Devel] jack dsp load calculation

On 26/12/2015 14:41, Robin Gareus wrote:
> I like Nedko's idea: Allow to query all: min, average, max  over a long
> time compared to the process-cycle (think second or seconds).
>

Hmm...  I didn't get that email for some reason.  But yes - as a feature 
update, that sounds promising.  I'm just pointing out that (a) the 
averaging mechanism / hybrid approach is NOT the underlying cause of the 
problem you described - and (b) in Mixbus and Ardour, we can already 
make a solution which wouldn't need us to tinker with Jack.  i.e. the 
following strategy instead of our current one:-

       if ( the_client->got_notified_about_an_xrun() ) {
             //  We know that an xrun occurred since we last checked
             //  the CPU load - so do something to accommodate that.

             //  and then reset the notification flag
             reset_the_xrun_notification_flag ();
       } else {
             //  No xrun was encountered - so we can update normally...
             update_cpu_load ();
       }

That would be very simple to implement and I honestly think we should 
try that first, before tinkering too much with Jack.

John

1451142645.1418_0.ltw:2,a <567EADED.3040400 at tiscali dot co dot uk>