Re: [ecasound] Problems with chains

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] Problems with chains
From: Kai Vehmanen (
Date: Wed Sep 13 2000 - 21:20:01 EEST

On Wed, 13 Sep 2000, lee johnson wrote:

>> connected to /dev/dsp... have you tried replacing all mentions of
>> "/dev/dsp" with "null"? If this works, then the problem is with your
> okay her is output of it.......assuming my usage of null was correct
> the whole process hung OS completely......mouse did not respond for
> several minutes and HD was sent spinning staying busy.......?

Ah, you used -r. You should always be careful with this switch. When an
application runs with realtime-scheduling, it basicly can eat up _all_
resources. So it can hung up your machine completely. So in normal use,
you should first try your setup without -r, and if it works (and you need
the realtime behaviour), then with -r. This affects all Linux apps running
with rt-scheduling enabled. This is also the reason, why -r requires root

In this specific case your machine hangs because "null" is a
superfast input/output device (well, it doesn't do anything). Because of
this, ecasound doesn't need to keep any pauses (= give other apps the
possibility to run), and it just keeps on processing.

> BUT I didn't get any does this mean that its the driver
> and anyone have best guess how to correct and
> what's causing it?

Btw; do you have multiple dsp devices in your /dev directory -
/dev/dsp0, /dev/dsp1, etc? If you have, try using them, one for input and
one for output. If your drivers don't support multi-open, specifying
/dev/dsp both as input and output will not work.

 . ... [ audio software for linux ] /\ . 
 . ... [ aivastus net radio ] /\ . 
 . [ my armchair-tunes mp3/ra/wav ]

-- To unsubscribe send message 'unsubscribe' in the body of the message to <>.

New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Wed Sep 13 2000 - 21:58:45 EEST