08Mar01- Multiple drum lanes with the same sample (but different filter settings, etc) are merged to one lane when saving an xtc clip

I think is is fixed in 09Nov02 beta...

Though:
EQs, Inserts and Sends are not saved with presets and clips.

insertpizhere: delete this post.

i disagree, (or misunderstand)

if i have CC22 mapped to cutoff on synthX on track 1 i want it to record midi from CC22 to sequencer as sequencer playing back recorded CC22 will still control synthX's cutoff, (so its good it still records)

also if i have CC22 mapped it will controll whatever its mapped to regardless to what track i have selected, thus making CC22 of no use to any other plugin,

if i want 2 parameters mapped to CC22 on two different synths i camn do that in the midi mapper

IMO this is the best way,

of course if there is a fix where it can still send the mapped CC data through a plugin to the sequencer but not have it effect that plugin even better,

with no way to disable midi data going to insert FX (Ooooh, must add that to the feedback forum) blocking the mapped CC's is helpful here

feel free to discuss in this thread, i will brake it out to a new thread when its time to clean up this thread

Subz

hmmm... i'll re-word the bug description. one problem is that it records the CC data only in some cases, and so is inconsistent. the other problem is that you can't do any processing of the data when it's used by the controller map. that's based on this thread: http://www.kvraudio.com/forum/viewtopic.php?t=2681 46

i also think this is related: http://www.kvraudio.com/forum/viewtopic.php?t=2681 02
(i.e., maybe it should record the automation curve rather than the CC)

for now i'll change it to this:

09Nov02- CCs mapped to plugins on Sequencer tracks via the Controller Map don't get recorded in the Sequencer unless it is connected directly to the MIDI In.



consider this:

synths A, B, and C will all be automated by CC1 received at the MIDI In, but only B (with the connection directly from MIDI In to Sequencer) gets the CC recorded so that the automation also happens on playback. with C, the user wants the data affected by the midi plugin before it hits the sequencer and synth, but that isn't what happens.

the controller map can control things "remotely" (without an explicit route from the MIDI In), and also through explicit midi connections. if there is a connection from the MIDI In to the automated plugin, i think it should go through the chain before applying the automation, but i suppose that could be complicated to implement.

a feature that would help here is midi insert effects... on sequencer midi tracks and maybe also in the controller map.

having the option for (audio) inserts to ignore midi is a separate issue (i'm voting for it at the feedback forum).

split

you've got a point
It's a very effective way to prevent triggering other plugins in the chain
But I think letting you record data modified by additional plugins first is a very important feature
just for example you may want to make the cc messages a specific channel

I guess you need an option for each mapping to go remotely or through the wiring

another thing: the controller mapping needs a midi ch parameter too - for each mapping - so you can switch channels on your controller and use the same cc# for something different




+1 to midi track insert in the sequencer but you can just put a plugin between seqencer out and vsti in, isn't that the same?

and to record tweaks with modifications AND have remote mapped cc you would need midi inserts inside ccmap right?

Greets, Pete

yes, good point



no, because then you lose the mixer strip and automation of the vsti from the sequencer. the sequencer can't tell that you're using a plugin as a midi effect.


yes.