re. is there a way around this state of affairs, as the "MIDI learn" answer seem to suggest?
yes, being the workaround what has been called "poor man's automation" and in practice way before the TYOQA (but not exclusive to qtractor alone): if you can assign a specific MIDI controller to a desired ZASFX target subject (via MIDI Learn or whatever it may let you do manually), then you can enter or draw a so called pseudo-automation curve as normal MIDI performance data into a MIDI clip, under the designated MIDI controller event type, of course.
the good news are that this kind of solution is similar to regular automation in (sample&)Hold curve mode; the bad news are that all similarities stops there and is not an option ;)
re. is there a way around this state of affairs, as the "MIDI learn" answer seem to suggest?
yes, being the workaround what has been called "poor man's automation" and in practice way before the TYOQA (but not exclusive to qtractor alone): if you can assign a specific MIDI controller to a desired ZASFX target subject (via MIDI Learn or whatever it may let you do manually), then you can enter or draw a so called pseudo-automation curve as normal MIDI performance data into a MIDI clip, under the designated MIDI controller event type, of course.
the good news are that this kind of solution is similar to regular automation in (sample&)Hold curve mode; the bad news are that all similarities stops there and is not an option ;)
hth.
cheers