rate my xruns: tuning assistance?

Optimize your system for ultimate performance.

Moderators: khz, MattKingUSA

merlyn
Established Member
Posts: 489
Joined: Thu Oct 11, 2018 4:13 pm

Re: rate my xruns: tuning assistance?

Postby merlyn » Thu Apr 25, 2019 4:58 pm

@ZestieBumwhig tramp and Musicteacher have good suggestions. The thread Musicteacher linked to is in-depth.

PD uses a buffer or block size of 64.

Have you tried a buffer of 192?

192 = 3 * 64 = 4 * 48

So maybe you could keep PD and your interface happy at the same time. :)

User avatar
ZestieBumwhig
Established Member
Posts: 28
Joined: Fri May 20, 2016 4:56 pm

Re: rate my xruns: tuning assistance?

Postby ZestieBumwhig » Sat Apr 27, 2019 3:04 am

Oh yeah.... Math! 192 buffer size makes PD, SuperCollider, and the interface all very happy indeed. Thank you, @merlyn... in the back of my mind, I knew I needed to remember high school, and a Lowest Common Multiple.

I wish I had better than 8ms latency, but I'll just change my settings whenever I'm in an overdubbing/DAW mood. This works as a general purpose, mucking-about default for me.

And yes, I finally implemented the suggestion about c-states from @MusicTeacher - I'd been nervous about kernel settings, not really knowing what I was doing, but the more explicit instructions from @tramp seemed comprehensible to me. So I did it, and everything's even better now.

Code: Select all

scuttlebutt@scuttlebutthost:~$ ./xruncounter
Samplerate 48000
Buffersize is 192
jack running with realtime priority
Xrun 1 at DSP load 99.215645
in complete 1 Xruns in 10257 circles
first Xrun happen at DSP load 99.215645 circle 10252

Spanner
Established Member
Posts: 67
Joined: Mon Mar 10, 2014 8:18 pm

Re: rate my xruns: tuning assistance?

Postby Spanner » Sat Apr 27, 2019 6:26 am

I posted this here: viewtopic.php?f=27&t=19268&start=60#p106031

Maybe I should have posted it here.

I have a USB interface:
USB-Audio - USB Audio CODEC
Burr-Brown from TI USB Audio CODEC at usb-0000:00:12.0-3, full speed

I was running set at:
periods = 3
buffersize = 256 (or 512)
block latency was reported by Cadence to be around 5ms (or 10ms)
I held this setting because I thought that 3 periods was somehow better or necessary for USB audio interfaces. I thought maybe I could do better.


I downloaded and compiled xruncounter (thank you tramp! et al.) and then experimented with dropping periods down to 2 and altering buffersize:

periods = 2
buffersize = 192
samplerate = 48000
block latency was reported by Cadence to be 4ms


Testing over several iterations...

./xruncounter
first Xrun happen at DSP load 97.305107 circle 17107

./xruncounter
first Xrun happen at DSP load 99.298500 circle 17164

./xruncounter
first Xrun happen at DSP load 99.975204 circle 17519

./xruncounter
first Xrun happen at DSP load 99.392029 circle 17299

./xruncounter
first Xrun happen at DSP load 99.679459 circle 17608


Next, tried buffersize = 288

periods = 2
buffersize = 288
samplerate = 48000
block latency was reported by Cadence to be 6ms


Again, testing over several iterations...

./xruncounter
first Xrun happen at DSP load 99.576996 circle 26257

./xruncounter
first Xrun happen at DSP load 99.503143 circle 26250

./xruncounter
first Xrun happen at DSP load 99.217041 circle 26227

./xruncounter
first Xrun happen at DSP load 99.275375 circle 26182

./xruncounter
first Xrun happen at DSP load 99.476608 circle 26235


It looks to me as if buffersize = 288 would be the wiser choice for me to run at.


Ideas?


Return to “System Tuning and Configuration”

Who is online

Users browsing this forum: No registered users and 3 guests