Sarge,KDE.Rosegarden und Jack (laaang ;-))

[Werner Flügel <wfluegel@fh-lausitz.de>]

Hallo,

ich versuche seit ein paar Tagen o. g. Software zum Laufen zu bringen. 
Sarge und KDE läuft ohne Probleme, Sound unter KDE geht auch (sowohl 
Systemsounds als auch CD abspielen). Nun also Rosegarden testen. Also: 
Rosegarden4 gestartet, Testfile geladen, Abspielen gestartet, kein Sound 
:( Einstellungen gecheckt (über Einstellungen/Rosegarden4 
einrichten/Sequenzereinstellungen/allgemein): "Sequenzerstatus: Midi, 
aber kein Audio"
Ähm...wieso dat denn? Statusdetails:

------vonhier------

Rosegarden 1.0 - AlsaDriver - alsa-lib version 1.0.8

JackDriver::initialiseAudio - JACK server not running

  ALSA Client information:

    64,0 - (ESS ES1938 (Solo-1) MIDI - Rawmidi 0, ESS ES1938 (Solo-1) 
MIDI)   (DUPLEX) [ctype 2, ptype 2, cap 127]
    65,0 - (OPL3 FM synth, OPL3 FM Port)  (WRITE ONLY) [ctype 2, ptype 
1030, cap 66]
    129,0 - (AlsaModularSynth, ams)  (WRITE ONLY) [ctype 1, ptype 
1048576, cap 66]
    129,1 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]
    129,2 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]

Creating device 0 in Play mode for connection 65:0 OPL3 FM Port (write)
Default device name for this device is MIDI soundcard synth
Creating device 1 in Play mode for connection 64:0 ESS ES1938 (Solo-1) 
MIDI (duplex)
Default device name for this device is MIDI external device
Creating device 2 in Record mode for connection 64:0 ESS ES1938 (Solo-1) 
MIDI (duplex)
Default device name for this device is MIDI hardware input device
Creating device 3 in Play mode for connection 129:0 ams (write)
Default device name for this device is MIDI software device
Creating device 4 in Record mode for connection 129:1 ams (read)
Default device name for this device is MIDI software input
Creating device 5 in Record mode for connection 129:2 ams (read)
Default device name for this device is MIDI software input 2
    Current timer set to "system timer"
    WARNING: using system timer with only 100Hz resolution!
AlsaDriver::initialiseMidi -  initialised MIDI subsystem

    Current timer set to "system timer"
    WARNING: using system timer with only 100Hz resolution!
AlsaDriver::setRecordDevice - successfully subscribed device 2 as record 
port

  ALSA Client information:

    64,0 - (ESS ES1938 (Solo-1) MIDI - Rawmidi 0, ESS ES1938 (Solo-1) 
MIDI)   (DUPLEX) [ctype 2, ptype 2, cap 127]
    65,0 - (OPL3 FM synth, OPL3 FM Port)  (WRITE ONLY) [ctype 2, ptype 
1030, cap 66]
    129,0 - (AlsaModularSynth, ams)  (WRITE ONLY) [ctype 1, ptype 
1048576, cap 66]
    129,1 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]
    129,2 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]

AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setPlausibleConnection: connection like 65:0 OPL3 FM Port 
(write) requested for device 0
AlsaDriver::setPlausibleConnection: exact match available
AlsaDriver::setPlausibleConnection: connection like 64:0 ESS ES1938 
(Solo-1) MIDI (duplex) requested for device 1
AlsaDriver::setPlausibleConnection: exact match available
AlsaDriver::setPlausibleConnection: connection like 129:0 ams (write) 
requested for device 3
AlsaDriver::setPlausibleConnection: exact match available
Creating device 6 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 1
AlsaDriver::setPlausibleConnection: connection like 130:0 ams (write) 
requested for device 6
AlsaDriver::setPlausibleConnection: nothing suitable available
Creating device 7 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 2
Creating device 8 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 3
Creating device 9 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 4
Creating device 10 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 5
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed

------bishier-----

