MIDI Export Options for CC Data

• Apr 12, 2021 - 16:53


I'm not sure if I am missing something but when I read the Musescore handbook I don't see anything in regards to options for exporting MIDI data. When I import midi into Logic created with Musescore I've noticed that the handling of dynamic info is instrument specific and is translated as breath control CC2 for Strings (see attached).

Even in the case of woodwinds and brass I'm almost always wanting expression and modulation data in regards to dynamics as breath control is not incorporated into most orchestral sampling libraries.

I'm wondering if there is a way to give more options per stave or system in regards to how MIDI data is handled and how dynamics are applied as it would save a lot of time when it comes to making Mock-Ups based on Musescore's MIDI output. While I haven't experimented with direct MIDI out from Musescore I would think that this would also be critical to creating realistic real-time performances.

I'm aware that I can do this all in Logic but it is cumbersome and time consuming particularly if sections need to be re-written and re-imported etc...

As an aside I also think it would be useful to be able to disable things like default reverb, chorus, panning and volume to allow for more flexibility if one wanted to for example create a fade in using volume automation.

Any help or guidance would be much appreciated.


I'm not 100% clear on what you are trying to do here, but I can tell you that there are global controls for how dynamics are handled in View / Synthesizer / Dynamics, and also for each staff in Staff/Part Properties. I don't really know how these play with MIDI export though. I would hope though that if you disable single note dynamics, or set them to use a different CC message, this would be reflected in the export or direct MIDI output.

As for disabling effects, similar answer, really - the global controls for playback are in View / Synthesizer, the specific instrument controls are in View / Mixer.

In reply to by Marc Sabatella

Hi Marc,
That was exactly what I was trying to do although I did realize that you have to hit "save to score" in the bottom left before the desired CC channel (11 in my case) will export as MIDI. I do think it would be great to have more flexibility in this realm overall. Unless I'm mistaken, however, this is only possible for the entire score as the only option I received on staff/part properties is a tick box for "use single note dynamics" and I don't see how one could for example, have flutes use CC2 and violins use CC11. I also think it would be great to have the ability for dynamics to affect more than one CC i.e. CC1 and CC11 so that you could have both timbre (modulation) and level (expression) automated at once.

In regards to the mixing controls I did see where those take place but as far as I'm aware it is not possible to bypass them entirely. The reason I would want to do this is that sometimes the initial expression messages are sandwiched between the (essentially null) reverb volume and panning messages and it would make for a smoother workflow since these controls aren't being used. It's also no longer necessary to have multiple program change messages on export unless once desires to use general MIDI which is almost never the case.

Thanks for such a quick reply!

Do you still have an unanswered question? Please log in first to post your question.