On Mon, 13 Feb 2006 11:33:04 +0000, Chris Cannam wrote:
[snip]
>
.... That's why I'd like to know what you were
> actually doing (e.g. what you were trying to play) at the time.
>
> (It is perhaps possible that the calculation RG is doing to work out the CPU
> load is getting it wrong because of something to do with the non-low-latency
> kernel. Probably more likely to be just a bug though.)
>
....
>
> Chris
Tried again yesterday after checking to see what related processes were
running and axing them.
Seems I had two lots of timidity going, one I started myself and one which
the init processes start up automatically, qsynth and then trying to load
the synth plugins. So, with no timidity processes, no qsynth and just the
fluidsynth-dssi loading the soundfonts, or xsynth, everything works
beautifully.
However, and I suspect this is another issue, I cannot get sound to run
without the synth plugins. I've tried using rosegarden with just the
timidity daemon running, no sound. I've tried changing the instruments in
the studio to no effect.
Same as using qsynth.
Something I noticed is that when I go to the configure rosegarden
dialogue, it says there is no driver for the sequencer.
Here is the output of the sequencer status message: (using timidity)
Rosegarden 4-1.2.3rc3 - AlsaDriver - alsa-lib version 1.0.9
JackDriver::initialiseAudio - JACK sample rate = 48000Hz, buffer size = 2048
JackDriver::initialiseAudio - creating disk thread
JackDriver::initialiseAudio - found 6 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 2 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:
62,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype 2, cap 99]
128,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
Creating device 0 in Play mode for connection 128:0 TiMidity port 0 (write)
Default device name for this device is MIDI software device
Creating device 1 in Play mode for connection 128:1 TiMidity port 1 (write)
Default device name for this device is MIDI software device 2
Creating device 2 in Play mode for connection 128:2 TiMidity port 2 (write)
Default device name for this device is MIDI software device 3
Creating device 3 in Play mode for connection 128:3 TiMidity port 3 (write)
Default device name for this device is MIDI software device 4
Creating device 4 in Play mode for connection 62:0 Midi Through Port-0 (duplex)
(not connecting)
Default device name for this device is MIDI output system device
Creating device 5 in Record mode for connection 62:0 Midi Through Port-0
(duplex) (not connecting)
Default device name for this device is MIDI input system device
Current timer set to "system timer" with timer checks
AlsaDriver::initialiseMidi - initialised MIDI subsystem
Current timer set to "system timer"
ALSA Client information:
62,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype 2, cap 99]
128,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
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 2
AlsaDriver::setPlausibleConnection: nothing suitable available
AlsaDriver::setPlausibleConnection: connection like 65:3 Emu10k1 Port 3 (write)
requested for device 3
AlsaDriver::setPlausibleConnection: nothing suitable available
AlsaDriver::setPlausibleConnection: connection like 64:0 EMU10K1 MPU-401 (UART)
(duplex) requested for device 4
AlsaDriver::setPlausibleConnection: nothing suitable available
Creating device 8 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 1
Creating device 9 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 2
Creating device 10 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 3
Creating device 11 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 4
ALSA Client information:
62,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype 2, cap 99]
128,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
Creating device 12 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 5
Creating device 13 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 6
Creating device 14 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 7
Creating device 15 in Play mode -- no connection available
Default device name for this device is Anonymous MIDI device 8
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
ALSA Client information:
62,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype
2, ptype 2, cap 99]
128,0 - (TiMidity, TiMidity port 0) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,1 - (TiMidity, TiMidity port 1) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,2 - (TiMidity, TiMidity port 2) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
128,3 - (TiMidity, TiMidity port 3) (WRITE ONLY) [ctype 1, ptype 2,
cap 66]
AlsaDriver::setRecordDevice - 255:255 failed to subscribe device 5 as record
port
.......
I probably have issues from when I had a SBLive! card. I am happy to get
the dssi plugins going, as I have an easier time understanding what is
going on with them than the studio setup interaction with sound fonts and
soundcards etc.
Shelagh
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
