Re: [Protux-devel] Same Run, different error

[Luciano Giordana]

On Tuesday 24 September 2002 05:56 pm, Fabio dos Santos wrote:
> on A different try, I got this:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++
>
> bash-2.05a$ ./protux
> DEBUG : Recorder.cc::arm : recBufferSize = 4096
> DEBUG : Audio.cc::create : Creating audio : 2 channels,
> DEBUG : Audio.cc::create : 44100 Hz, 16 bits
> DEBUG : Audio.cc::create : Project : Take
> DEBUG : Audio.cc::create : Group : Take
> DEBUG : Audio.cc::create : Hardware : Take
> DEBUG : Audio.cc::create : Desc : Real Time Take
> DEBUG : Recorder.cc::th_loop : Entering REC loop thread
>

> *** Error in int MustuxDsp::open_for_play()
> Cannot open /dev/dsp for playback. ( maybe busy ? )
>
> *** Error in int Mixer::play(long long int)
> Opening DSP for PLAY failed.
>
> *** Error in int Song::toggle_play()
> Mixer engine cannot be started
>
> *** Error in int MustuxDsp::open_for_play()
> Cannot open /dev/dsp for playback. ( maybe busy ? )
>
> *** Error in int Mixer::play(long long int)
> Opening DSP for PLAY failed.

it is normal. Some other process is using the dsp. Check is artsd is running 
(should not!) or esound...

anything that uses the dsp device will cause protux to be blocked. Remember 
this is conceptual. PRotux should be the only
application using dsp at a time.


>
> *** Error in int Song::toggle_play()
> Mixer engine cannot be started
> bash-2.05a$ X Error: BadLength (poly request too large or internal Xlib

The X ERror BadLengh again.. check last email