Ableton Forum

sigabort wrote:It maps unique parameter layouts, so probably not completely, as whilst different Rounds presets have different layouts, they are not entirely unique...

However, if you custom map each preset to a different custom layout then these can be individually mapped in PrEditor

There is, unfortunately, no way to obtain the preset name...

Im also interested in custom layouts per preset. So are you saying that to do this for a vst/au all i need to do is to save the custom layout for each preset
How would i recall the layout for the individual presets in a live situation?

Hi, we're talking specifically about Reaktor/Kontakt here - I'm working on a more general mechanism for a future update...

Hi sigabort,

I noticed in the 1.3.3 video that you are planning to "enable" Komplete Kontrol. Would that lead to Push 2 enabled to control KK?
F.e. browse/up/down/left/right/back/etc. plus the 8 encoders and their page selection? That would be awesome!

Thanks

Hi, no it will just be mapping functionality - it's not possible to control KK directly - best bet is to use AudioModder to import all your presets into Live and then you can browse the content from P1/P2. I'll be looking at supporting AudioModder in PrEditor in an upcoming update...

jestermgee wrote: For a VST when you show how to access more than 128 parameters you show a new mask being created because the configure map is different. Does this mean the masks created are based off the plugin ID + configured controls? This would then also mean you must have the plugin configure map the same for any project for this to be used?

We really need Ableton to get rid of this 128 parameter limit... so many cool possibilities for interesting controllers are limited by it

Ive made 150 + vst push racks try them out here.

https://www.facebook.com/AbletonPushVstRacks/

Tom above is rightly calling for a removal of the 128 limit!

Cheers
D

Does the PrEditor map user made ensembles?

Hi, i'm not sure which manual you have but the latest one clearly details the installation part as the Scripts supplied should auto install if you follow the instructions....

Max can be installed by downloading from Cycling 74, link in the manual, and then a double click on the PrEditor.mxf file will open PrEditor...

If you need anything further please get in touch through the Contact Page on the website choosing the Existing Customer option so we can validate your license...

Cheers
D

Hi Sigabort,

I was just wondering if you could clarify if PrEditor can run on its own as a standalone (no need for Max or Max4Live) or if it needs Max or M4L to run?

I ask because I see conflicting info. The first post of this thread says its standalone but in the help guide it says Max/M4L is needed.

Just curious as only have M4L (with Live 9 Suite) and would like to avoid having to purchase Max at a later date (after trail ends) if I need to make more control mappings.

Cheers!

Hi, Max is used (currently) to host the editor, but is not required once you've set everything up other than to change settings. The actual implementation in Live is independent of this and the next version of the editor will no longer require Max.

Awesome!

Thanks for the quick response. Looks like I will be busy setting up mappings this weekend

S4racen wrote:Tom above is rightly calling for a removal of the 128 limit!

Cheers
D

this!!

same here! too limiting for plugins with a lot of parameters (like Reaktor).

Hi there,

I still on the fence and I was wondering if VST mappings work when changing presets?

For ex. If I have a vst that has only 100 parameters and I setup a mapping for the 'init' preset. Will the custom mapping work when I surf the presets? Or would I need to make a mapping for each individual preset?

I read the manual and watched the videos but was not clear about this.

...the mapping is instrument (plugin) related so you only have to map the parameters once and all presets will represent the mapping...