[bluelion]

Just to follow up with this improvement…

I experimented with the plug-in in Ableton, and I found that Ableton will not save the plug-in window’s configuration parameters if you click the floppy disk icon and save the plug-in’s state. It does save the preset within Ableton in the User Library, which is fantastic.

The easy way to be able to have the same configured parameters included in the plug-in window is to create a set in Ableton with the CRTRL plug-in on a channel. Click the configure button and click away on the panel’s sliders to include them in the plug-in window. Save the project. Now anytime that you want to pull out the plug-in window with all of the automation-enabled parameters in the plug-in window, just find the set you created with the plug-in, and drag’n’drop it into the current project. It should bring the plug-in window just as you saved it in its original set, with all of the parameters “configured” and ready to go!

I super love CTRLR. I’m going to spend some time figuring this thing out and see if I can create a panel for my Roland D-110.

[bluelion]

Wowzers. Thanks for this, Atom! This is going to be the most productive weekend EVERRRRRRRRRR.

Attachments:

You must be logged in to view attached files.

[bluelion]

Hey there,

I really appreciate the work you put into this panel. I’m new to CTRLR but I love the idea of it. That said, I’m not much of a programmer, but I try to see if I can find out stuff on my own before I post on forums. That said…

I tried opening up this panel in Live 9.0.6 in hopes to use the Configure option to use automation from Ableton to control the parameters of the panel/my Alpha Juno-1. Interestingly enough, three parameters are recognized by Ableton as “configurable”: LfoDly, LfoRate, and DcoLfo. When I use the sliders of the configured parameters in Ableton it animates the mapped knobs and relays the appropriate messages to my Juno. So, after spending about a half an hour with a new program, trying to spot the difference in WHY this is happening with these three knobs, I’ve come to the end of myself.

So, señor panel maker sir, do you have any idea why this might be happening? Or rather, if it’s working effectively for these three parameters, what do I need to investigate or update in the downloaded panel I’m using so I can configure the rest of the sliders in the MKS-50 panel?

Thanks for your input,
bluelion

Attachments:

You must be logged in to view attached files.

[Author]

Posts