Re: [Qtractor-devel] HR timer

[Ralf M. <ral...@al...>]

Rui Nuno Capela wrote:
> On 12/26/2009 12:29 AM, Ralf Mardorf wrote:
>   
>> Rui Nuno Capela wrote:
>>     
>>> On 12/25/2009 07:36 PM, Ralf Mardorf wrote:
>>>  
>>>       
>>>> Hi :)
>>>>
>>>> I never tried to launch Qtractor by
>>>>
>>>> $ qtractor <filename.qtr>
>>>>
>>>> maybe it's possible to restore a HR timer session this way. I'll test
>>>> this as soon as possible.
>>>>
>>>>     
>>>>         
>>> you still did not make it clear on how you know the hrtimer is not being
>>> used the second time a qtractor session is loaded.
>>>
>>> seeya
>>>   
>>>       
>> The output occurs after loading a session:
>>
>> spinymouse-sudo@64studio:~/Desktop$ qtractor
>> no message buffer overruns
>> This system has no accessible HPET device (Device or resource busy)
>>
>> How do I know that even if there's no message, the HR timer is fine when
>> running a session for the first time? Because there's less jitter.
>>     
>
> ok. check whether dmesg says something related to that.
>
> as said before, snd-hrtimer module has a bug that makes its use a
> dangerous game. on some machines whole system gets locked-up, other
> maybe more lucky. ymmv :)
>
> cheers
>   

spinymouse-sudo@64studio:~$ dmesg | grep hpet
[    0.000999] hpet clockevent registered
[    0.197086] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[    0.197090] hpet0: 4 comparators, 32-bit 14.318180 MHz counter
[    0.629275] rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
spinymouse-sudo@64studio:~$ dmesg | grep hr
[    0.819863] ACPI: Invalid passive threshold
spinymouse-sudo@64studio:~$ dmesg | grep timer
[    0.000999] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[    0.001007] Calibrating delay loop (skipped), value calculated using timer frequency.. 4200.36 BogoMIPS (lpj=2100181)
[    0.034003] Calibrating delay using timer specific routine.. 4199.73 BogoMIPS (lpj=2099868)
[    0.218664] pci 0000:00:07.0: setting latency timer to 64
[    0.618352] pcieport-driver 0000:00:07.0: setting latency timer to 64
[    1.361509] r8169 0000:02:00.0: setting latency timer to 64
spinymouse-sudo@64studio:~$


I only heard that Rosegarden should freez the system and I tested it 
with OpenOctave (quasi Rosegarden) and I also only could push the reset 
button, to be honest, I didn't try the magic keys.
This is a bug for Rosegarden/ OpenOctave. Before I used Qtractor, I used 
Rosegarden. There's  more than one reason, that I changed from this 
"finished" and potentially comfortable sequencer Rosegarden to the 
rudimentary Qtractor.

Rosegarden is crap, it has got a trillion of bugs and always it's said 
that those bugs are because of it's dependencies and not because of a 
bug for Rosegarden.

Separating dependencies from the application is nonsense.

The completely outdated OS XP is using hrtimer for years. Linux should 
be able to use it too.

I never heard that Qtractor did freez the system, when using hr timer. 
On my machine it's fine, assumed that Qtractor runs a session for the 
first time and don't need to load a file.qtr.