On Mon, 15 Feb 2016 09:28:09 -0500
"jonetsu@email-addr-hidden" <jonetsu@email-addr-hidden> wrote:
> This is what it gives. This is still very far away from the value of
> 80 you mentioned.
>
> PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> -6 0 5782316 2,825g 133576 S 18,9 18,4 41:52.87 mixbus-3.1.66
> -6 0 5782316 2,825g 133576 S 18,6 18,4 41:49.34 mixbus-3.1.66
> -6 0 5782316 2,825g 133576 S 18,6 18,4 41:54.50 mixbus-3.1.66
> 20 0 1223108 339364 103676 S 5,6 2,1 9:29.98 renoise
> 20 0 5782316 2,825g 133576 S 4,0 18,4 11:51.23 mixbus-3.1.66
> 9 -11 219472 90804 83556 S 2,7 0,6 5:31.81 jackd
> -6 0 5782316 2,825g 133576 S 2,0 18,4 3:50.16 mixbus-3.1.66
Are you sure that you have configured JACK to run with realtime at
priority 80? Kind of looks like you are running it at 10, which would
make your mixbus audio threads run at 5 less, that is at priority 5.
Note that top normally shows realtime thread priorities as a negative
value offset by 1 compared to what we refer to when we configure this.
-- Joakim _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Mon Feb 15 20:15:02 2016
This archive was generated by hypermail 2.1.8 : Mon Feb 15 2016 - 20:15:02 EET