samplerate~ race condition?
"Peter P." <[email protected]>
| Newsgroups | gmane.comp.multimedia.puredata.general |
|---|---|
| Message-ID | <[email protected]> |
Hi list, on Debian Linux with jackd running at 44100 it seems that [samplerate~] when [loadbang]ed will report a rate of 48000. But if this loadbang is [delay]ed by 1msec it will report the correct rate of 44100. Furthermore, sound files created via [writesf~] and [loadbang] will have a 48k sampling rate, while files created one millisecond after loadbang will have a 44k1 rate. I include a minimal working example. Is this behavior known? best, Peter --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/OYMU4KGLCG2FGLTRLJPYD36UESIDLJC6/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
writesf-samplerate-MWE.pd
(text/plain, 1.1 KB)
#N canvas 495 133 967 626 12; #X obj 584 154 samplerate~; #X obj 102 65 loadbang; #X obj 417 382 writesf~; #X obj 259 337 noise~; #X msg 491 296 open noise48k.wav \, start; #X obj 417 269 del 1000; #X msg 417 294 stop; #X obj 417 237 t b b, f 11; #X obj 103 400 writesf~; #X obj 102 281 del 1000; #X msg 102 306 stop; #X obj 102 224 t b b, f 11; #X msg 176 278 open noise44k.wav \, start; #X obj 102 193 del 1; #X obj 817 167 send pd; #X msg 817 142 dsp 1; #X obj 102 96 t b b b b, f 68; #X obj 584 179 print samplingrate at 0:; #X obj 396 155 samplerate~; #X obj 396 180 print samplingrate at 1:; #X obj 396 127 del 1; #X connect 0 0 17 0; #X connect 1 0 16 0; #X connect 3 0 2 0; #X connect 3 0 8 0; #X connect 4 0 2 0; #X connect 5 0 6 0; #X connect 6 0 2 0; #X connect 7 0 5 0; #X connect 7 1 4 0; #X connect 9 0 10 0; #X connect 10 0 8 0; #X connect 11 0 9 0; #X connect 11 1 12 0; #X connect 12 0 8 0; #X connect 13 0 11 0; #X connect 15 0 14 0; #X connect 16 0 13 0; #X connect 16 1 7 0; #X connect 16 2 0 0; #X connect 16 2 20 0; #X connect 16 3 15 0; #X connect 18 0 19 0; #X connect 20 0 18 0;