There have been some major changes made in on this version so please test it carefully, as for now it should really be our release version.
Main fixes:
Should solved Ableton automation issues
Tuning changes when moving SUSTAIN
Automation recorded values in Logic
If this version is found to introduce some new issues, or doesn’t work well enough, we will go with the recent 0.9.47/1.1.25 for 1.0.0 and keep on fixing to 1.0.1.
Your feedback regarding this version’s stability is highly important to us, so please try to feedback on it with your impression in all aspects.
Well with this update i am still having the automation issue and it stop recording automation after only one lane dropped down. I have noticed that when it stop recording automation if i am recording knob movements in real time they then get passed as “midi ctrl” messages in the clip’s envelop section.
I am curious to know what happens if you also map the hardware knobs to the plugin UI knobs using Live’s MIDI mapping mode. This should prevent the knob movements from being recorded as “midi ctrl” messages.
To do this, open the editor plug-in UI, type control-M (command-M) to enter MIDI mapping mode… click a knob in the plug-in UI and then turn the corresponding knob on the hardware to create a mapping. You can map as many knobs as you want this way. Press ESC when you’re done.
Then try recording automation for the knobs you mapped and see if it behaves better than un-mapped knobs… let me know if it behaves well enough to be musically useful. Thanks very much!
Very little thing on OSX (maybe something for the marketing department): I think the stand alone app launch icon could be a bit prettier: it is now a white square with the Sub…
Yes if i midi learn the knob to the gui it does prevent them from being recorded as “midi ctrl” and keeps them recording as automation. It also prevents the “automation line stops following knob movements” problem but then the problem is still having to "midi learn’ a knob i want to record which slows down workflow and can be disruptive considering it functions correctly for a bit. It is fine for a “workaround” now.