Re: [linux-audio-user] Newbie Linux user Struggling with MIDI

Last Sunday 31 July 2005 00:51, PhilJackson was like:
> Christoph Eckert wrote:
> >>Ok thanks. I fired up qjackctl and haven't the foggiest
> >>idea what to do with it.
> >
> >Audio applications which use MIDI via the ALSA sequencer or
> >even JACK do usually not autoconnect to [MIDI/AUDIO][In/Out].
> >You have to do it manually.
> >
> >In Qjackctl klick on connect and connect your applications and
> >hardware ports as desired, regardless if it was MIDI or
> >audio.
> >
> >
> >Best regards
> >
> >
> > ce
> >
> >Thanks. I clicked "connect" and am looking at the MIDI tab.On one side is
>
> Readable Clients /output on the other Writeable Clients /input
> Under both are two "ports"
> one with a plugin port icon -64:CS46XX
> one that looks like the plug on a cable 0:CS64XX
>
> Which is which?

64 should drive the SoundCanvas. This is usually the external MIDI port.

> Under the Audio tab it is simply blank
>
> When I click "Start" I get the message below -don't know what they mean,
> but it doesn't look good...
>
> Phil J.
> Error messages from Jack below:
>
> 18:28:24.341 Statistics reset.
> 18:28:25.558 MIDI connection graph change.
> 18:28:25.565 MIDI connection change.
> 18:34:12.073 MIDI connection change.
> 18:34:17.703 MIDI connection change.
> 18:34:42.249 Startup script...
> 18:34:42.254 artsshell -q terminate
> 18:34:43.299 Startup script terminated with exit status=256.
> 18:34:43.436 JACK is starting...
> 18:34:43.438 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
> 18:34:43.473 JACK was started with PID=7800 (0x1e78).
> jackd 0.99.0
> Copyright 2001-2003 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> loading driver ..
> apparent rate = 48000
> creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
> control device hw:0
> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> ALSA: cannot set period size to 1024 frames for capture
> ALSA: cannot configure capture channel
> cannot load driver module alsa
> 18:34:43.998 JACK was stopped successfully.
> 18:34:45.500 Could not connect to JACK server as client.
> 18:36:16.931 Startup script...
> 18:36:16.941 artsshell -q terminate
> 18:36:17.460 Startup script terminated with exit status=256.
> 18:36:17.464 JACK is starting...
> 18:36:17.466 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
> 18:36:17.484 JACK was started with PID=7803 (0x1e7b).
> jackd 0.99.0
> Copyright 2001-2003 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> loading driver ..
> apparent rate = 48000
> creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
> control device hw:0
> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> ALSA: cannot set period size to 1024 frames for capture
> ALSA: cannot configure capture channel
> cannot load driver module alsa
> 18:36:17.686 JACK was stopped successfully.
> 18:36:19.532 Could not connect to JACK server as client.

This means ALSA isn't configured properly. Try alsaconf.

cheers,

tim hall
http://glastonburymusic.org.uk
Received on Sun Jul 31 16:15:07 2005