Re: [Rosegarden-user] Rosegarden(sequencer) troubles

[Karel L. <Lemaitre.Karel@Pandora.Be>]

I see. Sorry about that, her comes the terminal-output:

This is what I get when I lauch rosegarden the first time:


rosegarden: main: Showing startup logo
AudioPluginManager::fetchSampleRate - couldn't fetch sample rate
rosegarden: RosegardenGUIDoc::getMappedDevice - waiting for Sequencer to
come up
rosegarden: RosegardenGUIDoc::getMappedDevice - waiting for Sequencer to
come up
rosegarden: RosegardenGUIDoc::getMappedDevice - waiting for Sequencer to
come up
rosegarden: RosegardenGUIDoc::getMappedDevice - waiting for Sequencer to
come up
rosegarden: RosegardenGUIDoc::getMappedDevice - waiting for Sequencer to
come up
rosegarden: RosegardenGUIDoc::saveIfModified()

--> "couldn't fetch samplerate" -> Has this something to do wtih the
fact I'm using a SBlive, which has a 48000-samplerate?



And this is what I get when launching rosegarden the second time



rosegarden: main: Showing startup logo
rosegarden: RosegardenGUIDoc::getMappedDevice - devices = 4
rosegarden: RosegardenGUIDoc::getMappedDevice - i = 0
rosegarden: RosegardenGUIDoc::getMappedDevice - adding MIDI Device "72
Rawmidi 1 - MK-249C USB MIDI keyboard" id = 0
rosegarden: RosegardenGUIDoc::getMappedDevice - i = 1
rosegarden: RosegardenGUIDoc::getMappedDevice - adding MIDI Device "65
Emu10k1 WaveTable" id = 1
rosegarden: RosegardenGUIDoc::getMappedDevice - i = 2
rosegarden: RosegardenGUIDoc::getMappedDevice - adding MIDI Device "64
Rawmidi 0 - EMU10K1 MPU-401 (UART)" id = 2
rosegarden: RosegardenGUIDoc::getMappedDevice - i = 3
rosegarden: RosegardenGUIDoc::getMappedDevice - adding audio Device
"JACK Audio" id = 3
rosegarden: RosegardenGUIDoc::getMappedDevice - Sequencer alive -
Instruments synced
rosegarden: MultiViewCommandHistory::attachView() : creating actions
rosegarden: RosegardenGUIApp::performAutoload() - autoloading
rosegarden: RosegardenGUIDoc::deleteContents()
rosegarden:
RosegardenGUIDoc::openDocument(/usr/share/apps/rosegarden/autoload.rg)
rosegarden: RosegardenProgressDialog::RosegardenProgressDialog type 2 -
Reading file... - modal : true
RosegardenGUIDoc::xmlParse (reader.parse()): 60ms elapsed
rosegarden: RosegardenGUIDoc::openDocument() end - m_composition :
0x85447d4 - m_composition->getNbSegments() : 0 -
m_composition->getDuration() : 0
AudioFileManager::generatePreviews - for 0 files
rosegarden: RosegardenGUIApp::initView()
rosegarden: TrackEditor::setupSegments() begin
rosegarden: SegmentCanvas::slotSetTool(3)[SegmentCanvas pointer
(0x856fd68) to unnamed widget, geometry=100x30+0+0]
rosegarden: SegmentMover()
rosegarden: SegmentCanvas::slotSetTool(1)[SegmentCanvas pointer
(0x856fd68) to unnamed widget, geometry=100x30+0+0]
rosegarden: SegmentPencil()
rosegarden: useInstrument() - populate Instrument
rosegarden: RosegardenGUIDoc::slotNewRecordButton()
rosegarden: useInstrument() - populate Instrument
rosegarden: RosegardenGUIDoc::slotNewRecordButton()
rosegarden: RosegardenGUIDoc::slotNewRecordButton()
rosegarden: reinitialised studio
rosegarden: initialised 16 audio faders
rosegarden: getSequencerPlugins - getting plugin information
rosegarden: getSequencerPlugins - got 7007 items
rosegarden: Returning chord-label ruler width as 10200.000000
rosegarden: Returning chord-label ruler width as 10200.000000
rosegarden: Returning chord-label ruler width as 10200.000000
rosegarden: Returning chord-label ruler width as 10200.000000
rosegarden: RosegardenCanvasView::polish()


For the crashing of the drumtrack, I don't have enough time to reproduce
the crash now, I'll email the info tomorrow.

Karel.


On Sun, 2003-04-13 at 07:15, Silvan wrote:
> On Saturday 12 April 2003 02:37 pm, Karel Lemaitre wrote:
> > When I launch rosegarden (0.8.5) the first time at a fresh login, it
> > crashes, leaving the RG-sequencer running. If I launch RG the second
> > time, everything seems to be functioning normal... Although for some
> > strange reason, RG crashes when trying to modify a drum-track.
> >
> > Can I prevent this from happening?
> 
> You haven't given us much to go on here.
> 
> Try running from the command line, and then post the output stream from 
> slightly before up until the time when the GUI crashes.  It might afford us a 
> clue for something you can work around.
> 
> As for the crash when modifying the drum track, the same thing applies.  A 
> little hint would be nice, to see if it's possibly some sort of configuration 
> issue that you can do anything about.
> 
> Otherwise, I'd say just sit tight and hang in there.  A new release is coming 
> soonish, with several new features, myriad bug fixes and a  host of new and 
> improved bugs to explore.  :)