Looking for a patch, or library that can help me getting this precious information when trying to put in place a low latency setup in pd:

I care mostly about:

• Deadline
• Load (AVG)
• Load (MAX)

I am currently on Windows... in Linux we have this information in Jack I think, and we know when a frame was dropped. I would like this information in pd or in Windows if there is a free software.

Cheers~

@EEight The same graph seems to be available in Bitwig for windows...... https://forum.cockos.com/showthread.php?t=213288
30 day free trial...... https://www.bitwig.com/download/

Not the same, but this portable program (run, not installed) will report dropped frames with a 1000ms deadline, current latency, and maximum latency........ so the info you are looking for..... maybe, maybe not...
DPC latency monitor.zip
Graph on my machine while scrubbing audio in Pd and Video in GEM.......

There is another... I think better.... which gives a massive amount of information also about your drivers, setup, etc. and will tell you which kernels are having trouble...... latencymon 7.31......
https://www.resplendence.com/downloads
David.

@EEight P.S. Tools like those use some data already available of course and collate it.
The universal tool is Sysinternals suite from Microsoft.
When you open procexp.exe and click on the pd process you can even see which binaries it is using and the live cpu for each one.
And so much more.......
David.

looks like a job for plugdata

Thank you, I am new to Windows, trying to fine-tune the OS as much as possible to get super low latency (under 5ms). In linux when using qJackctl, on the main window, there's an "XRuns" counter that increments each time a dropout occurs.

The number in parentheses shows the number of overrun xruns. Overruns occur when the audio buffer is not consumed quickly enough by the system, leading to a buffer overflow.

The number outside the parentheses shows the total number of underrun xruns. Underruns happen when the system fails to provide data to the buffer in time, causing a buffer underflow.

This is what I am looking for to have in Windows or directly in PD.

Well, silly me, we have the Audio I/O Error shown in the main interface! I think this is a good indicator that PD wasn't able to process the DSP fast enough. Sadly I don't think we can log that or get the information in a patch to count the number of occurence...

Checking the source, I see this commented code, would love to have this information in the patch, or at the very minimum in the console log:

if (sys_getrealtime() > nt_nextreporttime)
    {
        post("%d audio I/O error%s", nt_errorcount,
            (nt_errorcount > 1 ? "s" : ""));
        if (nt_resynccount) post("DAC/ADC sync error");
        nt_errorcount = nt_resynccount = 0;
        nt_nextreporttime = sys_getrealtime() - 5;
    }