ecasound fails launch lame after upgrade

Bug #296120 reported by rubing
Affects Status Importance Assigned to Milestone
ecasound2.2 (Ubuntu)

Bug Description

I use the latest version of ecasound on my server to produce a fake stereo effect on mp3 files as follows:

ecasound -i infile.mp3 -etf:8 -o outfile.mp3

This worked fine until upgrading from hardy to ibex. Now, it seems to fail when trying to launch lame. Another person filed a similar complaint on the forums. Here are the errors I get:

(audioio-mp3) Starting to encode zi.mp3 with lame.
(audioio-forked-stream) Fork child-for-write: 'lame -b 128 -s 44.10 -x -S - %f'
(eca-engine) output error - stop
(eca-engine) stopping engine operation!
(eca-engine) Signaling stop
(eca-engine) Signaling exit
(eca-engine) WARNING: An output object has raised an error! Possible causes: Out
... of disk space, permission denied, unable to launch external applications needed in
... processing, etc.

Revision history for this message
Jaguar_fr (toolinux-ubuntu) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at

I have classified this bug as a bug in ecasound,
this will subscribe the bug supervisor of this package to this bug.

For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at

Revision history for this message
Kai Vehmanen (kv2004) wrote :

This bug is caused by recent changes in 'lame' (at least 3.98 and newer are incompatible). There is a simple workaround that does not need recompilation, see the ecasound-list list mail:

Intention is to integrate a proper fix to 2.7.0 upstream release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers