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

[rodanmusic]

It's out now! I will test it tonight.

Thank you so much for this. If the functionality for the P4 is the same as the T series then this will have made my Atom redundant.

I do have one question about Nektarine.

Has any thought been given to what happens when Nektarine is no longer updated or supported?

When i used Novation's similar solution Automap, years later down the road, i lost many settings for synths that were loaded inside of the automap software and wasn't really able to recover them.

I don't know that there is any solution to that problem, but I was just wondering what happens when the software no longer works and all we have are the original virtual instruments.

Either way I'm still super excited to use it.

[dellboy]

Its nice to get a free update for my P6, thanks Justin.

I have all of the Studio One instruments working, but no success with non-native VSTs. You can click with the mouse to gain focus and then use the panorama knob to adjust different parameters though. I notice it always says "learn" in the screen, so I guess its a matter of reading the instructions.

[WasteLand]

It's out now! I will test it tonight.

Thank you so much for this. If the functionality for the P4 is the same as the T series then this will have made my Atom redundant.

I do have one question about Nektarine.

Has any thought been given to what happens when Nektarine is no longer updated or supported?

When i used Novation's similar solution Automap, years later down the road, i lost many settings for synths that were loaded inside of the automap software and wasn't really able to recover them.

I don't know that there is any solution to that problem, but I was just wondering what happens when the software no longer works and all we have are the original virtual instruments.

Either way I'm still super excited to use it.

automap still works. even without a supported DAW, for example maschine...
i must make your own automaps, it is still supported, there is a beta for live 10 and cubase 10, but that integration is more mixer and or stuff.
but automap i work with it daily...

i have also the panorama p1, which i like, it is in a way a better solution than automap, but there integration works another way, so it is for cubase, for instance, not deep anymore, not even close.
for reason 10, it is a feast. the panorama p1 (or p4/6) can be unleashed, they have more power to control what you want than NKS. automap is also powerfull, but no menu structure, and you can't program a page, that an encoder changes, in functionality, the page changes.

by the way, i can use nektarine. i talk with support sometimes about the status for cubase.

i am glad to see that they are still developing.

but again back to automap: it still works, and it great.

if you see how you can control reason 10, with user community mappings, every rack, and many vst's... and nektarine, the editor shows the power of the controller.

[rodanmusic]

It's out now! I will test it tonight.

Thank you so much for this. If the functionality for the P4 is the same as the T series then this will have made my Atom redundant.

I do have one question about Nektarine.

Has any thought been given to what happens when Nektarine is no longer updated or supported?

When i used Novation's similar solution Automap, years later down the road, i lost many settings for synths that were loaded inside of the automap software and wasn't really able to recover them.

I don't know that there is any solution to that problem, but I was just wondering what happens when the software no longer works and all we have are the original virtual instruments.

Either way I'm still super excited to use it.

automap still works. even without a supported DAW, for example maschine...
i must make your own automaps, it is still supported, there is a beta for live 10 and cubase 10, but that integration is more mixer and or stuff.
but automap i work with it daily...

i have also the panorama p1, which i like, it is in a way a better solution than automap, but there integration works another way, so it is for cubase, for instance, not deep anymore, not even close.
for reason 10, it is a feast. the panorama p1 (or p4/6) can be unleashed, they have more power to control what you want than NKS. automap is also powerfull, but no menu structure, and you can't program a page, that an encoder changes, in functionality, the page changes.

by the way, i can use nektarine. i talk with support sometimes about the status for cubase.

i am glad to see that they are still developing.

but again back to automap: it still works, and it great.

if you see how you can control reason 10, with user community mappings, every rack, and many vst's... and nektarine, the editor shows the power of the controller.

It's been a long time since I used it. I just remember that i had to re-apply the automap software to all my vsts again, and then when I did that it created duplicate versions of the actual vsts wrapped by the automap wrapper. As a result none of the previous automap vsts in a project would load the correct synth and parameters because on disk they were actually different vst files. Maybe they've fixed or changed it now, but this was a long time ago...back when nocturn came out....around 2009 i think?

I imagine the nektarine software doesn't work like that...probably just loads the vst inside of it without creating new .vst files.

[reggie1979]

God I hated automap

[WasteLand]

It's out now! I will test it tonight.

Thank you so much for this. If the functionality for the P4 is the same as the T series then this will have made my Atom redundant.

I do have one question about Nektarine.

Has any thought been given to what happens when Nektarine is no longer updated or supported?

When i used Novation's similar solution Automap, years later down the road, i lost many settings for synths that were loaded inside of the automap software and wasn't really able to recover them.

I don't know that there is any solution to that problem, but I was just wondering what happens when the software no longer works and all we have are the original virtual instruments.

Either way I'm still super excited to use it.

automap still works. even without a supported DAW, for example maschine...
i must make your own automaps, it is still supported, there is a beta for live 10 and cubase 10, but that integration is more mixer and or stuff.
but automap i work with it daily...

