Is there a way to copy a volume automation into a velocity automation?

[Keith Young]

I would like to do this and then use the offset tool to offset either form to get a balance between amplifying the sound and simulating the effect of playing louder.

 

[David Baay]

It's not currently possible to automate Velocity Offset. If the synth is programmable you might get the same effect by assigning a controller(s) to brighten the tone, open a filter or do whatever else it is that makes the timbre change with velocity and automate the controller(s). If the synth is a sampler with velocity layers, you're kind of out of luck.

Edited November 1 by David Baay

[Amberwolf]

You could use a velocity-scaling plugin, and reassign the copied volume (CC7, etc) to it's appropriate parameter. 

 

Unfortunatley the cakewalk velocity MFX isn't automatable.  I cant remember if Variorum's MFX are automatable (the "compressor" modifies velocity, so it should be able to do what you're after if it is).  

I think there's one by NiallMoody for velocity scaling, but don't recall if it's automatable. 

Might be others. 

 

 

 

Edited November 2 by Amberwolf

[David Baay]

I should add: if it were me, I would just destructively edit the velocities (or re-record the performance). In addition to editing them directly and "drawing" ramps and  curves as you would with automation, the Transform tool allows re-shaping groups of velocities in various ways without losing the underlaying rhythmic pattern. 

[Amberwolf]

2 hours ago, David Baay said:

I should add: if it were me, I would just destructively edit the velocities (or re-record the performance). In addition to editing them directly and "drawing" ramps and  curves as you would with automation, the Transform tool allows re-shaping groups of velocities in various ways without losing the underlaying rhythmic pattern. 

FWIW, it is often helpful to experimentation to use automation to play with various ideas, as being much faster to shape and reshape curves and nodes than to do any of the direct methods of editing velocities, individually or en-masse. 

This is how I use automation for most of my purposes (sometimes later baking it into a rendered version, sometimes leaving it as is, depending on further edits needed or the end-usage of the results). 

[Keith Young]

I think I will have a play with different things. Thanks.

[Keith Young]

I wrote a MFX MIDI plugin for Sonar. I am still working on it, but basically it allows you to control the velocity of the notes in a track by the values of an automation controller and then have various different ways to apply that information. So as you play the track, the plugin keeps the current value of a user defined automation controller (defaults to 20) and then either replaces the velocity value or, more intelligently, uses it as a boost value so that values recorded are not lost. It has a couple of different "curves" and a boost factor. I am not sure yet that is the best way to use it. Also, it means you can set the input automation to be 7 (i.e. volume) and us the volume automation to update the velocity of the notes. It's a fun toy if nothing else. I am aware that it has probably been done before.

[Amberwolf]

It sounds sort of like an automatable version of Variorum's "compressor" (if that one isn't already automatable). 

 

If it's available as a 32-bit MFX, I'd be interested in playing with it on my ancient SONAR .   

If it obeys normal automation data within a MIDI track (not just CCs within clips) then you could copy automation cuves you have created in other tracks to the track it's on and then reassign those to it's parameter(s). 

[Keith Young]

I should investigate both. I have written it to compile 32  and 64 but only have 64 to test. 

[Keith Young]

It appears to work on my old 32-bit Sonar Pro.

I am having a lot of difficulty building an install whether using WiX or Inno. I don't understand why it has to be this hard.

So, without an install, the output consists of 32- and 64-bit versions of the DLL and their pdbs and an optional .ins file. Essentially, you install the relevant DLL and PDB into "Shared MIDI Plugins", register the DLL with regsvr32.exe. You can import ins and it will name controller 20 to dream if that's what you want. I should also write a description file explaining what it is doing that I have not got round to.

[Amberwolf]

Whenever you put it up I'll see if it will register and operate here (occasionally in testing things like this I've found something that works on a dev system has a dependency that didnt' get packaged with it during compile), then I can play with it and let you know of any issues (or feature requests if you accept those). 

 

[Keith Young]

I have uploaded the two versions:

x64
https://1drv.ms/u/c/0cfa47718ef7d49e/IQB7PtmYYf8ZSYZj1hqGZiPdAac8oMLFsvBibyI4Z3SE1Ck?e=COFbne
x86
https://1drv.ms/u/c/0cfa47718ef7d49e/IQB_bsamGJllTZnkDqRnDU9AAb8_qZXtrAkKeUPr8OcXCPY?e=fNzXar

Each link points at a zip file containing the plugin, a symbol file and a Readme explaining what it is, how to install it, how to monitor it and the standard MIT license.  Have fun!

[Amberwolf]

Thanks!  I'll poke around with it and see what I can mangle with it.