Velocity values in Xml files
I'm working on Musescore 3.6.2 but suppose that my question may apply also to latest versions.
>If I load a .xml file , I can see all the dynamics (p,mf, f, crescendo etc.) and the file play accordingly
but on the "Inspector" (file 1.jpg) all the notes are type "Offset" with velocity =0
If I go to the PianoRoll (file 2.jpg) and select "Velocity absolute" at the left , I can see all the velocity values
of the notes , corresponding to the dynamis p,mf,f etc. and that is how the file is played.
>My question : is there a way (a quick way) to put all the velocity values as "user" in the Inspector ?
I'm asking because I normally work with Musescore and Cubase , but if I import the .xml to Cubase
all the dynamics indications are preserved ( p, mf , f, < > etc. as they appear in Musescore )
but the velocity is lost (it is fixed for all the notes ) and the track of course plays "flat"
Thanks in advance
Comments
• Select a note in the score.
• Right-click it and choose "All similar".
• Set any note properties in the inspector, e.g. velocity type, and they will all get the same setting.
In reply to • Select a note • Right… by yonah_ag
This is OK when you start a new piece . In my case I already have the file .xml loaded and I would transfer
the velocity values which appear on the PianoRoll to the Inspector ..........
In reply to This is OK when you start a… by Luciano Rizzi
Your only question was:
My question : is there a way (a quick way) to put all the velocity values as "user" in the Inspector ?
Hence my answer, which applies to both new scores and existing scores.
Can you share a few measures of a score, (mscz file), where the PRE velocity differs from that seen in the inspector?
In reply to Your only question was: My… by yonah_ag
See attached . However it is exactly the same as shown on the .jpg images attached above.
And it is not that velocities differ . the problem is that they are shown in the Piano Roll
while in the Inspector everything is "Offset" and zero and I would like to transfer those velocities
from the Piano Roll to the Inspector (which is the only way to see them in Cubase when I load the .xml)
In reply to See attached . However it is… by Luciano Rizzi
But I can't edit the jpg in MS to investigate the issue.
And I'm still confused. You say, "it is not that velocities differ" but then you want to transfer them. What's the point transferring them if they do not differ?
Maybe when I check the file it will make more sense.
In reply to But I can't edit the jpg in… by yonah_ag
You only need to use velcoity values if you want to override the dynamic on a note.
You can change the velocity associated with a dynamic marking from the inspector. Here I have selected the f dynamic marking in measure 17:
or you can set user velocities as I described above, (and ILPEPITO confirmed below), if this is the only way to get the dynamics carried over to Cubase properly.
Sorry . I specify "My question" above :
My question : is there a way (a quick way) to put all the velocity values as "user" in the Inspector ?
i.e. copy the values which appear on the Piano Roll and paste them on the Score so that the Inspector
will show "User" and value instead of "Offset" and zero
In reply to Sorry . I specify "My… by Luciano Rizzi
I did an experiment with Cubase 12 Pro.
I prepared 4 musicxml files exported by Musescore 3.6.2, all with only 4 notes:
1) Only dynamics ('P', Velocity = 49; 'F', Velocity = 96), no Velocity value for single notes;
2) No dynamics, growing values for the Velocity of the individual notes (40-60-80-100);
3) Dynamics + Velocity by combining the indications of the first two;
4) Dynamics as previously + fixed Velocity value (127) for the individual notes.
I don't know what to think about your request: Cubase 12 imports only the dynamic indications in the lane of the Velocity, and completely ignore the values of the Velocity of the individual notes. Is it perhaps a question of 'version'? (For example, Cubase 14 seems to no longer support Musicxml files, other versions I don't know how they behave).
If you really want to copy the Velocity values of the dynamics in the values of the individual notes, the first suggestion of 'yonah_ag' seems very correct to me: just select for 'blocks' the notes (all those that have, for example, the indication 'p') and assign the relative Velocity value.
In reply to I did an experiment with… by ILPEPITO
Thanks to you and to Yonah_ag for the replies.
To summarize :
> My question was because I normally use Musescore to Cubase and viceversa.
>The xml file play correctly in Musescore where you can see and hear all the Dynamic Indications and all the
correponding Note Velocities . However the individual Note Velocities can be seen only in the Piano Roll
while in the "Inspector" all the velocities are shown as "Offset" =0
AND THIS WAS MY PROBLEM BECAUSE IF I LOAD THIS .XML IN CUBASE , IT IMPORTS ALL THE DYNAMIC
INDICATIONS BUT IT IGNOREs THE VELOCITY VALUES (AS SHOWN ON THE ATTACHED "3.jpg" WHERE ALL
THE VELOCITIES ARE =90 !) .THIS IS A CUBASE "BEHAVIOR" IN ALL THE VERSIONS (Ihave from Cubase 5 to
Cubase 11 and all of them have the same problem importing .XML)
> To solve this problem what I'm actually doing is as follows (which is what you suggested) :
1) In Musescore I notice the velocity values corresponding to Piano (p) =49 , to Forte (f) = 96 etc.
then I select all the notes in that section and put the velocity value in the Inspector (i.e User =49
User=96 etc.)
2) At the end I re-save the Score as XML and then import in Cubase , AND THIS TIME IT KEEPS BOTH
THE DYNAMIC INDICATIONS IN THE SCORE AND ALL THE INDIVIDUAL NOTE VELOCITIES IN THE PIANO ROLL
> MY QUESTION WAS IF IN MUSESCORE THERE IS A QUICKIER WAY TO COPY ALL THE INDIVIDUAL
VELOCITIES WHICH APPEAR IN THE PIANO ROLL AND TRANSFER THEM IN THE INSPECTOR SLOT
AT THE PLACE OF "Offset =0" . The question was mainly if I have a long Orchestra Score with a lot of
dynamic changes , the procedure of the above points 1_2 takes long time.......
In the case you will find a quick trick for the above , pls let me know
In the meantime thanks a lot to both of you for the kind assistance
In reply to Thanks to you and to Yonah… by Luciano Rizzi
In Cubase 12 it is not as you say; here I attach two screenshots obtained from the import of a musicXML that contains ONLY dynamic indications: as I said, it would be useless to even add the velocities of the individual notes because they are not considered.
Apparently, this is not the case in the version you have. I see only 2 solutions: update the Cubase version to 12, or create a specific plugin for Musescore. If I find the time (but I don't promise anything) I could also make it myself.
In reply to In Cubase 12 it is not as… by ILPEPITO
So it seems from the first screenshot that Cubase 12 keeps the velocity values from the xml ...
However I don't have the version 12 . I'm on Win 7 and that's why I use Musescore 3.6.2 and Cubase 10
which are the last versions for Win 7 and don't want to change for many reasons .
In Cubase 10 the XML individual velocities are not imported if the Musescore Inspector show "Offset =0", while after many tests , If in Musescore I put "User =49 etc...." then they are OK also in Cubase !
I Will appreciate If you will create a Plugin or a workaround to transfer velocities from Musescore PianoRoll
to the Inspector slot (but you are quite at MS version 5 and I'm still to 3.6.2 ........)
Thanks a lot
In reply to So it seems from the first… by Luciano Rizzi
I attach here the first drafting of the plugin (for MS 3.6.2), with the hope that does not contain a few bugs. I was able to try it only briefly and it seems functional to me, but you never know. Read the instructions carefully, which also clearly indicate the limits of the plugin.
In reply to I attach here the first… by ILPEPITO
I add 2 things that I forgot: 1) it is always better to work on a copy of the original score; 2) In the case (improbable) of non 'blue rectangle' selections, the dynamics will always be selected sequentially, while for the notes the selection order does not matter.
In reply to I add 2 things that I forgot… by ILPEPITO
I wrote a second drafting that solves the potential problem of the non -sequential selection of the dynamics, in addition to the fact that someone could place them in different voices. So it's certainly better, it's just about testing it.
In reply to I wrote a second drafting… by ILPEPITO
I have downloaded and installed the Plugin . I loaded an XML file of approx 100 measures with different
Voices and with Dynamic changes every 2 or 3 measures from "ppp" to "fff" and the result is .........................:
THIS IS EXACTLY WHAT I NEEDED !! SIMPLE AND QUICK .
(with a large score and many Dynamic changes it tends to " not responding" but leaving it , after a while it has done ! In this cases probably it will be better to make 2 or 3 selections instead of a "CTRL+A")
For me it was worth it because it is the only way I have to import XML into Cubase preserving the dynamics and velocities. And for that I don't know how to thank you because it saves me a lot of time composing with Musescore and Cubase.
And you can bet I will use it almost all the time!
THANKS AGAIN FOR YOUR EFFORT AND SUPPORT !
In reply to I have downloaded and… by Luciano Rizzi
Not at all. Remember that if you divide the work into several selections, each selection must contain the indications of dynamics; As I wrote in the instructions, for large scores, it is just a little patience. It could also be that I forgot to consider something: in the case of anomalies, let me know and then let's see if something can be done. Have fun!
In reply to Not at all. Remember that if… by ILPEPITO
OK , it's clear
But from the few tests I have done it seems to work perfectly . And also there is no need to go into the Piano Roll because everything can be done from the score with a click ! In addition , if I want to put a particular
velocity value in the Inspector , it will preserve it ! VERY GOOD.
I think I will compose a Piano piece dedicated to you using only this plugin and will upload to the Musescore site.
Thanks again !
In reply to Not at all. Remember that if… by ILPEPITO
Nice work.
In reply to Thanks to you and to Yonah… by Luciano Rizzi
There are no individual velocities in your score . What you are seeing in PRE are the velocities implied by the dynamic markings.
A plugin would be possible for setting note velocity from dynamic markings but it has nothing to do with PRE.
The plugin would also need to deal with any user velocities already in the score. How would it distinguish those from a previous run of the plugin vs. those where you have tweaked velocity manually? This would mainly be an issue if you changed the dynamic marking for some measures.
If you save the score as a mscx file you can inspect it as plain text, (xml), and see exactly what data is available
In reply to There are no individual… by yonah_ag
I'm not sure I understand some of your objections, but I'll try to answer anyway.
The main purpose of the plugin (with all its limitations and the need for a 'smart' user to apply it) will simply be to limit manual work in the case in question, a very 'specialized' case.
I only have a general idea for the moment, but I think that: 1) the user doesn't seem to be interested in preserving already set user velocities of single notes, but a switch could be added to activate/deactivate this option (I don't think there are any 'magic' plugins that can do everything without the conscious intervention of the user); 2) assigning in 'block' the velocity of a dynamic indication to the velocity of the single notes (as rough as it may be) opens up the possibility of using the MIDI format to transfer this data too, a detail that interests me more than anything else.
What will come of it? We'll see...
In reply to I'm not sure I understand… by ILPEPITO
The first part of my post was for the OP, trying to explain that there aren't actually any note velocities in his score and that PRE is just showing the values corresponding to the dynamic markings.
A simple plugin should work well and save a lot of manual effort.
It's probably not worth inviting complications that might never be needed.