i have also the panorama p1, which i like, it is in a way a better solution than automap, but there integration works another way, so it is for cubase, for instance, not deep anymore, not even close.
for reason 10, it is a feast. the panorama p1 (or p4/6) can be unleashed, they have more power to control what you want than NKS. automap is also powerfull, but no menu structure, and you can't program a page, that an encoder changes, in functionality, the page changes.

by the way, i can use nektarine. i talk with support sometimes about the status for cubase.

i am glad to see that they are still developing.

but again back to automap: it still works, and it great.

if you see how you can control reason 10, with user community mappings, every rack, and many vst's... and nektarine, the editor shows the power of the controller.

It's been a long time since I used it. I just remember that i had to re-apply the automap software to all my vsts again, and then when I did that it created duplicate versions of the actual vsts wrapped by the automap wrapper. As a result none of the previous automap vsts in a project would load the correct synth and parameters because on disk they were actually different vst files. Maybe they've fixed or changed it now, but this was a long time ago...back when nocturn came out....around 2009 i think?

I imagine the nektarine software doesn't work like that...probably just loads the vst inside of it without creating new .vst files.

nektarin is a pluginhost, for more than one, even. do you call it a pluginhost plugin?

never noticed problems, when changing to none automap dll's, in projects. they are still wrapped, sort of duplicated, not really of course, it are the automap enabled plugins. vst3 versions are also wrapped, but that works better, i.e. they are shown to the host with the normal names/ID.

sometimes, when updating or installing new plugins, it is easier to disable all automap files. and cubase has the hickup, if i do not do that, sometimes. that is another "problem". the workaround is simple and after that it works flawlessly, most of the times..

when the plugins where automapped, cubase loads the non automapped plugins without problems, with the same settings. never experienced what you have experienced. i use it for 3 or 4 years, do not know exactly, perhaps something is fixed....

so sometimes when i disable the automap wrapper, via the automap server for a particular plugin, it loads with no problems, i enable it again it works again. i shall try it, perhaps i am wrong, but never lost a state of a plugin.

but this is not an automap thread.

it is a thread about controlling DAW's, and plugins. i have the Obsessive Tactile Controller Syndrome, many controllers, some dedicated. the hardware feel, tactile... i am wondering how many people are looking for that kind of control... it seems only it can be achieved, by having more than one controller...

great that nektar still goes foreward with there panorama p1, i expect much of it...

[WasteLand]

God I hated automap

many do, and did. i like it.............. it works......... 8 encoders, 8 knobs, 8 faders, 32 buttons per page (and the buttons can be in step mode, for example: an LFO type, step right through it. a button is more then a toggle, can also be momentary...) ow well....

[chk071]

God I hated automap

No wonder.

[rodanmusic]

I can't wait to get home to play with this.

[reggie1979]

God I hated automap

many do, and did. i like it.............. it works......... 8 encoders, 8 knobs, 8 faders, 32 buttons per page (and the buttons can be in step mode, for example: an LFO type, step right through it. a button is more then a toggle, can also be momentary...) ow well....

It always had a mind of it's own when I used it. It's been some time.

[EnGee]

I uninstalled Nektarin as I don't need it in Bitwig (integration is already supa dupa!), but the new firmware update is great! I can use the other modes in other DAWs now which wasn't the case before.

I didn't test other DAWs extensively, as I was busy making some beats with Bitwig after years of inactivity! But I'm sure that Nektar team with Justin will iron all the bits. The start is very encouraging

[elnn]

Looks great, timed even better –– and just as I was getting ready to switch from Logic to S1 and put up my P4 for sale:)) you're staying, babe.

Does Nektarine give all hosted plugin parameters for automation?

[jens]

Regarding Fat Channel... it presents a different set of parameters, depending on which stage is selected and which model is active for that stage. We thought it was best to map the parameters which appear by default when you create a new instance, so that you can see what the controls are doing. It's very easy to change control assignments using the control link system. The user guide described the process.

I was hoping for something similar to what you did with Reason. Perhaps it's just technically not possible to get the controls updated depending on the selected model and that is the problem/ reason why you didn't do it (even if it would come as a big surprise to me if that technical restriction existed, given the fact that it works in other places) but it's certainly very disappointing for me. You have only mapped the Gate btw. (perhaps for the same reason) which is probably for most users by far the least used processor of the strip.

A plugin channel-strip with direct hardware control is certainly something that a lot of people find very desirable. It's exactly what Softube are selling with their Console 1.

And especially because the Fat Channel can a) load different modules which b) rival high quality VSTs soundwise this would make it very attractive. If the mapping was sensible (e.g. with the TubeComp map gain to the encoder which controls threshold on other comps and peak reduction in place of ratio etc.) you could have had a real winner - all imo.

[dellboy]

Starting to get the hang of this now.

The Studio One plugins work out of the box, but other VSTs need Nektarine installed to gain access to all the parameters.

Anyone get patch change to work in Nektarine ?

[justin3am]

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. 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.