Re: [ecasound] ecasound bug, bad chainsetup or stupid user?

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] ecasound bug, bad chainsetup or stupid user?
From: Kai Vehmanen (k_AT_eca.cx)
Date: Wed Dec 10 2003 - 02:33:54 EET


On Tue, 9 Dec 2003, Eric Dantan Rzewnicki wrote:

> I'm having some trouble with a chainsetup (guitar_mix.ecs -- see
> attached).
> Everything worked fine until I added amplify effects like this:
> -ea:0 -kos:1,0,175,0.01,0
[...]
> modulated by a slow sine wave. But, when the session gets to the end
> there is a second or two of very loud noise just before the processing
> finishes. The meters in envy24control go all the way up and stay there
[...]
[...]
> I run ecasound and jackd as root with jack started like so:
> jackd -R -v -d alsa -d ice1712 -r 44100 -p 256

Try running without JACK, and use ALSA directly. If you get the same
error, try replacing ALSA with a file object (render to a wav-file). If
the nosie is still present in the file, then the problem is in the
Ecasound engine, otherwise in the JACK/ALSA/... (Ecasound) output plugins.

> 2)
> I typed "start" and everything started playing. Then I wanted to jump to
> just before the end when the noise occurs, but accidentally went too far
> with "fw 2800" (the chainsettup is limited to 907s). My machine locked
> up -- no mouse, no keyboard, couldn't switch desktops, couldn't switch
> out of X -- for 1-2 minutes. I was then kicked out of X to a console

Hmm, I guess the same test (with ALSA and with rendering to file) would
again help to pinpoint the problem cause.

With JACK, a transport change will not only affect Ecasound, but all
transport aware components in the running JACK system.

> I was able to repeat this lockup. The 2nd time things went as they did
> the first time. But, when I logged in after getting kicked out of X I
> was unable to get a gdb session going. They kept getting killed with Out
> of Memory messages. Eventually I had to reboot because my bash sessions
> and even my getty's and logins were getting killed with Out of Memory
> messages.

Also, try running without root privileges (or the "-R" option to jackd).
You might need to increase jackd timeout to keep the JACK system running
with these settings, but this helps a lot with debugging (system wont
freeze totally if errors happen... unless there's a bug in kernel
drivers).

-- 
 http://www.eca.cx
 Audio software for Linux!


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Wed Dec 10 2003 - 02:29:43 EET