Add ability to merge unsupported MIDI data with the open chart's tempo map

[GoogleCodeExporter]

Various folks are syncing the RB3 MIDIs with audio files.  It becomes 
problematic when people want to keep MIDI tracks that aren't supported, as EOF 
won't keep this during import.

I propose a feature to allow the user to import a MIDI to assist with the beat 
syncing process, then when the tempo map is completed, to import a MIDI file so 
that all events are converted to floating point realtimes and then back to 
deltas to merge into the newly created tempo map.  This would prevent users 
from having to use an external MIDI editor to perform the task.

Original issue reported on code.google.com by raynebc on 19 Oct 2010 at 2:50

[GoogleCodeExporter]

This would be more feasible once EOF using MIDI timing.  It can store 
unidentified MIDI events in a separate array, whose delta timings can be 
updated appropriately whenever an tempo/TS change is made.

Original comment by raynebc on 3 Nov 2010 at 10:14

[GoogleCodeExporter]

Original comment by raynebc on 14 Mar 2011 at 9:52

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Alternatively, this could be stored in a custom data block in the project.  The 
data block would need to contain track 0 and any other unidentified track.  
During MIDI export, each of the stored MIDI events will have its time converted 
to real time and then written using the active project's tempo map.

Original comment by raynebc on 17 Oct 2011 at 11:43

• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

Completed in r896.  EOF offers to store harmony and pro keys tracks during MIDI 
import and allows MIDI tracks to be manually stored by selecting a MIDI or RBA 
file.

Original comment by raynebc on 19 Apr 2012 at 9:57

• Changed state: Fixed