Full Nektar support for Studio One now available plus the new Nektarine tool

[jens]

As I mentioned, only the plug-ins which are included with Studio One have been mapped for use without Nektarine. You can still control third-party plug-ins without Nektarine but you are limited to one page of parameters.

When it comes to Studio One's control link system, we need to present Studio One with a fixed array of controls. This means we can't create an arbitrary number of pages, depending on the number of parameters a plug-in has (as we can with Nektarine). Still, I find the control link system is very well thought out. It's much better suited for on-the-fly mappings than many other DAWs.

I totally understand that there are much more useful ways to map the Fat Channel and other plug-ins but we chose to map the controls which are visible as soon as you create an instance, so that you can immediately see what is being controlled.
It can become a big support issue if the controls map to parameters which are not visible by default.

They're certainly not always visible in Reason either, which didn't stop you in this case. And anyway, visible or not: the name should give it away: "comp" and "EQ". If someone looks at the gate and wonders why the "Comp" parameters aren't doing anything that person will probably be a huge support issue anyway...

Ultimately, you can choose which parameters are mapped and when you change the mapping for one instance, it will apply to all others. Think of the mapping which we provide as an example of what can be done. I hope that makes sense.

Sure, but it's not nearly the same as having at least the comp and the EQ available directly on the top Mixer level. As soon as you have to move a few levels further down, using the hardware-control becomes less of a help when it comes to working fast and spontaneously.

B.t.w.: why can't I move along the insert slots using the DATA wheel (which serves no other function for this level either)? It's these little things combined that make or break a great integration.

[jens]

If the message appears in Panorama's display, when a plug-in window is open, it likely means that the 'Panorama' device is not in focus. At the top-right of each plug-in window, you should see this:



If you see a different controller listed in that yellow box or if the box is grey, Panorama will not be able to control the plug-in. You will need to make sure that 'Panorama' or 'Panorama T' are selected there (not 'Panorama Keyboard' or 'Panorama T Keyboard'). You can select which device is in focus by clicking the down facing triangle next to the yellow box, then choosing a device from the list.

That's basically exactly what was happening here - thanks!

[justin3am]

B.t.w.: why can't I move along the insert slots using the DATA wheel (which serves no other function for this level either)? It's these little things combined that make or break a great integration.

Currently the data encoder is used for auto-assignment function. I'd be happy to create a feature request.

Regarding Reason, you will see 'No Instrument' anytime you have selected a device which we have not mapped. Reason's system is quite different from most other control surface APIs. If there isn't a scope in our remotemap file for a given plug-in or RE, we cannot control it. In other DAWs, we can access parameters for a plug-in even if we don't provide a default map.

Every DAW has it's quirks and compromises when it comes to control surface integration. We try to explore everything that is possible within a DAWs control surface API and implement as much as we can within the scope of each controller. Sometimes we find that we can't make everything work the way would like (otherwise, our DAW integration would work exactly the same in every DAW) but we always look at those cases as a challenge, a puzzle to solve.

This is all to say, "I hear you". While it may seem like I'm dismissing some of your comments, that definitely is not the case. I've discussed your comments with my colleagues and those discussions may lead to changes but it should also be clear that there are reasons why we chose to do things, that may not make sense at first. In any case, I do appreciate your honest feedback. It helps us to make our products better.

[rodanmusic]

This is just amazing integration.

Now I can use both Bitwig and Studio One with full integration.

Easily the best keyboard controller out there imo (P4).

Thank you so much for this awesome integration.

[reggie1979]

Nektar are terrific.

[rodanmusic]

Two questions.

1. Do the pads work? I can't seem to get my pads to work with impact even though they're on the proper keys. I can't see anything about them in the manual.
2. Is it possible to reassign all of the faders? I would like to assign something like: first 4 to pitch, second 4 to filter, and the knobs above them to adsr. It kinda seems to work, but then it resets the assignments.

I don't know if this is possible with the current setup, but it would be cool.

Thanks again!

[ShawnMH]

My track volume fader (numbers) and panner position (L/C/R) on Panorama P1 screen are not changing with adjustment, only showing in upper right corner of screen.

The sliders and knobs do show movement, and work correctly on S1 side of it, although I cannot adjust panner back to <C> - only L0 and R0.

Anything known that would cause this?

I have the original P1 S1 mapping template from before, is this going to cause any problems?

