> 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
> ?
I couldn't even find where this is done in the source code in 20
minutes. I have no clue, but I doubt there's a nice looking answe
On Wednesday 19 June 2013 09:55:10 D. Michael McIntyre wrote:
> >>> BTW : What is the clock source actually used by Rosegarden when (auto)
> >>> is selected ?
>
> It's complicated, technical, and I have totally forgotten every one of
> the details. The short version is Rosegarden tries to pick t
On 06/19/2013 03:45 AM, aCOSwt wrote:
> Would you mean a bug in the snd_hrtimer module ?
> I'd be grateful if you could provide more details so that I can narrow down my
> investigations.
This bug has existed for the better part of 10 years. Either the timer
works, or it freezes your entire sys
On Wednesday 19 June 2013 07:10:27 you wrote:
> On Tue, 18 Jun 2013, aCOSwt wrote:
> > ...
> > As soon as I depress the apply button after changing the midi clock
> > source from "auto" to "HR timer", my system entirely freezes and the
> > hardware reset is the only solution left.
> > ...
> It's no
On Tue, 18 Jun 2013, aCOSwt wrote:
> Hello,
>
> - Using Rosegarden 13.04
> - jackd 0.121.3 running SCHED_FIFO
> - alsa
> - Whatever linux kernel : 2.6.38 / 3.4.43 / 3.8.13
> - Whatever patchset : None / ck / CONFIG_PREEMPT_RT
> - All kernel configs with : CONFIG_SND_HRTIMER and
> CONFIG_SND_SEQ_
Hello,
- Using Rosegarden 13.04
- jackd 0.121.3 running SCHED_FIFO
- alsa
- Whatever linux kernel : 2.6.38 / 3.4.43 / 3.8.13
- Whatever patchset : None / ck / CONFIG_PREEMPT_RT
- All kernel configs with : CONFIG_SND_HRTIMER and
CONFIG_SND_SEQ_HRTIMER_DEFAULT set.
Everything audio / midi related
