Please note that we are mainly interested at this point in major/critical level testing and reports:
Thank you !
Hey Gil,
When using Editor(0.9.37) with Ableton (9.5) I noticed that when the LFO’s are synced, moving the LFO Rate knob on the hardware doesn’t affect the actual LFO Rate – the clock sub division changes in the bottom panel, but the LFO Rate knob in the software does not reflect the movements of the hardware. When not synced, the hardware affects the LFO Rate as it should.
Moving the LFO Rate knobs in the software when synced changes the clock sub division and affects the LFO Rate. It seems to just be a communication between hardware and software when the LFO Rate is synced, as opposed to free.
This is accurately reflecting what is happening on the hardware… when LFO Sync is on, turning the LFO Rate knob only affects Clock Division, it doesn’t adjust Rate. So the MIDI output from the hardware to the Editor is the Clock Division MIDI CC, not the (free-running) LFO Rate CC. So, the editor is showing you changes to the only parameter that is really changing at this time.
Part of the confusion here is due to the early decision to have two different parameters / CC numbers, one for free-running LFO rate and a separate parameter for Sync value… this is confusing when there’s only a single knob controlling one parameter or the other depending on Sync state.
I had a similar issue in Logic…, LFO1 didn’t respond on the plugin.
I then closed Logic and reopened the standalone version. Neither LFO1 or LFO2 would respond.. nothing was synced. Clicking on one of the LFO sync buttons on the editor on then off resolved the issue.
I’ve not been able to duplicate this since.
FYI the clock div parameters were changing on the editor, as if it was in sync.
V9.36
Edit
After installing 9.37 it happened again… LFO 1 was acting as if it was synced. Switching sync on and off didn’t fix it, but changing patches eventually did.
Hey Amos,
Thanks for clearing that up. I’m still having a bit of weirdness related to the Editors LFO’s in Ableton – using Editor 0.9.37 (VST and AU) with Ableton 9.5 (I haven’t updated to 9.6). Hopefully you can reproduce this… or someone else to confirm.
Steps to reproduce:
(1) Twist LFO knobs on hardware — accurately reflects in software.
(2) Press Sync LFO and twist knobs — accurately affects the clock division.
(3) Press Sync button to disengage — continues to affect clock division … except values skewed.
Steps to reproduce:
(1) Create MIDI track, load Ext Instrument device, load Editor, setup routing
(2) Group Ext Instrument and Editor to create Instrument Rack
(3) Click ‘configure’ on Editor, toggle parameters on Editor GUI, click configure to exit.
(4) Click ‘map’ on Instrument Rack, click each Editor parameter, then map to Macro’s (1 thru 
(5) Go into ‘MIDI map mode’ in Ableton, assign Macros to Livid Code V2 knobs (any controller I assume)
Result:
(1) Free LFO responds normally — knob responds and sound is affected by LFO
(2) Sync’d LFO does not respond — knob moves, but sound is not affected.
Inconclusive:
Number 2 seems to have something to do with the two parameters for the sync value, where the knob isn’t actually connected to the clock division. If that’s the case though, I can’t figure out how to setup the clock division in this fashion with the Macros in Live. In other words, I can’t click ‘configure’ and then toggle a ‘clock division’ parameter to appear in Ableton’s list. Also, at one point nothing responded when No. 2’s setup was used (VST), but I wasn’t able to reproduce it.
Yesterday my sub37 a note hangs. I don’t know why. Did have this behaviour with earlier versions. When trying to hit al notes on the keybed it still hangs, and plays the note continiously. Also with program change it still hangs. Only sollution is to reboot the machine. Can’t give more info, but when it occurs again I will report back.