[dellboy]

My track volume fader (numbers) and panner position (L/C/R) on Panorama P1 screen are not changing with adjustment, only showing in upper right corner of screen.

The sliders and knobs do show movement, and work correctly on S1 side of it, although I cannot adjust panner back to <C> - only L0 and R0.

Anything known that would cause this?

I have the original P1 S1 mapping template from before, is this going to cause any problems?

The instructions say to do a factory reset and remove the original folder from C:\Program Files\PreSonus\Studio One\devices.

Remember to do a backup if you want to keep your memory banks.

[ShawnMH]

Ok, thanks for the reply.

I was thinking this was the answer, but was avoiding it due to all of my other DAW installations on/with the P1.

[dellboy]

Ok, thanks for the reply.

I was thinking this was the answer, but was avoiding it due to all of my other DAW installations on/with the P1.

I was concerned it would wipe out my Cubase maps,but somehow they are intact, no idea how though.

[ShawnMH]

Just did the reset, and all of my controls still work for: Cubase 9.5 Pro, Reason 10, Cakewalk/Bandlab, Reaper, and Mixbus 5

Strange. I am going to re-update the firmware with the Presonus update (although I should see if that works now as is ?!?!)

[ShawnMH]

Okay, so factory reset and reloaded the firmware, re-installed S1 integration software, and all is the same with the onboard P1 screen's panning and fader levels (L-C-R/numbers).

If I switch to Transport mode and back, they update.

"Known issues" describes a similar scenario (maybe the same?)

[jens]

B.t.w.: why can't I move along the insert slots using the DATA wheel (which serves no other function for this level either)? It's these little things combined that make or break a great integration.

Currently the data encoder is used for auto-assignment function. I'd be happy to create a feature request.

After reading the manual I realized that I can hold down the next or previous button in and the encoder will scroll through the list. Not quite as immediate but a lot better than I thought.

I'd still prefer though if the insert-list would automatically get the focus of the data encoder. If I browse through the inserts I am currently not tweaking any parameters so yes, I'd love to request that.

Regarding Reason, you will see 'No Instrument' anytime you have selected a device which we have not mapped. Reason's system is quite different from most other control surface APIs. If there isn't a scope in our remotemap file for a given plug-in or RE, we cannot control it. In other DAWs, we can access parameters for a plug-in even if we don't provide a default map.

Every DAW has it's quirks and compromises when it comes to control surface integration. We try to explore everything that is possible within a DAWs control surface API and implement as much as we can within the scope of each controller. Sometimes we find that we can't make everything work the way would like (otherwise, our DAW integration would work exactly the same in every DAW) but we always look at those cases as a challenge, a puzzle to solve.

Yes, I bet that can be quite a challenge. It would be great if there was some kind of a standard, if and where possible and sensible.
(E.g. there's a few times of tracks and items and all DAWs have a least some of them and the same goes for inserts and sends so could they not share the same control command (whatever type of message that may be) for adding them and the same protocol for reporting them? They all cut and add items, they all have a timeline and those items sit on tracks on this timeline, yadda yadda - but perhaps that's just me being naive - in any way it exceeds the scope of this thread and perhaps I should start a new one about this.)

This is all to say, "I hear you". While it may seem like I'm dismissing some of your comments, that definitely is not the case. I've discussed your comments with my colleagues and those discussions may lead to changes but it should also be clear that there are reasons why we chose to do things, that may not make sense at first. In any case, I do appreciate your honest feedback. It helps us to make our products better.

You know, I think considering my own tone here I think you've been more than friendly, polite and open. Hats of to you for remaining a better gentleman than most and certainly a far better than I could ever dream of becoming.
And someone who is as blunt as me really shouldn't be overly sensitive.
But I am really happy if you consider my suggestions/comments.

[Roman Wisniak]

Komplete Kontrol would be good if it had sliders. I love that feature on my P6. I use it with Nuendo and it is a great integration (also with Reason). If Komplete Kontrol had more knobs and sliders I might bite that bullet (cause I think it integrates with Nuendo).

Am I off topic? heh.

Komplet Kontrol has sliders when you use it with Maschine Jam. Imho this it's the best implementation of sliders I've ever used.

[zyguli]

Is Nektarine supposed to work correctly within Cubase 10 at this point, because my P6 doesn't display the same parameters as Nektarine?