View previous topic :: View next topic |
Author |
Message |
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Mon Jun 17, 2013 2:00 pm Post subject: rosegarden + hr timer => System freezes |
|
|
OK don't try just in order to (un)confirm, your system is likely to freeze completely and the hard reset be the only solution.
OK, google tells me that this has been occurring in ancient times but that the problem was fixed.
But here, I'm running rosegarden 13.04 under a 3.8.13 kernel and... the system completely freezes as soon as I select the hr timer as midi clock source.
(No trace available nowhere of course)
_________________
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Mon Jun 17, 2013 3:35 pm Post subject: |
|
|
audiodef wrote: | Are you using a real-time kernel configured with a kernel seed? |
Well, this problem basically occurs whatever the kernel I use from gentoo portage. gs/ck/rt
Thank you for the hints.
I do not think my config differs greatly from yours on the most important points. I get the snd_hrtimer statically built though.
audiodef wrote: | Also make sure your system is configured with the correct groups and settings... I assume before running Rosegarden you've successfully started JACK, with or without Qjackctl. |
Well, basically, everything jack / midi / audio related is working as expected, even Qtractor.
Rosegarden works troublefree with (auto) as preferred clock source.
I am just not perfectly happy with the midi events sync I can achieve with Rosegarden and thought that selecting the hr timer option would help but then... everything freezes immediately...
EDIT : BTW, I wonder what actual clock source is associated with rosegarden's auto setting being said that I get the Use HR-timer as default sequencer timer kernel config option set. _________________
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Tue Jun 18, 2013 2:43 pm Post subject: |
|
|
I was wondering if maybe Rosegarden's graphics settings were involved, but I saw no difference in this case between "fast" and "safe". But I did notice that there's some lag when starting JACK with ALSA (I normally start it with firewire). There was some delay on startup, and then a short freeze every time I highlighted a new track. So I'm wondering if ALSA is the real culprit here.
Do you have any FFADO-compatible firewire devices you can use? If so, start JACK with firewire and see if Rosegarden has the same problem. Or really, try to start JACK with anything other than ALSA (maybe dummy?). _________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Tue Jun 18, 2013 4:06 pm Post subject: |
|
|
audiodef wrote: | I was wondering if maybe Rosegarden's graphics settings were involved, but I saw no difference in this case between "fast" and "safe". But I did notice that there's some lag when starting JACK with ALSA (I normally start it with firewire). There was some delay on startup, and then a short freeze every time I highlighted a new track. So I'm wondering if ALSA is the real culprit here. |
Hmmm... as far as I understand, you do not manage to reproduce my problem.
Could you please confirm that your implementation of rosegarden is actually using the hr-timer as midi clock source ? (Edit/configure/MIDI/Clock)
And... moreover, which clock source does your jackd implementation uses for midi ? And what did you select associated with the -X parameter in jackd ?
===============
EDIT : OK! Thank you, audiodef, for your help but you can stop your efforts as I have had some kind of answer on the rosegarden's mailing list.
In short : The problem is with the snd_hrtimer module. Either it works, or it freezes the system entirely at once and things have been so for the last 10 years. _________________
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Wed Jun 19, 2013 2:21 pm Post subject: |
|
|
aCOSwt wrote: |
In short : The problem is with the snd_hrtimer module. Either it works, or it freezes the system entirely at once and things have been so for the last 10 years. |
Hm... there's got to be SOME combination of settings that triggers this. I seem to have avoided whatever combination that might be in Gentoo Studio. If you're really stuck, and really need a working Rosegarden on Gentoo with hrtimer, you could use the Gentoo Studio stage 4 tarball and let me know if that solves your problem (since Rosegarden, JACK and everything but some kernel drivers for your specific machine have already been configured and it works). _________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
_______0 Guru
Joined: 15 Oct 2012 Posts: 521
|
Posted: Sun Jun 23, 2013 1:44 pm Post subject: |
|
|
out of curiosity how do you determine which timer is MIDI using? I noticed snd_hrtimer wasn't loaded here. |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Sun Jun 23, 2013 3:43 pm Post subject: |
|
|
_______0 wrote: | out of curiosity how do you determine which timer is MIDI using? |
As a matter of fact... this was exactly... part of my question :
aCOSwt on the mailing list wrote: | Is there a simple mean for the user (I mean without implementing some trace in the source code) to know which timer has actually been selected by rosegarden? |
And the answer I got from a dev :
Quote: | I have no clue, but I doubt there's a nice looking answer to this. |
_________________
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Mon Jun 24, 2013 3:10 pm Post subject: |
|
|
There's an option to switch the timer from "auto" to your selected preference. If that's what you're referring to, perhaps you don't have the correct module loaded and that's why it freezes. The easiest way to know whether the module is loaded is to verify that your kernel is configured for it and to modprobe the module. Of course, if it's in your /etc/conf.d/modules, it should be loaded already. If it's compiled into the kernel, try configuring it as a loadable module instead. I've been told by devs that it shouldn't matter, but the practical reality is I've found some things more stable as loadable modules than compiled into the kernel. _________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
Cybernetic1 n00b
Joined: 07 Apr 2020 Posts: 1
|
Posted: Tue Apr 07, 2020 9:16 am Post subject: |
|
|
If RoseGarden freezes, you can edit the file
Code: | ~/.config/rosegardenmusic/Rosegarden.conf |
Change the line "timer=HR timer" back to "timer=auto"
Then it won't freeze and you can try other options. |
|
Back to top |
|
|
|