Tagged: ableton live automation
December 15, 2013 at 11:33 pm #16640
2 part question.
1) I have a panel I’m using (the new Bass Station 2 panel posted to Novation’s forum) When I’m in Ableton Live and set the plugin to configure mode so I can automate values in the panel, Live doesn’t notice when I click or move a knob for this panel. It works in the other panel I tried though (juno 106). Is there something that needs to be added to a control to get it to be recognized in Live?
2) As mentioned above, the 106 panel works with automation, but when click a control it shows a generic title like “automater_4”. Is there a way to configure the panel to have a custom name so I can actually figure out what parameter I’m automating? If not, feature request!.
edit: Nevermind, I figured out how to change the values for question #2. There’s a property called Name (duh). They just weren’t set in this panel. Still learning…
December 29, 2013 at 3:28 pm #17081
- This topic was modified 3 years, 6 months ago by JoeMatt.
Hey, I have the same issue. When I want to learn some controls from my DAW, it doesn’t pick up if I change the value of a knob so it can’t learn the parameter I want to use for automation. Have you figured out what you need to change in Panel mode (besides name) to get the parameter to be learned from the DAW?December 29, 2013 at 3:29 pm #17082
(also using the BS2 panel from the novation forums)January 6, 2014 at 6:26 am #17431
I figured it out. If you click a control in edit mode it has a VST Index value. I’m assuming there’s a valid range that will be accepted here as setting to lower values. The maximum value seems to be 64. I tried the VST and AU wrappers and this applies to both.
I’m not sure if this is a Live limitation, VST limitation or ctrlr bug. 64 seems like a low number so I’m suspicious it’s ctrlr in this case.
January 6, 2014 at 10:34 am #17436
- This reply was modified 3 years, 5 months ago by JoeMatt.
You can change the maximum amount of VST index exports in ctrlr preferences. I’ve set mine to 512 in case 256 is not enough.
www.facebook.com/opuswerkJanuary 8, 2014 at 11:28 pm #17576
The 64 is a default for a Ctrlr started in normal mode, it needs a value. The problem with that number is that the host asks for that number on load and never asks for it again, so you can’t change the number during the panel lifetime AND the question about the number is sent before the plugins state is loaded by the host so you can’t really respond with the correct value.
Anyway you can set the number to something very high (and i can do that in the source code) BUT that makes the load time of an empty Ctrlr significantly longer (enough to be noticed by a normal user).
This limit is not present when exporting an instance, because in an instance Ctrlr knows how many parameters it should report to the host on start (that’s why the instance is embedded inside).January 9, 2014 at 10:57 pm #17627
oh, that’s very good to know.
Do the number of parameters have anything to do with the VST Index number? or is it independent?
www.facebook.com/opuswerkJanuary 9, 2014 at 11:01 pm #17628
The index must be below the max number of reported parameters.
If you report 100 parameters you can’t have index 100 or higher only 0-99 (that’s a hundred parameters starting with index 0)June 5, 2016 at 10:07 pm #69376
Ok, so could someone explain how to solve that in steps?
Ive seen that vstIndex is going up to 650 – so i’ve set in “edit” – “preferences” – “max exported VST params” up to 800 (from 64 what seems default), saved ctrlr state and generated new VST exports, but without any luck in getting live mapping to work.
Or should i rewrite an vstIndex numbers to lower ones (seems “randomly” distributed between 100 and 650)?
Or did i miss something?
Have the same effect in an older SHRUTI ctrlr panel which works otherwise as expected for me. I’m open to contribute my working changes as updates in case i find to there…ß)
many, many thanks for any hint,
- This reply was modified 1 year ago by email@example.com. Reason: just to get notifications
You must be logged in to reply to this topic.