Re: [linux-audio-user] Ecasound or MuSE whose the guilty ?

On Fri, Mar 18, 2005 at 11:31:23PM -0000, Dubphil wrote:
> Hello,
> I couldn't resist to re-intagrate the new version of ecasound into my setup.
> So I have running :
> - jackstart -R -dalsa -dhw:1 -r48000 -p256 -n3
> - ecasound -a:1,2,3 -i jack -a:1 -efb:500,400 -o jack -a:2 -efb:1000,600
> -o jack -a:3 -efh:1300 -o jack
> if I want to run MuSE Ecasound escape with this message :
> [...]
> - [ Controller/Batch processing finished ]
> -------------------------------------
> - [ Engine exiting ]
> -----------------------------------------------------------
> (eca-control-objects) Disconnecting chainsetup: "command-line-setup".
> (audioio_jack_manager) (audioio-jack-manager) Connection closed!
> - [ Chainsetup disconnected ]
> --------------------------------------------------
> Warning: DBC_CHECK failed - "is_prepared() != true", audioio-device.cpp, 35.
> Warning: DBC_CHECK failed - "is_prepared() != true", audioio-device.cpp, 35.
> Warning: DBC_CHECK failed - "is_prepared() != true", audioio-device.cpp, 35.
> Warning: DBC_CHECK failed - "is_prepared() != true", audioio-device.cpp, 35.
> [/]
>
> what is wrong ?

I'm not sure, but check out the jack transport related options in
ecasound's man page. My suspicion is that muse and ecasound both try to
be transport master or aren't listening to the transport stuff in a
mutually agreeable manner. I think only one of them can try to be the
master.

-- 
Eric Dantan Rzewnicki  |  Systems Administrator
Technical Operations Division  |  Radio Free Asia
2025 M Street, NW  |  Washington, DC 20036  |  202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any 
unauthorized dissemination, distribution, or copying is strictly 
prohibited. If you receive this transmission in error, please contact
network@email-addr-hidden.