Sagt mir alles nix rechtes...aber da war mal was mit Jack... also auf 
der Karte "Start" das Häkchen gesetzt bei "Jack mit Rosegarden starten"

- Rosegarden4 neu gestartet, Statusdetails:

------vonhier------

Rosegarden 1.0 - AlsaDriver - alsa-lib version 1.0.8

JackDriver::initialiseAudio - JACK server not running

  ALSA Client information:

    64,0 - (ESS ES1938 (Solo-1) MIDI - Rawmidi 0, ESS ES1938 (Solo-1) 
MIDI)   (DUPLEX) [ctype 2, ptype 2, cap 127]
    65,0 - (OPL3 FM synth, OPL3 FM Port)  (WRITE ONLY) [ctype 2, ptype 
1030, cap 66]
    129,0 - (AlsaModularSynth, ams)  (WRITE ONLY) [ctype 1, ptype 
1048576, cap 66]
    129,1 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]
    129,2 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]

Creating device 0 in Play mode for connection 65:0 OPL3 FM Port (write)
Default device name for this device is MIDI soundcard synth
Creating device 1 in Play mode for connection 64:0 ESS ES1938 (Solo-1) 
MIDI (duplex)
Default device name for this device is MIDI external device
Creating device 2 in Record mode for connection 64:0 ESS ES1938 (Solo-1) 
MIDI (duplex)
Default device name for this device is MIDI hardware input device
Creating device 3 in Play mode for connection 129:0 ams (write)
Default device name for this device is MIDI software device
Creating device 4 in Record mode for connection 129:1 ams (read)
Default device name for this device is MIDI software input
Creating device 5 in Record mode for connection 129:2 ams (read)
Default device name for this device is MIDI software input 2
    Current timer set to "system timer"
    WARNING: using system timer with only 100Hz resolution!
AlsaDriver::initialiseMidi -  initialised MIDI subsystem

    Current timer set to "system timer"
    WARNING: using system timer with only 100Hz resolution!
AlsaDriver::setRecordDevice - successfully subscribed device 2 as record 
port

  ALSA Client information:

    64,0 - (ESS ES1938 (Solo-1) MIDI - Rawmidi 0, ESS ES1938 (Solo-1) 
MIDI)   (DUPLEX) [ctype 2, ptype 2, cap 127]
    65,0 - (OPL3 FM synth, OPL3 FM Port)  (WRITE ONLY) [ctype 2, ptype 
1030, cap 66]
    129,0 - (AlsaModularSynth, ams)  (WRITE ONLY) [ctype 1, ptype 
1048576, cap 66]
    129,1 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]
    129,2 - (AlsaModularSynth, ams)  (READ ONLY) [ctype 1, ptype 
1048576, cap 33]

AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setPlausibleConnection: connection like 64:0 M Audio 
Audiophile 24/96 MIDI (duplex) requested for device 0
AlsaDriver::setPlausibleConnection: nothing suitable available
AlsaDriver::setPlausibleConnection: connection like 65:0 Emu10k1 Port 0 
(write) requested for device 0
AlsaDriver::setPlausibleConnection: nothing suitable available
AlsaDriver::setPlausibleConnection: connection like 65:1 Emu10k1 Port 1 
(write) requested for device 1
AlsaDriver::setPlausibleConnection: nothing suitable available
AlsaDriver::setPlausibleConnection: connection like 65:2 Emu10k1 Port 2 
(write) requested for device 3
AlsaDriver::setPlausibleConnection: nothing suitable available
Creating device 6 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 1
AlsaDriver::setPlausibleConnection: connection like 65:3 Emu10k1 Port 3 
(write) requested for device 6
AlsaDriver::setPlausibleConnection: nothing suitable available
Creating device 7 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 2
AlsaDriver::setPlausibleConnection: connection like 65:1 Emu10k1 Port 1 
(write) requested for device 7
AlsaDriver::setPlausibleConnection: nothing suitable available
Creating device 8 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 3
AlsaDriver::setPlausibleConnection: connection like 129:0 KAMix: qamix 
(write) requested for device 8
AlsaDriver::setPlausibleConnection: nothing suitable available
Creating device 9 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 4
Creating device 10 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 5
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed
AlsaDriver::setRecordDevice - attempting to subscribe (2) already subscribed

