1 Nov
2004
1 Nov
'04
6:28 a.m.
Sorry for the repost - first post went a bit astray
Hello all
Just recently updated debian unstable and I am not sure if it was just
coincidence, but if an ardour session is loaded and I start rosegarden,
somewhere in the middle of initialising a session ardour gets killed. In
fact it is impossible for the two apps to coexist rosegarden always kills
ardour
Anybody else seeing this with debian
Dave
Ps anybody getting debian version of jackeq to work properly?
1 Nov
1 Nov
7:55 a.m.
On Monday 01 Nov 2004 10:52, David Mulcahy wrote:
Just recently updated debian unstable and I am not
sure if it was
just coincidence, but if an ardour session is loaded and I start
rosegarden, somewhere in the middle of initialising a session ardour
gets killed. In fact it is impossible for the two apps to coexist
rosegarden always kills ardour
Spooky. Never seen that one before, and I can't offhand think of a
reason for it.
Might as well start by looking at the stdout/stderr output from each:
run ardour from one terminal window and then "rosegardensequencer" (the
non-GUI part of Rosegarden) from another, and see what happens. If
ardour gets killed, see what it and rosegardensequencer printed out
last before that happened. Otherwise leave them both running and also
run "rosegarden --existingsequencer" from a third terminal, and see
what happens then.
Chris
10:11 a.m.
This is the output from rosegardensequencer on the first run
rosegarden (sequencer): SequencerMmapper : setting size
of /tmp/kde-davmul//rosegarden_sequencer_timing_block to 91012
rosegarden (sequencer): SequencerMmapper : mmap size : 91012 at 0xb64fd000
rosegarden (sequencer): SequencerMmapper::init()
rosegarden (sequencer): Registering with DCOP server
Rosegarden 0.9.9 - AlsaDriver - alsa-lib version 1.0.4
AudioFileReader::run()
AudioFileReader::run() done
JackDriver::initialiseAudio - JACK sample rate = 44100Hz, buffer size = 2048
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:
64,0 - (M Audio Delta 1010LT MIDI - Rawmidi 0, M Audio Delta 1010LT MIDI)
(DUPLEX) [ctype 2, ptype 2, cap 127]
129,0 - (ardour, seq) (WRITE ONLY) [ctype 1, ptype 2, cap
99]
Creating device 0 in Play mode for connection 64:0 M Audio Delta 1010LT MIDI
(duplex)
Default device name for this device is MIDI external device
Creating device 1 in Record mode for connection 64:0 M Audio Delta 1010LT MIDI
(duplex)
Default device name for this device is MIDI hardware input device
Creating device 2 in Play mode for connection 129:0 ardour: seq (write)
Default device name for this device is MIDI software device
AlsaDriver::setCurrentTimer((auto))
Current timer set to "PCM playback 0-0-0"
AlsaDriver::initialiseMidi - initialised MIDI subsystem
rosegarden (sequencer): RosegardenSequencer - started OK
AlsaDriver::reportFailure(0)
rosegarden (sequence manager): ControlBlockMmapper : Couldn't
open /tmp/kde-davmul//rosegarden_control_block
WARNING: Rosegarden::Exception: "Couldn't
open /tmp/kde-davmul//rosegarden_control_block"
and the output from ardour
finished route resort
Audio 1 master
finished route resort
Audio 1 master
finished route resort
Audio 1 master
finished route resort
Audio 1 master
finished route resort
Audio 1 master
Segmentation fault
Not sure why it cant open the tmp file permissions seem ok and all was working
well maybe something to do with kde3.3?
Dave
On Monday 01 November 2004 12:06, Chris Cannam wrote:
On Monday 01 Nov 2004 10:52, David Mulcahy wrote:
Just recently updated debian unstable and I am
not sure if it was
just coincidence, but if an ardour session is loaded and I start
rosegarden, somewhere in the middle of initialising a session ardour
gets killed. In fact it is impossible for the two apps to coexist
rosegarden always kills ardour
Spooky. Never seen that one before, and I can't offhand think of a
reason for it.
Might as well start by looking at the stdout/stderr output from each:
run ardour from one terminal window and then "rosegardensequencer" (the
non-GUI part of Rosegarden) from another, and see what happens. If
ardour gets killed, see what it and rosegardensequencer printed out
last before that happened. Otherwise leave them both running and also
run "rosegarden --existingsequencer" from a third terminal, and see
what happens then.
Chris
10:17 a.m.
On Monday 01 Nov 2004 14:35, David Mulcahy wrote:
This is the output from rosegardensequencer on the
first run
[...]
That output is actually all fine, and exactly as it should be. This
alarming-looking message:
rosegarden (sequence manager): ControlBlockMmapper :
Couldn't
open /tmp/kde-davmul//rosegarden_control_block
WARNING: Rosegarden::Exception: "Couldn't
open /tmp/kde-davmul//rosegarden_control_block"
is not in fact a problem in this situation -- it just means that the GUI
hasn't started yet, which we already know (because you didn't start the
GUI).
and the output from ardour
[...]
Segmentation fault
This doesn't look so fine. I wonder if something about the MIDI
subscription from Rosegarden is confusing Ardour. I probably have to
bow out here -- it doesn't look like the problem's in Rosegarden, and I
don't know enough about Ardour to help out any further. You could
probably do with getting a stack trace from gdb or whatever, but I'm
not sure whether you'll manage that with the Debian package of Ardour
or whether you'd have to build your own with debug symbols.
Chris
9:24 a.m.
David Mulcahy wrote:
Just recently updated debian unstable and I am not
sure if it was just
coincidence, but if an ardour session is loaded and I start rosegarden,
somewhere in the middle of initialising a session ardour gets killed. In
fact it is impossible for the two apps to coexist rosegarden always kills
ardour
Anybody else seeing this with debian
What are the respective versions of the software you are running? I am
using more or less the latest CVS versions (give or take a week) of both
on Debian Sid without the problems you describe. In fact, I was using
both just yesterday and they were both pretty solid (nothing crashed, no
xruns).
-- Brett
10:17 a.m.
Debian debs from unstable
ardour beta9.19r3
rosegarden4 0.9.9r1
I have had them both working together but i guess due to an upgrade with
either kde (3.3)or some other deps they have stop working together.
Dave
On Tuesday 02 November 2004 01:24, Them wrote:
David Mulcahy wrote:
Just recently updated debian unstable and I am
not sure if it was just
coincidence, but if an ardour session is loaded and I start rosegarden,
somewhere in the middle of initialising a session ardour gets killed. In
fact it is impossible for the two apps to coexist rosegarden always kills
ardour
Anybody else seeing this with debian
What are the respective versions of the software you are running? I am
using more or less the latest CVS versions (give or take a week) of both
on Debian Sid without the problems you describe. In fact, I was using
both just yesterday and they were both pretty solid (nothing crashed, no
xruns).
-- Brett
7126
days inactive
7126
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Chris Cannam -
David Mulcahy -
Them