Panorama cs12 bumpy fader

Cubase
,
1

Hello, I know this is a Cubase forum, but I heard the Nektar rep is active on here, so I was hoping to get some help. I just bought the Panorama CS1,2 and in Cubase 15 Pro, the fader is really bumpy. If I turn off the CS12, the fader is smooth. Also, when I record automation, it records it really jagged and as I’m recording it, I can see it drop out and “miss” a lot. Is this a CS12 issue or a Cubase one?

Thanks!

2

Hi, I would try uninstalling CS12 and reinstalling it. Also, just in case, try CS14. There are no problems here, except that Cubase loses the user assignments. It’s a Cubase bug, of course. You can contact @Tim_Chandler

3

unfortunately for you, I think this is a your problem. CS12 working just fine for me. The fader is surprisingly quiet compared to others I have used, and it is working just fine with automation and no automation - none the issues you describe. I am not a deep user, but when it comes to fader and basic control/editing it have been super solid. And even the mid remote has been flawless for me, unlike my 2 other midi remote devices.

do you have latest hardware update and drivers?

4

I know you have the Novation SL MK3 too. Have you observed inconsistencies in CB15? I haven’t tested it there, but it should work at least as in CB13-14.

5

the scripts works very good @m.c - I have noticed the times I loose it is when I load up older projects. Then I need to remove the script and re import it. It is done in a snap as I have it saved on a external drive and the script is back to working. once the project is saved in a “new” version number format Cubase remembers it.

1 Like
6

Yes, the known issue with MR, due to saving inside a project. This can occur either when port names change or whenever we may have project-dependent mappings. Do you have any of these mappings?

7

I am not sure what you are talking about here. I used a Native Instruments S49 before, then I switched to the Novation around Cubase 14.

8

Talking about altering a control assignment, from the one included in the script, with a project specific assignment, for example, the CutOff of a VST. I guess you haven’t.
Could you do me a favour if you have some time?

  • Open one of your projects with this problematic behaviour.
  • Delete the script using the trash icon as shown here:
    εικόνα
    εικόνα347×292 20.1 KB
  • Now, go to your [documents folder]/Steinberg/Cubase/MIDI Remote/User Settings , and find a file named similarly to this: Novation_SL_MK3_MC_Custom_3004242C6915D7C657343C2844C47731_globalmappings.json
  • Delete this file.
  • Now, restore the script as you normally do by re-importing it, and save the project file. Close Cubase.

When you reopen this project file does the issue persist?

EDIT: I’ve just now noticed that this thread is about the CS12. My apologies. Please @glennloopez , let’s continue using a pm or the SL MK3 dedicated thread, whenever you have the time.

9

Hello, Nektar support is your best call here, it is not a Cubase or integration issue.

You should however check the latest firmware is installed. Current CS12 FW version is v01.02.02. You will see the FW version displayed on the welcome page when Steinberg is opened with the CS12 connected.

This is really great to hear, thanks!
A lot of work has been done on improving fader functionality and accounting for different environmental factors.

Best,

Tim

10

Thanks, all. Sweetwater is doing an exchange for me, and I’m going to uninstall the software and do it all over again.

11

@Tim_Chandler I got my CS12 replacement, and it’s doing the same thing but worse. I’m convinced it’s most likely user error or least likely a Cubase error. When Cubase is closed, the fader is smooth. When Cubase is open, and I write automation, the fader stops in increments. Let me upload 2 videos, the choppy fader is with Cubase open, and the smooth fader is with it closed. What am I doing wrong?

12

@Tim_Chandler and here is with Cubase off.

Firmware and everything has been updated. The second I open Cubase, the fader gets choppy. I opened up a blank project and tested it out. It’s smooth until I record the animation, then it records jagged and you can see the red color cuts out periodically as I record. Video is longer so I had to upload it to Google drive - @Martin.Jirsak

13

Hi esimone00,

I can’t be sure, but I think the touch element on the fader is not read correctly, which can happen due to grounding issues caused by external factors, studio setup, interference.

We’ve only seen a handful of such issues with CS12, but it was enough to diagnose the problem and be able to help the customers affected. It’s an isolated case I’m afraid, so you’ll need to contact support who will take you through full diagnostics and can provide a work around.

There’s not much I can do on my end.

Best,

Tim

1 Like
14

Ahh ok, strange as this is my second unit. I emailed Nektar support twice and no response. I’m not sure what to do here.

15

Sure, but if the factors are due to external interference causing grounding issues a different unit will exhibit the same problem.

I will chase up your case with support, what is the case number?

16

ok thank you! #13733

Oddly enough, all my other control surface faders work perfect.

17

So the knobs are recording in choppy automation as well so I can’t imagine it being the touch sensitivity on the faders. Perhaps it’s an issue with the communication between Cubase and the device?

18

Just wondering if there may be any relation with this issue:

@Tim_Chandler perhaps you’d have some time to look into this, just in case?