Dynamics/Velocity Question (Beta 1)
Hi folks,
I just noticed that in the Beta release, dynamic velocity has changed somewhat. In 1.X, the dynamics and velocities were as follows:
mf = 80
f = 96
ff = 112
fff = somewhere around 120
And the velocity was capped at 124 or something like that; you couldn't go above that velocity. Now it seems that the velocity cap is only 99, meaning f is the loudest you can go. You can't even reach the old ff velocity. In fact, ff and fff are now the same velocity (99). Is this just an oversight or is this actually how it'll work in 2.0? Perhaps this is a known issue and has been fixed already.
If this is indeed how it will work in 2.0, then all the dynamic velocities should be changed to lesser values so you can get a true fff effect on playback.
Edit: I just did a test in which I repeated one chord at different dynamics, from p to fff. fff is indeed the loudest despite showing the same velocity as ff. So, the actual playback is correct, but the inspector thing only shows a velocity of 99. This is still a problem for those of us who want to tinker with the velocity of a specific note. If we want to do so in the ff or fff range, we can't because the inspector only goes up to 99. Unless of course I am completely missing something, which is always possible...
Comments
I suspect this is fixed in the nightly version since beta1 was released. I created a score of 7 notes, applied pp up to fff, and got:
pp - 33
p - 49
mp - 64
mf - 80
f - 96
ff - 112
fff - 126
By default, the Inspector does not show you the actual velocity of each note - it shows the *offset* you have applied from the default, which is the controlled by the dynamic markings in your score. So you should actually be seeing "0", not 99, for notes at ff, unless you have manually changed them already.
Could you describe in more detail, with sample score and precise steps, what you are seeing that is different from what you should be?
In currently nightly builds, I have no trouble setting the offset to 127, BTW. But of course, if a note was already at 80, you can't *really* apply that much offset - there is no such thing as a velocity of 207. It's still going to max out at 127, which works out to an offset of 47.
In reply to By default, the Inspector by Marc Sabatella
Okay, I played around with it a bit more. Yes, an individual note can be changed to any velocity up to 127. What I was actually referring to, but didn't make clear at all (apologies), is when you place a dynamic marking and view it's properties in the inspector. There you'll find Dynamic Range and Velocity. Here is where ff and fff are both 99 and cannot be changed to anything above that.
I just assumed I could change the default velocity for a specific dynamic marking this way (for example, change ff from 112 to 110). Perhaps that is not what that part of the inspector is meant for? Or is the velocity value defaulted to be an offset value rather than a user value? You can change between the two when looking at an individual note, but not here when you're looking at the marking itself.
In reply to Okay, I played around with it by pabond007
My numbers above refer to the dynamics, not the notes.
In reply to Okay, I played around with it by pabond007
Ah, I was looking at the velocity values for individual *notes* in Inspector, not for the *dynamic markings* themselves. Notes are represented as offsets, but the dynamics themselves show with full values. I understood your original question to be about changing values of notes one by one, not globally for all notes in a given passage. That's why I was looking at notes, not the markings.
Anyhow, in the Nightly builds, you can indeed go up to 127, so I think you are seeing a bug in the Beta that has already been fixed. I sort of remember hearing about that, but I can't seem to find an issue in the tracker.
In reply to Ah, I was looking at the by Marc Sabatella
Thanks for looking into it guys, glad to hear it is won't be an issue down the road!