------bishier-----

Hm, sieht nicht viel besser aus (wieso eigentlich "Audio Audiophile 
24/96" und "Emu10k1"??? Meine Karte ist ne Terratec 128 PCI, also ESS 
ES1938 (Solo-1)!), achja: und immer noch kein Sound! Da war doch mal was 
mit jackd... also qjackctl gestartet und auf "Starten" geklickt.
Zum Glück ist JACK gesprächig, seine Messages:

------vonhier------

21:31:29.484 Statistics reset.
21:31:29.492 Startup script...
21:31:29.493 artsshell -q terminate
21:31:29.551 MIDI connection graph change.
sound server terminated
21:31:29.854 Startup script terminated successfully.
21:31:29.855 JACK is starting...
21:31:29.855 /usr/bin/jackd -v -R -dalsa -dhw:0 -r48000 -p1024 -n2 -D 
-C/dev/dsp -P/dev/dsp
21:31:29.857 JACK was started with PID=2919 (0xb67).
getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_dummy.so
getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_alsa.so
getting driver descriptor from /usr/lib/libjack0.80.0-0/jack_oss.so
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
registered builtin port type 32 bit float mono audio
required capabilities not available
capabilities: =
cannot lock down memory for jackd (Operation not permitted)
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x80579c0 fd = -1
apparent rate = 48000
creating alsa driver ... 
/dev/dsp|/dev/dsp|1024|2|48000|0|0|nomon|swmeter|-|32bit
ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp
ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to 
capture-only mode
cannot load driver module alsa
21:31:29.874 JACK was stopped successfully.
21:31:30.063 MIDI connection change.
21:31:32.156 Could not connect to JACK server as client.

------bishier-----

Da fällt zunächst mal auf: "cannot lock down memory for jackd (Operation 
not permitted)" Kann ja sein, schließlich arbeite ich als normaler User, 
nicht als root. Wenn ich jackd schon beim Systemstart lade, gibbet dann 
Probleme mit artsd?
Und wenn ich qjackctl aus nem root-xterm starte, gibbet "qjackctl: 
cannot connect to X server"! Muß ich etwa beim sequenzern im KDE als 
root... mir gruselts... oder hilft "setuid root"?

Und dann: "ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM 
/dev/dsp"? Wieso? /dev/dsp existiert doch:

werner@k6-500:~$ ls -l /dev/dsp
lrwxrwxrwx  1 root root 9 2004-11-07 17:08 /dev/dsp -> /dev/dsp0
werner@k6-500:~$ ls -l /dev/dsp0
crw-rw----  1 root audio 14, 3 2004-11-07 17:08 /dev/dsp0
werner@k6-500:~$

Ja, zur Gruppe audio gehöre ich.

Resümee: "Could not connect to JACK server as client." Und dazu ist 
Google (und leider auch das Archiv der Mailingliste) nicht sehr 
gesprächig :(

System: Dual-Athlon 2600+, 512MB, Kernel 2.4.24 mit ALSA-Modulen, Debian 
Sarge
Soundsystem im KDE-Kontrollzentrum: Soundserver mit Echtzeitprio 
aktiviert, autom. Abschalten nach 5s Inaktivität, für Audio-Hardware ist 
sowohl "autom. feststellen" als auch "ALSA" getestet, kein Unterschied, 
für MIDI-Gerät sowohl "ESS ES1938 (SOLO-1)" als auch "OPL-3 FM Synth", 
"ROSEGARDEN input" als auch "ALSA Modular Synth" getestet, kein 
Unterschied.
Hat wer KDE, MIDI und Rosegarden am Laufen und kann mir mit den 
korrekten Einstellungen (bzw. Tips) aushelfen?

Gruß & Dank

--
mfG.

W.Flügel
HRZ FH Lausitz
Tel. 03573 / 85382