[LAU] Rosegarden 1.5.1 on Debian Etch - Gui doesn't appears

From: Carlos Pino <pinojazz@email-addr-hidden>
Date: Fri Nov 30 2007 - 14:35:00 EET

   Hi , I have a problem with Rosegarden 1.5.1 .

   I'm on Debian Etch , using Gnome , jackd-0.103 , qjackctl-0.2.21

     Linux debian 2.6.23.1-rt11 #1 SMP PREEMPT RT Sun Nov 11 20:32:00
EET 2007 i686 GNU/Linux .

    When launch Rosegarden the gui doesn't appears , but I can see the
connections at the Qjackctl tab . It does'n
  happens untill now , some days before everything was working fine.

     This is what the terminal says:

 
JACK tmpdir identified as [/dev/shm]
PluginFactory::instance(dssi): creating new DSSIPluginFactory
LADSPAPluginFactory::discoverPlugins - discovering plugins; path is
[/home/supertux/.dssi] [/usr/local/lib/dssi] [/usr/lib/dssi]
LADSPAPluginFactory::discoverPlugins - trace is Rosegarden 1.5.1 -
AlsaDriver - alsa-lib version 1.0.13
JACK tmpdir identified as [/dev/shm]

JackDriver::initialiseAudio - JACK sample rate = 44100Hz, buffer size = 256
JackDriver::initialiseAudio - creating disk thread
JackDriver::initialiseAudio - found 10 JACK physical outputs
JackDriver::initialiseAudio - connecting from "rosegarden:master out L"
to "alsa_pcm:playback_1"
JackDriver::initialiseAudio - connecting from "rosegarden:master out R"
to "alsa_pcm:playback_2"
JackDriver::initialiseAudio - found 12 JACK physical inputs
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_1" to
"rosegarden:record in 1 L"
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_2" to
"rosegarden:record in 1 R"
JackDriver::initialiseAudio - initialised JACK audio subsystem

  ALSA Client information:

    14,0 - (Midi Through, Midi Through Port-0) (DUPLEX)
[ctype 2, ptype 655362, cap 99]
    16,0 - (TerraTec DMX6Fire, MIDI-Front DMX6fire 0)
(DUPLEX) [ctype 2, ptype 589826, cap 127]
    16,32 - (TerraTec DMX6Fire, Wavetable DMX6fire 0) (WRITE
ONLY) [ctype 2, ptype 589826, cap 74]

CREATED OUTPUT PORT 3:out 1 - MIDI external device for device 0
Connecting my port 3 to 16:32 on initialisation
done
Creating device 0 in Play mode for connection 16:32 Wavetable DMX6fire 0
(write)
Default device name for this device is MIDI external device
CREATED OUTPUT PORT 4:out 2 - MIDI external device 2 for device 1
Connecting my port 4 to 16:0 on initialisation
done
Creating device 1 in Play mode for connection 16:0 MIDI-Front DMX6fire 0
(duplex)
Default device name for this device is MIDI external device 2
Creating device 2 in Record mode for connection 16:0 MIDI-Front DMX6fire
0 (duplex)
Default device name for this device is MIDI hardware input device
CREATED OUTPUT PORT 5:out 3 - MIDI output system device for device 3
done
Creating device 3 in Play mode for connection 14:0 Midi Through Port-0
(duplex) (not connecting)
Default device name for this device is MIDI output system device
Creating device 4 in Record mode for connection 14:0 Midi Through Port-0
(duplex) (not connecting)
Default device name for this device is MIDI input system device
AlsaDriver::setCurrentTimer((auto))
    Current timer set to "system timer" with timer checks
AlsaDriver::initialiseMidi - initialised MIDI subsystem

   Any idea?

   Thanks a lot.

  Saludos.

 -- Carlos
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Fri Nov 30 16:15:06 2007

This archive was generated by hypermail 2.1.8 : Fri Nov 30 2007 - 16:15:06 EET