Ted:

I had additional information on the Rosegarden crash, but my reply with the information included two '.rg' attachments. 

In case the reply got filtered-out because of the attachments, here is the information without the attachments:


I re-ran my test, with Rosegarden running in a terminal so I could collect diagnostic information. 

The results were much the same as before, except that when I stopped the recording (this time by pressing the Play button, rather than clicking the Stop button), Rosegarden (in the terminal session) went into a loop outputting the following text:

WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder
WARNING: This is probably a bug; fix required
WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at ^C
aere@aere-Dell-DE051:~$

It did this for a very long time, and I finally terminated it via a control-C sequence. 

In looking at the diagnostic information, I wondered if perhaps it might have something to do with the chord at the end of the piece being held (at least some notes of the chord) for a very long time (while other notes of the chord switch between major/minor 3rd and major/minor 7th. 

So I recorded once, stopping playing before the very long held-out notes.  It actually succeeded in recording that once, but subsequent attempts (again stopping playing early) failed the same way as before.  So I have only that one successful short recording on the 11.11.42 version of Rosegarden.

I have attached that recording, which may be of limited value, since the recording filters do not get saved in the file (I wish they were saved in the file - it would save me time setting it up for subsequent recording). 

I have also attached the version of the piece I recorded on the earlier version of Rosegarden, which has been quantized and edited so that it prints out properly.  Given the editing and quantization, it may not be that useful, but is is what I played when recording, and it was originally successfully recorded on the earlier version of Rosegarden. 

It is possible my MIDI software is doing something wrong (I have no clue of what), but it records fine on the prior version of Rosegarden. 


- Aere




On Tue, 2012-06-05 at 10:51 -0400, Ted Felix wrote:
On 5/22/2012 3:09 PM, Aere Greenway wrote:
> I then clicked the "stop" (the filled-in square) toolbar button of the 
> Rosegarden window, and the Rosegarden window immediately disappeared 
> (I assume from the crash).

   I cannot get two MIDI keyboards to crash rg.  Here are the steps I took:

1. Launch jack and fluidsynth from the command line.
    See "My Audio Script" at http://tedfelix.com/linux/linux-midi.html.
2. Connect Akai LPK25 MIDI keyboard to USB (fixed on MIDI channel 1).
3. Launch vmpk and set to channel 2.
4. Launch rg.
5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices.
6. Arm tracks 1 and 2.
7. Press record.
8. Play on both keyboards.
9. Stop.

   I tested the above on 11.06, 11.11.42, and the latest svn.  Ubuntu 
12.04 64-bit.  No crashes.  The MIDI events go to both tracks (which 
seems slightly useless, but is the same for all versions tested).

   Sounds like you might have a bad library.  Are there any steps I may 
have missed?

Ted.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

-- 

Sincerely,
Aere