Hi,
If I go to media/audio setting and try to set a delay higher than 50ms, I get a lot of "tried but couldn't sync A/D/A" messages and then "audio I/O stuck... closing".
This is on Ubuntu 10.04 with Pd Extended 0.42.5, with ALSA.
In windows I used to increase the delay when I had cpu-heavy patches (or when some other cpu-heavy application had to run on the same computer) in order to have a bigger buffer and less dropouts and it used to work seamlessly. I got more latency, obviously, but it worked better (less dropouts), not worse.
Why do I get these errors, what do they mean and why should a higher delay value trigger them???
thanks m.
Do you really need plain alsa by any reason?
If not, switch to jack audio server, then in jack you can configure the desired "latency parameter" easily (use qjackctl as GUI frontend for jackd itself). Then configure a higher latency that will ultimately free more CPU cycles and glitch less.
At least, its the way I work =P
Best regards, Pedro Lopes
On Sat, Oct 2, 2010 at 6:32 PM, Matteo Sisti Sette < matteosistisette@gmail.com> wrote:
Hi,
If I go to media/audio setting and try to set a delay higher than 50ms, I get a lot of "tried but couldn't sync A/D/A" messages and then "audio I/O stuck... closing".
This is on Ubuntu 10.04 with Pd Extended 0.42.5, with ALSA.
In windows I used to increase the delay when I had cpu-heavy patches (or when some other cpu-heavy application had to run on the same computer) in order to have a bigger buffer and less dropouts and it used to work seamlessly. I got more latency, obviously, but it worked better (less dropouts), not worse.
Why do I get these errors, what do they mean and why should a higher delay value trigger them???
thanks m.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Matteo Sisti Sette -
Pedro Lopes