ensure that the user is a member of the 'audio' group
following a post in the linux mint forums, add the following to '/etc/security/limits.conf'
@audio - rtprio 99
@audio - memlock unlimited
@audio - nice -19
With these settings, everything seems to be working smoothly, as far as I can tell.
]]>It seems rosegarden can use either timidity or jack for midi .
Some testing shouild clarify if both those options need the 1000 Hz time or just one of them.
NB you may want to include the number of the post the solution is listed in the first post.
]]>1 kHz or 100 Hz? I think one of those is a typo. Any chance I can convince you to capitalize Hz ? It is a personal pet peeve.
Sorry, I hadn't picked up on that typo! It is indeed 1000Hz, as Lone_Wolf points out. They also correctly point out that it is only good for MIDI accuracy, which is fine, because that's the issue I was looking to solve!
]]>https://wiki.archlinux.org/title/Profes … ime_kernel gives some more background.
Keep in mind that the timer frequency only matters for MIDI .
]]>Hope this helps anyone else having this issue.
EDIT: Corrected a typo and capitalised the 'H' in Hz
]]>This is the relevant error message from Rosegarden. (Taken from terminal because the actual window displaying it doesn't allow for selecting/copying off text.)
[WarningWidget] WarningWidget::queueMessage( "<h3>System timer resolution is too low!</h3>" , "<p>Rosegarden was unable to find a high-resolution timing source for MIDI performance.</p><p>You may be able to solve this problem by loading the RTC timer kernel module. To do this, try running <b>sudo modprobe snd-rtctimer</b> in a terminal window and then restarting Rosegarden.</p><p>Alternatively, check whether your Linux distributor provides a multimedia-optimized kernel. See the <a style=\"color:gold\" href=\"http://www.rosegardenmusic.com/wiki/low-latency_kernels\">Rosegarden website</a> for notes about this.</p>" )
I also found this, the actual log portion of the terminal output.
[AlsaDriver] setCurrentTimer(): WARNING: using system timer with only 500 Hz resolution!
Looks like the problem really is real, unfortunately
That link you posted in relation to kernel options would seem to imply that the current solution to this is to compile my own kernel, which would be less that ideal.
Thanks for your help so far
]]>The most recent mention I could find is from kernel 3.16 , http://lkml.iu.edu/hypermail/linux/kern … 03158.html
Please post the full error message you get from rosegarden, that should help to determine if those links are relevant (or a red herring)
https://how-to.fandom.com/wiki/How_to_c … sound/core
https://www.mail-archive.com/ubuntu-bug … 43684.html
https://bugs.archlinux.org/task/7313
Maybe https://bbs.archlinux.org/viewtopic.php?id=266393 helps ?
Came across that in my googling of the issue, unfortunately, it's most concerned with audio output of Rosegarden. The aur package which the OP installed that might be in relation to the kernel module no longer exists and I cannot find anything that would replace, if it even solved the issue in the first place.
Thanks anyways!
]]>Just wondering if anyone here knows the proper solution to this on Arch Linux? I'm using a realtime kernel (xanmod 5.15.12 rt) and I'm not sure what, if any, package provides something comparable to the snd-rtctimer module Rosegarden is looking for.
Thanks!
Edit: I have found the solution, look post #6
]]>