Nektar CS12 strange behaviour

[AlderGrove]

Hi all, new FSP user and forum member here.

I just switched from Logic and set up my Nektar Panorama CS12 for use with FSP. I can't seem to get the insert strip to work at all. Everything else behaves as expected, transport, fader, zoom, markers, even the sends button on that strip, but when I press on any of the insert buttons or the instrument it gets selected for a split second and goes back to unselected. Then if I press a second time it does get selected (white button) but all it does is open the plug-in window on the DAW. Nothing happens on the CS12.
I doubt it's a configuration problem because it would just not work at all.
Also, if I hot-plug or unplug the Launchpad, the CS12 goes into the instrument parameters by itself (which is empty as nothing has been mapped). I've tried changing the connections to different ports in different hubs, or launching FSP without the Launchpad, but nothing changes.
I created a support ticket at Nektar but still haven't heard from them, so I thought maybe someone on here can shed some light.

 

[Skijumptoes]

Presuming you have the latest update from Nektar for the CS12,
Does the plugin window show the CS12 as the currently focused hardware when it opens? (Top right)

Sounds like something else is interfering with the commands it's sending, do you have many external devices that offer deeper integration such as MCU scripts or anything?

 

[Gary Shepherd]

Nektar work well with Studio One and had special software written to tie in with Presonus (and that still works with my T4 now it's Fender Studio Pro). The Nektar website has downloads for support but you could try to contact them if nothing works. It works superbly for me so you should be able to get it working.

 

[AlderGrove]

Thanks for the replies.
The more I test the stranger it gets.
I got a reply from Nektar asking for further details. This is an edit of what I replied:

"When launching Fender Studio Pro the screen displays the Fender Studio and Studio One logos. The ControlCore version is 1.2.9 and so is the Nektar Integration.

Yes, Panorama CS12 has the plug-in focus in all cases.

After some further testing this is what I’ve found:
– Stock plug-ins don’t work at all and display the behaviour shown in the video.
– Third-party FX plug-ins do work. Their parameters are displayed on the CS12 screen and the 12 knobs on the right function as expected, but the strange selection behaviour remains, i.e. on first press it turns white for a split second and gets deselected again, and only after a second press the button stays white.
– Instruments: Strangely enough, only synths by TAL Software and Toontrack work, although not on first press (it shows a blank screen). Only if I open some other plug-in first and then the instrument it will display its parameters on the CS12 screen. The rest of the synths don’t work at all, neither stock nor by Arturia, Cherry Audio or GForce. Worth noting that these are exclusively VST3 versions. I have disabled VST2.4 and AU on Fender Studio Pro’s Preferences."

Let's see how it goes...

I'll post my findings in case someone else encounters the same problem.

 

[AlderGrove]

From Nektar:

"We are currently testing Fender Studio 8.1.1 and I can confirm that there is an issue with plug-in control. We have an active bug report about the problem and our developers are looking into it now.

Hopefully we can find a solution quickly."

 

[reginaldStjohn]

I also have a CS12 and have reported several bugs to Nektar. One of the most annoying is that many plugins will only recognize the plugin mapping for the first instance inserted. Any other instances will go back to a default mapping.

I have been trying to log all the bugs I find with Nektar so their next update will have those fixes.