I am mostly using SV5 by starting with importing MIDI files. But found that SV5 seems not acceptping/responding to the velocity/dynamics data in MIDI files. The loudness in SV5 remains flat all the way. How can I make it interpreting the note velocity and become the default loudness in parameters? Or I have to manually add/draw loudness in SV5 to get that? Any tips for making the adjustment of dynamics easier?
I am exporting MIDI files from Dorico that has the dynamics/velocity info baked-in.
Dynamics and other properties are controlled internally by SV. Certain properties are exposed for some singers, and other properties for others depending on how the voice was constructed.
I’ve tried it and it works nicely. But just another idea came through, for voices, it might be helpfful if the mod wheel CC1 can also be extracted and combined with velocity then apply to Synthesizer V loudness (or separately only CC1). That could help shaping a more realistic and expressive dynamics. I found that my Dorico exported MIDI file contains CC1 that seems to be representing more closely to ideal singing dynamics.
But 2 days! to understand… your so specific midi file!
Because of several cases:
1/ Strange behavior when importing and then exporting midi from Cubase. Some results doubled the number of notes when reading the content…
2/ A first try with my script worked well. But only on my own midi file. Hours to understand why…
3/ Discovery that your specific midi file contains a tempo change (not at the beginning of the midi file…). This has contributed to strange behaviors…
4/ I was looking for a way (a workaround) to make my script work well on both midi files (mine and yours).
Finally, I just published an update on my github but it is not sure if it can work on any type of midi file.
You can try it now.
Thank you so much for spending so much time on this!
I am really sorry that I found I accidentally put two tempo mark at the first measure!
I quickly tested the new script. The CC1 value does applied! Just the loudness gain is generally very very high (often over +12 dB) even when the velocity gain is set to 0. I have to manually pull all the way down the whole loudness curve for a more ideal volume like the picture attached.
The midi file is exported from Dorico as it is. Indeed in some songs there might be some tempo change, even some accellarndo or rit. The Synthesizer 5 imported the midi fine with the correct tempo change when listening, but it won’t be reflected/displayed on the measure/tempo/signature track in Synthesizer 5 arrangement window or piano roll window, though. The time signature and tempo will only be displayed once at the beginning of the song and the actually measure/beat heard will gradually get out-o-sync with the displayed position. Note sure why. Maybe because Synthesizer V won’t read and reflect those change.
Just a quick initial feedback. I’ll test more and let you know if I found any issues.
Thank you very much, I believe this script will be very helpful to many people! As some might already shaped their loudness/volume of the voice in their original MIDI. And by applying it to the Synthesizer 5 track really make the voice sing more vividly and naturally!
Again, really really appreciated and this is awesome!
I updated the midi file and placed it here (fixed the doubled tempo mark): Test v2.mid.mid
I have been following this with interest.
Tempo changes are both possible and quite easy when you figure it out, any tempo change is indicated in the piano roll header strip, amongst the bar count indications, maybe a bit subtle but it’s there and can be changed mid-song.
Accel and rit are possible, I have done it.
issue-regarding-tempo-editing
I hope this script can play nicely with tempo changes when finished, even if it isn’t commonly used.
You’re welcome but I am not sure to do this again… to much time consuming!
But an interesting challenge.
Yes I’ve just added a reducing gain with a slider in the dialogbox.
Yes, same with Cubase. With most DAW we can set tempo first (so the tempo is set at the beginning position). User can set tempo anywhere in the song.
And it is not obvious to check everytime if the project is exactly at the starting position of the song. Excepting if you take care of it.
With your first test.mid file, we can heard the piano playing faster and then (1.25 second) slower and not seems to be desired. So your test V2 is better.
I tried myself with a Cubase with multiple tempo and my script was always working. I also added input aids to save time on file name or default positioning of track names:
Retrieve the path filename from the clipboard (if exists) for the dialogbox.
Retrieve the path filename from a track renamed with the full path name (piano track for example in your project) for the dialogbox. This makes it easier to test the script multiple times.
I checked your test V2 midi file and it works too.
The updated script works great. I can try the sliders and manually tweak the curve by moving control points here and there to get the dynamics I prefer much faster than hand drawing. I believe this concept has the potential and would be very useful in some people’s workflow!
