Filtering MIDI data

hesnotthemessiah · Post by **hesnotthemessiah** » Sun Sep 11, 2005 7:35 am

Hello there. I have been a Cubase VST5 user for a couple of years but switched to Live 5 about a month ago.

1)Does Live5 have a MIDI filter option so that you can choose to filter out certain MIDI data (such as controllers, aftertouch, etc).
2)Does Live5 have any way of preventing the recording of data that is produced when a VST plugin has a parameter changed? I have found that I will be recording to just one MIDI track, say for example recording me playing an Impulse. I then decide to adjust the settings on a VST effect or instrument on another track, such as Vanguard, whilst recording the Impulse on another track and find that, when I have stopped my recording, these adjustments I made to Vanguard has also been recorded. Surely MIDI (or sysex or whatever it is called that is produced when you twiddle with a VST plugin) should not be recorded onto a track unless you actually select to record to the track that the VST plugin device is used on (in this example Vanguard). There should be an option to prevent this data from being recorded - I often twiddle with various VST plugin settings on different tracks whilst recording and I don't usually want these twiddlings recorded.

Clearscreen · Post by **Clearscreen** » Mon Sep 12, 2005 3:01 am

you can filter out notes using the pitch plugin, but controllers etc can't be unfortunately. you could do it be routing you assignments through a midiyoke type of programming and turning that midi track on and off to prevent the data being sent for assignments coming in through that track. may

i'm not really sure about your second problem but it sounds like you're recording into arrangement view. you should be able to disarm the recording input for the tracks you don't want to record to. i don't use arrangement much though, so i'm not really sure about it...

hesnotthemessiah · Post by **hesnotthemessiah** » Mon Sep 12, 2005 4:24 am

Hi Clearscreen. I think I had better describe my procedures where the problem occurs:-

1) Insert VSTi into a MIDI track - for example "Vanguard" into MIDI track named "Vang Bass" .
2)Record notes on "Vang Bass" track and tweak "Vanguard" whilst playing notes on "Vanguard" .
3)Notes and Sysex data is recorded.
4)You have the sound you want from "Vanguard" after tweaking it whilst recording but don't want any of those tweaks you made played back by the sysex data that has been produced. So you need to go back to the track and delete all the sysex data.

A solution would be a button to disable sysex recording which could be switched on/off when recording.

1)Insert another VSTi into another MIDI track - for example "Albino2" into MIDI track named "AlbSynth"
2)Record notes on "AlbSynth" track and tweak "Vanguard" whilst playing notes on "Albino2" .
3)Notes and Sysex data is recorded.
4)You have the sound you want from "Vanguard" after tweaking it whilst recording but don't want any of those tweaks you made played back by the sysex data that has been produced. So you need to go back to the track and delete all the sysex data.

As before, a solution would be a button to disable sysex recording which could be switched on/off when recording. But, in this case, wouldn't it make more sense for Live to only record sysex data onto the track/s that are selected to be recorded onto (in this case only sysex data produced by the "Albino2" should have been recorded onto the MIDI track named "AlbSynth").

You see, my problem is I like to be able to record the notes I play on a VSTi plugin whilst tweaking various other plugins I might also have loaded. An example of this is tweaking a reverb plugin whilst playing a VSTi. I usually don't want the sysex data produced by the reverb plugin to be recorded!! A simple global sysex filter switch that can be switched on/off whilst recording would be really really useful to me plus the option for Live to only record sysex data onto the track/s that are selected to be recorded onto would really be useful. Does anyone else have an opinion on this?

bensuthers · Post by **bensuthers** » Mon Sep 12, 2005 5:09 am

what's sysex data? Ableton doesn't record sysex data; and Vanguard doesn't generate it.

i think you'll find you need to make sure you know what you're talking about first. You should probably read the manual.

hesnotthemessiah · Post by **hesnotthemessiah** » Mon Sep 12, 2005 5:33 am

SysEx stands for MIDI System Exclusive Messages.

Sysex is produced when you twiddle your VST (or Live device) parameters. This is the information that is then used to play back your twiddlings.

Ableton does record sysex data; and Vanguard does generate it.

i think you'll find you need to make sure you know what you're talking about first. You should probably read the manual.

husker · Post by **husker** » Mon Sep 12, 2005 5:52 am

Live doesn't record SysEx... when you twiddle the knobs in your VST, you are recording Live "automation" which has absolutely nothing to do with SysEx.

That might help you to target the correct bit of the manual

hesnotthemessiah · Post by **hesnotthemessiah** » Mon Sep 12, 2005 6:09 am

Hi husker. When you twiddle the knobs in your VST, you are recording Live "automation" which is SysEx.

Due to fly off on my hols today

so won't be able to respond to any replies until a week Tuesday. Wahoooooooooooo!!

rbrown46 · Post by **rbrown46** » Mon Sep 12, 2005 4:15 pm

You might look into using Plogue Bidule to filter your data. Very cool app.

Ryan