> On Wednesday, January 25, 2012, Tom Breton (Tehom) wrote:
>
>> So ignore most of what I said. So I'll use Instrument's old m_channel
>> as
>> its channel just when it's fixed, which is just when it's not auto. And
>> bring the remapping check and warning back in, and save the
>> device-relative channel despite anything auto does.
>
> I wonder about the remapping check. It _should_ only come into play for
> old
> compositions.
OK, it's back out. That's easy right now.
For old compositions, I still have to make percussion default to fixed.
Otherwise, while new drums wouldn't play out of the piano, old ones would.
(Done now. I'm back)
With that, I think the only loose end is MidiFile.cpp. I've given that
some thought. Hopefully I haven't designed it the hard way again. I will
run it by you.
What I'd like to do is make MidiFile use part of the normal
Events-to-output logic (metaiterator and the segment mappers). MidiFile
would write the MIDI headers etc, then create a MappedBufMetaIterator and
use it to write the MIDI.
In one way, it's roundabout. I'll turn Events into MappedEvents and then
to MIDI. It'll turn TimeT into RealTime and then back into TimeT. But it
may have to be that way to handle segments' RealTime delay.
On the plus side, it wouldn't miss anything and the sorting is already there.
Tom Breton (Tehom)
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
