On 09/12/2013 08:19 PM, Tom Breton (Tehom) wrote: > If I remember correctly, those all come from the way MappedEvent stores > text events, sysex events, etc. I bumped into this strange behavior when > I wrote the new MIDI exporter.
That sounds right, but I only glanced at it momentarily. > AFAICT there is no good reason for it to do that. It doesn't actually > keep the data between sessions. It struck me as an expensive substitute > for std::map. My guess is that it is intended to handle large sysex dumps. To keep them out of memory. In my case it appears that many thousands of very small messages are sent when I press buttons on my keyboard. Each of the 70,000 files was less than 10 bytes. It probably needs to be made smarter. Assume the message will be small, then offload to disk over a certain size. In this day and age of multi-gigabyte RAM, I'm not sure disk matters, though. Especially given that MIDI is a mere 31.25kbps. Or does MIDI actually run faster now that it can travel over USB? (I bet no.) Then there might be a situation where a sample dump or somesuch would require a disk cache. As a workaround, I could probably use rg's record filtering to remove the offending messages. Ted. ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
