9 Jul
2017
9 Jul
'17
10:14 a.m.
On Sun, 9 Jul 2017 17:53:15 +0300, alex wrote:
So, what could the issue be now?
Hi,
the log and the command line output are more or less equal [1]!
Hardware limitations and/or not optimal real-time tuning might cause
this issue.
For testing purpose try
-n 3 -p 1024
this would lead to
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 3 periods
What's the output of
uname -r
and
/etc/init.d/rtirq status
Note, there are more options than using a "good" kernel and Rui's rtirq
script, but those are starting points to optimize real-time usage.
Regards,
Ralf
[1] To avoid another mistake I saved both outputs and run
diff /tmp/Unsaved\ Document\ 1 /tmp/Unsaved\ Document\ 2
as well as
meld /tmp/Unsaved\ Document\ 1 /tmp/Unsaved\ Document\ 2
;)
--
Vote for apulse!
echo $(w3m https://aur.archlinux.org/packages/apulse |grep 'Votes: ')
Votes: 84 Updated: Sun Jul 9 17:14:49 CEST 2017