Control numbers?? Where? How??
Totally baffled – both MuseScore 3.6 and 4..
How do I control these MIDI control messages being exported from MS, which are associated with each of the chosen instruments?
If I have a flute track, the .mid export will have 4 different types of control messages. At time 1:01, Control numbers 121, 91 and 93 are all issued with a value of zero. Each note has an associated “Breath” message with a value of 80.
A Violin will have 3 (!) channels, with additional patches for violin, pizzicato strings, and Tremolo strings. Each of these channels will have added controls for volume and pan. (why is there 'Breath' control messages for a violin?)
These messages are shutting down settings I have in my DAW and Kontakt. I need to hand edit the MIDI channel event list in my DAW, which is very time consuming.
Can anyone tell me where the documentation for this is? How are they controlled? How are they used?
Please? I am almost two years with MuseScore and love it. This problem is one remaining mystery I really need help with.
help?
Comments
Internal details of how playback is handled aren't "documented" per see, except to the extent MuseScore is open source, so you can consult the code. But I'm guessing you re seeing the volume messages used to control dynamics. And/or pedal markings. Those are the things I know would typically use controller messages in MuseScore 3. Not sure about the new playback system for MuseScore 4.
In reply to Internal details of how… by Marc Sabatella
Thank you for the reply,
Yes. There is an instruments.xml inside the installation directory. This seems to be where specifics for each instrument is defined, but I cannot find where the default resets(?) for Controller #121, 93, etc are defined.
I am guessing that the three patches for a violin may be to trigger different articulations in Musescore playback. Right now, I need to export a MIDI file, convert it to a spreadsheet, edit out all the troublesome controller messages and convert it back to a midi file. That is when I may import it to a DAW.
While I congratulate the development team for the new release of Muse Sounds, I would like to comment that I see MuseScore's strength is in being a fine score editor, rather than a full featured DAW. There are many free and paid Digital Audio Workstations out there and MS would have a big hill to climb in order to match the others' level of development. I create my arrangements in MuseScore as standard notation, and then export midi files elsewhere to make a finished work. This includes subtle audio mastering of the final renders. I am hopeful that the development will continue to address features which may faithfully interpret written scores for the eventual export to other mastering tools.
In reply to Thank you for the reply, Yes… by Chris_Clawson
instruments.xml is no longer where these details are maintained; the file itself is something of a holdover from previous versions.
MuseScore 4 is not aiming to be a DAW - a program that requires you to spend hours upon hours tweaking audio parameters just to achieve moderately acceptable;e audio. MuseScore 4 is something far more useful to most composers - a program that produces stunning output right out of the box, no need to fiddle with settings note by note.
But MIDI export will no doubt remain possible for people who have the time to spend in a DAW attempting to get audio as good as the out-of-the-box results from MuseScore! :-)
In reply to instruments.xml is no longer… by Marc Sabatella
for MS3 , i've no experience in MS4
> Can anyone tell me where the documentation
handbook synthesizer
dev handbook instruments.xml
CC2=breath, the synth use velocity and CC2 to make loudness variation by deafult, value of 80=mf the default loudness
dev handbook instruments.xml, SND
you can change CC number or turn off CC2 see synth wiki above
> CC 121, 91 and 93
i've no idea why, you can repost in SOUNDFONT forum where the MIDI experts hangout
> edit out all the troublesome controller message
exactly what i've been doing. except i didn't edit .MID, i used a midi router FX in REAPER to filter CC
> a program that produces stunning output right out of the box
Yes Musesounds is amazing.
on the other hand, MS4's new support of VST inevitably need a common data layer/channel, what else could it be but MIDI CC?