Any Novation Remote SL Users Here?

Yes, yes, there's this thread already.

But what I'm interested in is how well the SL automaps to Reaktor synths, from the synths it ships with to the user library.

Specific questions:

1) Are deep synths like Carbon 2 mapped intelligently?
2) Are things like filters and envelopes mapped to the same place across many different synths so that you don't have to reimagine the parameters for every different one?
3) Do synths with parameter names automatically show up on the Novation's LCD screen?

I ask b/c after having had Reaktor for a year, I've found I don't do nearly enough mucking about with the parameters b/c it's just too much mousing around and/or manual mapping.

Thanks in advance, folks...

 

I use the Remote Sl 25, but have just barely started to dig into Reaktor. As far as I know you'll have to build a custom template on the SL using the midi learn feature or changing it in the Key-control for whatever Reaktor Synth/Ensembles you make. It will not automatically map on its own. Heres is a quote from Novations website Q&A section

"Can I use Native Instruments Reaktor with Automap Universal?
When you load an Automap wrapped instance of Reaktor the controls on the SL will be labeled 'P0001', 'P0002', P0003' etc. These numbers correspond to the Automation IDs of the parameters of the ensemble you load in Reaktor. It is unlikely that the parameters will be mapped intuitively to the ReMOTE SL and you will probably want to remap them. You will also probably want to rename them so you can identify the control by name rather than number. Consequently after loading an ensemble you can 'clear all' controls and start relearning them in a way that better suits you. When you relearn the controls you will see that the name displayed on the SL is now the parameter label as defined within Reaktor and not the parameter automation ID. Note the parameter label is not what it is labeled on the ensemble GUI but is set in the options for that parameter. You may still wish to rename the controls on the SL as the parameter labeling within the Reaktor ensemble may not be simple to understand or there may be parameters with identical labels. You can do this by typing a new name into the name box in the Automap GUI at the bottom of the Reaktor window.

Once you have learned all of the controls for an ensemble or instrument you can save the mapping as a *.automap file by clicking on the Novation logo in the Automap GUI and selecting 'Save...'. The 'Save As Default' function will not be particularly useful with Reaktor because the mapping for one ensemble will not suit any other ensemble. Therefore there is no suitable default mapping, unless of course you use one ensemble more than others. The best system to use is to load an Automap wrapped version of Reaktor, select the ensemble you want to use and then load in the relevant *automap file for that ensemble (if you have created one) by clicking on the Novation logo and selecting 'Load...'."

http://www.novationmusic.com/answerbase/article.php?id=346

 

Good lord.

Thank you for the link. But jeez -- there's really not much "auto" about that at all. You'd think there would be something with respect to the wrapping technology that linked "P0001" with its name. It seems like quite the missed opportunity when you think of synths like Carbon 2, which have so many parameters and so many pages that hardware control would be idea. Oh well.

 

How could it be otherwise? Reaktor assigns parameter IDs in the order in which the control's created, and you can delete and add controls.

ew

 

^ True dat. Reaktor's deeply different to standard VST's - it's a VST inside which is a toolkit for making your own stuff, so it's no surprise that Automap can only go so far.

 

But why would it be so hard for Automap Universal to wrap Reaktor, read the parameter names, and assign them to the the parameter number? Is it that NI wants that stupid Kore controller to itself?

 

Reaktor's different though: I'm not sure if what you're suggesting is even feasible technically, but I bet it'd be hard work, and commercially I doubt it'd be worth Novation's while. We're talking about software which works one way... EXCEPT if the user points it at Reaktor, in which case work in a different, more complex way. Unless R5 had a huge market share, which I don't think it does, there's probably no commercial imperative to let its weirdness ramp up the complexity of their software for everyone.

 

I just realised how weird Reaktor would be from automap's point of view: you were talking about whether filter controls are consistenly mapped... what should automap do if an instrument has 4 filters, or a filter that isn't called a filter but a flubberizer? That's the kind of turn-off from Novation's point of view.

 

Every ensemble has it's own unique set of knobs and buttons and it's completly up to the designer to name them. I can't see how a generic automap fuction could work with that. The best it could do is to match on a guess level.

The only way have usable automap fuction would be if NI added another field to each control (in addition to the existing name field) naming it for the automap fuction.

Not sure if you can make a map (manually) and then share it in the UL e.g. That would be a way to at least minimize the effort within the community....

PS. I don't have a Remote SL...

 

I've never bothered with auto map on the Zero. never bothered to try that function.

'Midi learn' the parameters that you want...it doesn't take that long...once the ens is saved…the midi assignments remain.

 

an old thread i know, but since messing about with this today (for the first time ages) i dusted it down and i've just come to realised how good the Novation remote Zero actually is for reaktor in standalone mode...when using the remotezeroEditor from the website, you just have the controller on the screen and create the 'map' you want for your ens, save the .syx file and upload it to the controller...yes i know i'm very late on the uptake of this, but just thought i'd have a play on it today, and blammo, it hit me with it's brilliance The onboard LCD display is also cool, i don't really need to look at my laptop screen (but i will), all the parameter names come up and it shows their state (buttons/faders/switches).


i wish i'd thought to have used this feature earlier :|

that is all.

 

Old thread I know too... but nothing wrong with revamping them, as long as we move forward.

New Automap is wicked. Is there a way by now to link a name to 001, 002, 003... so it is picked up by automap? Or is it still remember and assign jobby? Thanks!

H