In this scenario you do not need to mess with the Environment.My question is in using the environment can I automate this and have logic playback in defined order "E1, F1, E1, F1, C1," like a sequencer?
I see, the problem is quite understandable - you just modify the touch tracks (source track) information in real time! That's why Logic stops the monitoring!Problem is that when I do a volume automation on a track, while the touch track is playing, the midi sound stops as soon as I move the slider.
I see your idea. Long time ago (during L5) I developed a small Macro Tool named "Parameter Hunter (PH)" which supports "Learn" feature and "Feedback" feature for such controllers as B-Control. I.e you do not need to create hundreds of faders in the Environment. PH is an universal tool which can be learned very quickly via CC# to a given Logic Plugin parameter and the "Feedback" feature allows you when mouse move some Logic parameter to send that value back to the B-Control as CC# to refresh the B-control knob to that value (Logic CA does not support this "Feedback" feature for B-ctrl, though Cubase does) unless you use something like LC which is not the same.I plan on using a B-control for real time editing.
I'm a very long Logic user (say from the times of the Notator) and I'm not a certified trainer cause I do not need such levels at all. If you are good in anything you can be useful, if not - no certified levels or papers (got anyhow) will make you better...How long have you been using logic, are you an Apple certified trainer?