Hello Dorico team,
Would be very nice and useful if we have two separate options to disable the exporting of
the Expression Maps and CC data in the MIDI Export Dialog.
/Here we need to have in mind that some Expression Maps could contain CCs, if the disable function isn’t checked, it should preserve the CCs which are part of the Expression Maps, no matter if the disable function for CC data is selected. When E.Ms are disabled but CCs - not, then only the CCs which are part of the E.Ms should be excluded from the MIDI file./
Some DAWs have their own expression mapping systems and exporting them from Dorico
make the MIDI file very messy, because the exported expressions appears as midi notes, if they were keyswitches.
These options will make the MIDI file more clear for further editing in a DAW (Cubase/Nuendo, Studio One, Logic Pro - they all have own E.M. systems), which of course will save so much time.
I don’t think it’s likely that we would do this specific thing as you suggest, but I understand the underlying requirement, namely that you want the capability to export only the written notes and exclude the additional information required for a specific playback template. At the moment, you can do this by changing to e.g. the HSSE (SE) playback template before you export your MIDI file, but of course that can be a destructive operation so you would be well advised to save your project before you change the playback template and then discard the edited project after the MIDI export has completed.
@dspreadbury hello,
Thank you very much for the reply!
I hope you are doing well!
Yes, you correctly understood the idea of this request.
I will use this temporal solution but in the future would be nice if you consider to implement such
MIDI file Export options, because they will save so much time.
Switching every time to HSSE (SE) isn’t the most correct and logical way to achieve this result.
In addition to being destructive within Dorico, the resulting MIDI file can be destructive to any DAW that plays it. This output embeds a Program Change, so if the currently loaded synth responds to program changes then playing the MIDI file will change the patch. Yes, it’s possible to clean up that data - but you have to know it’s there, and have to be careful not to play the MIDI file before cleaning it up. I have a folder of MIDI clips that I preview in REAPER’s Media Explorer, and unfortunately Dorico MIDI files mess up my patches.
For anyone using REAPER, there’s a plugin in ReaPack called “MB MIDI Event Filter” that provides MIDI filtering and channel remapping. Toggle “Program Change filter” to “On” and the MIDI clip won’t mess up your synth preset:
Hey Daniel,
Hope all is well. I, too, think that implementing the option to export MIDI without any CC data would be immensely useful and a huge time saver.
Thanks, Sebastian
I’d be interested in a reply to @Janus question if the issue cannot be solved simply by applying the Silence template. What happens in this situation?
+1
I use NotePerformer in Dorico, but usually export to a DAW to do a more realistic mockup. The amount of time it takes to find and delete all the NotePerformer-specific CC info, that doesn’t work with other VIs, is pretty time-consuming.
Hey,
I found a workaround for the transfer of MIDI files from Dorico to Cubase. I created a preset in the Logical Editor (see screenshot), and then created a Macro in Key Commands that deletes all MIDI CC as well as all Program Changes of the selected MIDI files.
