Hi, This drives me crazy.
I'm trying PD 0.42-4 on Windows Vista. Always used XP before.
Logical time runs 50% slower than real time, i.e. 1000 logical millisecond pass in approximately 1500 real milliseconds. Yet there is no abnormal CPU consumption.
Try the attached patch. On any normal Windows XP machine I test it on, the number box will increase one unit every one second.
On my laptop with Windows Vista, which is a Core Duo T9300, it increments every 1.5 seconds approximately.
I haven't tested yet what happens with signals.
Any ideas?????
Thanks m.
#N canvas 321 345 584 396 12; #X obj 233 67 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1; #X obj 233 128 metro 1000; #X obj 229 174 timer; #X floatatom 235 258 5 0 0 0 - - -; #X obj 228 204 / 1000; #X obj 231 94 t f f; #X obj 124 139 select 1; #X connect 0 0 5 0; #X connect 1 0 2 1; #X connect 2 0 4 0; #X connect 4 0 3 0; #X connect 5 0 1 0; #X connect 5 1 6 0; #X connect 6 0 2 0;
i think, the samplingrate, that pd thinks it is using and the one that it is actually using, are differnt.
try an [osc~ 440], it will sound like a d.
can't tell, what is causing that confusion. check your soundcard settings. 1.5 could be related to 32kHz (real) <-> 48kHz (imaginary) confusion.
roman
On Wed, 2009-04-08 at 21:09 +0200, Matteo Sisti Sette wrote:
Hi, This drives me crazy.
I'm trying PD 0.42-4 on Windows Vista. Always used XP before.
Logical time runs 50% slower than real time, i.e. 1000 logical millisecond pass in approximately 1500 real milliseconds. Yet there is no abnormal CPU consumption.
Try the attached patch. On any normal Windows XP machine I test it on, the number box will increase one unit every one second.
On my laptop with Windows Vista, which is a Core Duo T9300, it increments every 1.5 seconds approximately.
I haven't tested yet what happens with signals.
Any ideas?????
Thanks m. plain text document attachment (test_time.pd) #N canvas 321 345 584 396 12; #X obj 233 67 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1; #X obj 233 128 metro 1000; #X obj 229 174 timer; #X floatatom 235 258 5 0 0 0 - - -; #X obj 228 204 / 1000; #X obj 231 94 t f f; #X obj 124 139 select 1; #X connect 0 0 5 0; #X connect 1 0 2 1; #X connect 2 0 4 0; #X connect 4 0 3 0; #X connect 5 0 1 0; #X connect 5 1 6 0; #X connect 6 0 2 0; _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Weird, weird weird, but solved it seems.
Roman Haefeli escribió:
i think, the samplingrate, that pd thinks it is using and the one that it is actually using, are differnt. try an [osc~ 440], it will sound like a d.
First I tried by using -noaudio and the timing issue disappeared, suggesting the diagnostic made by Roman was correct.
Then I switched to ASIO mode and the timing issue disappeared. I don't have absolute ear nor a diapason (nor any tuned musical instrument at home), but the tone in "test Audio and Midi" sounds exactly equal to the one in my older computer with XP which I know to be a reliable reference.
Also, with ASIO I was able to use the default 70ms latency settings without glitches, while in default MMIO mode I had to use 200ms or so.
Now the WEIRD WEIRD thing is that I switched back to MMIO mode, and now it still works fine, the timing is still correct.
I never made any "save all setting", so I restarted the computer (Windows Vista, the one previously presenting the issue), I opened PD with its default settings (MMIO) and opened the time test patch, changed only the latency setting to 200 in order to avoid glitches, and everything still works fine, with correct timing and correct pitch. Even changing sampling rate to different values, everything works as expected. In MMIO mode. And of course if I switch to ASIO it also works fine (and with lower latency).
I assure you that when I wrote I had tested the issue more than once and also after restarting the computer at least once.
I can only guess that the simultaneous use of some other application accessing the soundcard (IExplorer through Flash or Silverlight plugins, quicktime player, winamp, etc) may have messed something up, and probably even if I tested more than once even restarting the computer, I always had one of such applications running (often I listen to music or see stream TV programs and then leave winamp or the browser open and minimized and idle without closing it - bad habits).
So the problem seems gone and seems to be related to some sound card driver mess, possibly not related to any PD bug.
Thank Roman for the suggestions.
Bye m.
Weird, weird weird, but solved it seems.
Roman Haefeli escribió:
i think, the samplingrate, that pd thinks it is using and the one that it is actually using, are differnt. try an [osc~ 440], it will sound like a d.
First I tried by using -noaudio and the timing issue disappeared, suggesting the diagnostic made by Roman was correct.
Then I switched to ASIO mode and the timing issue disappeared. I don't have absolute ear nor a diapason (nor any tuned musical instrument at home), but the tone in "test Audio and Midi" sounds exactly equal to the one in my older computer with XP which I know to be a reliable reference.
Also, with ASIO I was able to use the default 70ms latency settings without glitches, while in default MMIO mode I had to use 200ms or so.
Now the WEIRD WEIRD thing is that I switched back to MMIO mode, and now it still works fine, the timing is still correct.
I never made any "save all setting", so I restarted the computer (Windows Vista, the one previously presenting the issue), I opened PD with its default settings (MMIO) and opened the time test patch, changed only the latency setting to 200 in order to avoid glitches, and everything still works fine, with correct timing and correct pitch. Even changing sampling rate to different values, everything works as expected. In MMIO mode. And of course if I switch to ASIO it also works fine (and with lower latency).
I assure you that when I wrote I had tested the issue more than once and also after restarting the computer at least once.
I can only guess that the simultaneous use of some other application accessing the soundcard (IExplorer through Flash or Silverlight plugins, quicktime player, winamp, etc) may have messed something up, and probably even if I tested more than once even restarting the computer, I always had one of such applications running (often I listen to music or see stream TV programs and then leave winamp or the browser open and minimized and idle without closing it - bad habits).
So the problem seems gone and seems to be related to some sound card driver mess, possibly not related to any PD bug.
Thank Roman for the suggestions.
Bye m.
-
Matteo Sisti Sette -
Roman Haefeli