Esben Stien:
> When playing, the jack code sets snd to run with realtime priority.
> Its an imorral thing to do, but it sometimes does a wonderful job of
> avoiding dropouts.
Don't know if it's related, but isn't only the audio thread supposed
to be realtime?.
Yes, correct. And thats why its imorral, it could lead to dropouts
in other audio programs running simultaniously. But since its so
effective of removing clicks in snd, its probably worth it. Setting
the jack priority to something larger than 1 would probably avoid
dropouts in other audio programs anyway.
> Well, its likely that you get the dropouts because you don't run
> realtime anymore, and that could be because of something with the
> new kernel.
All other apps run fine, but when playing something in Snd, the
computer freeze and outputs a sandstorm of noise, until it's finished
playing. It's almost totally frozen; the mouse moves 1 cm every
second, maybe;)
I don't know... Does it make a difference if you use the "-noglob -noinit"
switches?
Can you try sndplay ("make sndplay") also? That would be most useful
to find out whats causing this.
I'm now seeing messages like:
SNDLIB: Setting player to non-realtime for 2 seconds
SNDLIB: Play thread set back to realtime priority
Thats the watchdog working.
> when playing something in Snd
Strangely; snd-ls works perfect;).
Thats because snd-ls use a different play routine.
To use the old play routine instead, run
(define *rt-use-rt-player* #f)
after snd-ls has started. (please try and see what happens)
_______________________________________________
Cmdist mailing list
[email protected]
http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
