Thanks you so much Andi! Figuring out all the dumps in HEX has always been nightmare.
Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
196,707 users have contributed to 43,030 threads and 258,430 posts.
In the past 24 hours, we have 6 new thread(s), 11 new post(s) and 94 new user(s).
Fantastic. Thank you. I experimented with dump and VSL and it took me several tries before I found the right hex representation for a particular keyswitch midi note. Very tedious.
The readme says it doesn't depend on the Human Playback system which I understand and may ultimately be a good thing, but you still need HP to interpret dynamics correct? I think it would be great to be able to turn HP off actually because I think it does some strange things especially with regard to dynamic "mis-interpretation" at least for me.
Another possilbility this method of keyswitch could afford is for mixing libraries. If for example you wanted to use some GPO instruments along with VSL simply set the method of dynamics for sustaining instruments in Finale to use CC#7 + velocity then change expression in VSL to use CC#7 and even Velocity XFade to use CC#7 and use these keyswitch expressions rather than creating all the HP techniques.
HP has the advantage of being able to perform two actions; very good for an x y matrix. A staff expression can still only do one.
I think these are a good adjunct, for switching matrices orAB switches.
Hi winknotes_282!
It's not necessary but it is possible to turn off Human Playback completely and still use our collections with the VSL Keyswitch Dump. The velocity values according to the dynamic marks you have written will be sent anyway. You are right that Human Playback does some addional interpretation with dynamics.
Best,
Andi
They are text expressions you simply insert in your score where you want a keyswitch to occur. All the dump programming info is already programmed into each text expression and the expressions themselves are hidden text so they won't print in your score.
I'm very new to VSL, and I can't figure it out how to read the matrices in the manual and let them work in Finale. For instance, if you want a snap pizzicato in your violin solo (SE1), the dump would be KS F#1 according to the matrix, right? But I do not understand the principle of the Rows (V1, V2, sometimes V3) and how to exactly choose the right KS that sets the articulation as mentioned in Row V2. You get my point?
Hello wlasoen and welcome to the forum!
The Special Edition and Special Edition PLUS matrices have MIDI CC1 mapped by default for Y-Axis control. So you will have to add CC1 commands to your score to switch between rows. These commands are also included in the keyswitch dump file for Finale.
Best regards,
Andi
Hello Prong!
In Finale you can set up which MIDI commands get sent to virtual instruments under Human Playback Preferences/Dynamics/Volume. Our instruments react to velocity and/or MIDI Control Changes according to your settings. If you use our instruments with Finale, I recommend the following settings in our instruments.
Velocity X-Fade turned on and set to CC11. Expression set to None, CC12 or any other free CC that you don't use for other faders. Master Volume set to CC7. Then I would set "Dynamic Approach for Sustaining Instruments" in the aforementioned Finale menu to "Expression (CC#11) + Velocity". Please note that some earlier Finale versions had CC7 and CC11 mixed up.
CC1:000 stands for Control Change 1, value 0.
Best regards,
Andi