Inserting effect on MIDI clip

[rpm]

Since a few versions, it's possible to insert an effect on a single audio clip and this is very convenient.

However, it's not possible to apply an effect on a single MIDI clip. I guess that's because the MIDI first has to go through the sound generator so this is sort of visually misleading (it would look like the MIDI clip is affected first by the clip effect and then the plugin(s) on the whole track).

If it's a good idea, I'd like to put it in here as an FR.

If not, what's the easiest way to add an effect to a single MIDI clip (without having to render the clip to audio)?

[jabe]

What if that clip goes on its own track?

[lay it prodctions]

Since a few versions, it's possible to insert an effect on a single audio clip and this is very convenient.

However, it's not possible to apply an effect on a single MIDI clip. I guess that's because the MIDI first has to go through the sound generator so this is sort of visually misleading (it would look like the MIDI clip is affected first by the clip effect and then the plugin(s) on the whole track).

If it's a good idea, I'd like to put it in here as an FR.

If not, what's the easiest way to add an effect to a single MIDI clip (without having to render the clip to audio)?

You are right. It would be misleading, witch is not the Tacktion way.
Everything is in order from left to right.
From inputs to ouput of each track.
So on every audio clip you add any audio affects or vst's to directly will in terms be affected before any plungins, meters or faders on the mixing channel of that track.
So a midi clip will always be before any vsti plugin or sound generator.
So all effects must be after the vsti plugin.
This makes the most since when you think about it, most effects are audio effects and most midi effects is only a automation to a audio effect being built-in or external effect.
Tacktion just did away with the confusion.
Any effect is post midi clip.
No need to render or you cand render if you like.
I would base rendering on cpu in each edit and hard drive space, but that is another topic.

[Peter Widdicombe]

It's quite logical, if you think about it. For MIDI .vst's, you need to consider the order:

1. MIDI note modifiers, if any (i.e. note transposition, or controller modifiers.filters)
2. .vst effect itself
3. audio effect .vst (reverb, echo, gate, eq... in the order of preference)
4. volume, pan controls

Remember, an audio vst does nothing to midi events, so it needs to be AFTER sound is generated.