Re: [Lmuse-developer] no midi ouput to timidity

[Robert J. <rob...@da...>]

Hi Conrad,

Comments in the text, lots of suggestions, ask again if I it's fuzzy ;-)

/Robert


On Tuesday 09 March 2004 11.15, Conrad Berh=F6rster wrote:
> Hello,
>
> can anybody explain the following output
>
> first I start jack
>
>  > jackd -d alsa&
>
> conrad@linux:~> loading driver ..
> creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|rt|32bit
> control device hw:0
> configuring for 48000Hz, period =3D 1024 frames, buffer =3D 2 periods
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
>

Jack is started, but your soundcard does not support 32 bit data so jack tr=
ies=20
other combinations, finally settling on 16 bit audio. This is how it looks =
on=20
my SB-Live card also.

no '-R' on commandline but the output of jack suggests it was started with=
=20
realtime priority anyway... perhaps the default was changed...

>
>
> than timidity
>
>  > timidity -iA -D2,8 -Os &
>
> conrad@linux:~> Requested buffer size 32768, fragment size 8192
> ALSA pcm 'default' set buffer size 32768, period size 8192 bytes
> TiMidity starting in ALSA server mode
> can't set sched_setscheduler - using normal priority
> Opening sequencer port: 128:0 128:1

Timidity is started, very large buffers.... you might consider using the=20
internal fluidsynth of muse if it is soundfonts you are using.... (not a=20
requirement, but it's what I do...)

Also, timidity is not connected to jack, which might not be what you want.

>
> and kaconnect
>
>  > kaconnect&
>
> and the sequencer
>
>  > muse &
>
> the following output will come up
>
>
> **** alsa_pcm: xrun of at least 38.356 msecs
>
>
>
> **** alsa_pcm: xrun of at least 28.603 msecs
>
>
>
> **** alsa_pcm: xrun of at least 1.392 msecs

You might have problems with realtimeness. Hmmm, MusE should probably be=20
started with '-R' to enable realtime priority.

>
> cannot read connection request from client

I'm not sure which process produces this output

> cannot complete new client connection process
nor this one.

I suggest you start the different processes in different terminals to easy=
=20
debugging.

> no JACK audio server found
muse seems to be started with a different user than jack, muse does not use=
=20
jack either....=20

> ALSA lib pcm_hw.c:1055:(snd_pcm_hw_open) open /dev/snd/pcmC0D0c failed:
> Das Ger=E4t oder die Ressource ist belegt
> ALSA: device <hw:0> open error: Das Ger=E4t oder die Ressource ist belegt

infact, muse seems to have failed to setup alsa also. Probably because jack=
=20
has already grabbed the sounddevice.

>
> ----------------------
>
> why can the connection not established.
> the sequencer had started correctly and want to send MIDI data to the
> output, but i can't hear any mididata.
> with kmid i can hear the data.

While jack is running ? Since MusE failed to contact the soundcard, that mi=
ght=20
be true for timidity also.

I suggest you try without jack and start MusE with -a (no audio, only midi)=
=2E=20
If that works you can try incorporating jack again, you need some more=20
configuring though to make softwares talk to jack.

If you are running MusE 0.6.2 it is possible you have hit a known bug that=
=20
prevented midi from going out from MusE, this was fixed in 0.6.3. In that=20
case, upgrading is a good idea.

Regards,
Robert


> and wave/cd is fine to.
>
> any idea. thanks c~
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
> _______________________________________________
> Lmuse-developer mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-developer