> I think I hear what's happening. It's not that notes are missing but that > repeated notes get immediate noteoffs. It sounds like they are seeing > their predecessor's noteoff just after their own noteOn. > > I will look at what the ordering is and what it needs to be. Possibly > just changing the ordering of notes/noteoffs will fix it.
I've found the problem and I think I can fix it. We were already producing noteOff/noteOn in the right order; I traced it. Then SortingInserter would resort the list and change the order of events. So despite initially making them in the right order, we were writing them in reverse order. This is definitely the cause; I just listened to a MIDI export that does the right thing. But what I have right now is not a fix, just a cheap trick with the MidiEvent comparison operator. I will code a real fix for it. I will also incorporate fixes for two minor bugs that I tripped over while diagnosing this: * http://home.roadrunner.com/~jgglatt/tech/midispec.htm tells me noteoffs should have a "dumb" velocity of 64, not 127. * Our conversion from timeT to RealTime wasn't consistent wrt segment delay. Tom Breton (Tehom) ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
