![]() ![]() And this neednt be very complicated to implement either because volume and velocity are independent of each other. Its a big creativity killer.īlackbart is right some of you are confusing velocity with volume. ![]() All this just to turn down some hi hats or snare or bass drum or whatever so they sit better in the mix. So now I have to find a workaround by opening up each tracks midi editor and selecting all the midi notes and then grabbing a velocity handle and turning down the velocity hits for all the midi notes. If I turn down the volume fader of the drum vsti then it turns down the volume of all the drum parts. Right now there is no easy way to turn down the velocity of these individual tracks. For example I have some midi drums each on their own track snare bassdrum hihats etc. But with the track faders contolling midi velocity we could have one instance of a vsti and then multiple tracks in a folder that go to that vsti and control the velocity that is sent to the vsti withought affecting the overall level of the vsti. Some people dont want to load multiple instances of the same vsti just to control the volume of their midi tracks. Right now the way it is it kind of sucks because you can only control the global volume of all the midi tracks (like the master volume on a mixer) rather than individually. What a waste of space and screen realesate. ![]() It breaks my heart to to see all those faders sitting their in the mixer doing nothing. The faders would be useful for contolling midi velocity. It takes a little bit longer, but I can save the volume changes with the MIDI file, and they are there is I ever need to load the file in another sequencer. I prefer to just draw in the CC#7 data for each channel, or record it in real time as I'm mixing. This could be handled by having the user select whether they want audio or MIDI volume to change. I would not want a single fader (as we have now) that applied the same MIDI volume to all channels.Ģ) If the MIDI data is being sent to a VSTi on the same track, you don't want the fader to alter both MIDI volume (CC#7) and the audio volume of the VSTi - then you would get twice the amount of volume change as you would get for a pure audio signal. It's not brain surgery, but there are some things to consider that make it more difficult than it seems:ġ) If the MIDI item has multiple MIDI channels in it, what you really need is up to 16 faders so that you can control the volume of each channel independently. ![]() It's not brain surgery.have the tracks that are sending MIDI switch to MIDI functions. I don't even bother opening the useless mixer!ĭark Star.thanks for all the research and compilation!!! I set up templates with them already inserted on all the MIDI channels. Function Mode".įor now, I'm using one of various MIDI volume plugins. Sort of a "FADER SWAP" mode, if you will.or call it "Fader Alt. Just like the other parameter controllers, that volume stage could be bypassed, and the fader would now control the assigned function. That could work for audio as well as MIDI. Susan, I think it was, had an interesting idea. Like some have said, many VSTi's have more MIDI channels than outputs.something has to get combined. That's only done with MIDI volume, or the overall output volume. Often I'll want a hard attack sample.just soft. Most samplers use multiple velocity-dependent samples. Several people, I notice, are confusing velocity changes with volume changes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |