Hello @Tim_Chandler. There still seems to be a problem with the German Cubase version: Cubase sometimes hangs on startup. If I then remove the USB cable from the CS12, the Cubase start continues. This problem does not occur when I switch Cubase from German to English.
What else I have noticed: 2 Nektar panoramas are displayed in the Midi Remote Panel. One active and one inactive. If I delete the inactive entry, both nectars are removed. Is that normal?
Hi,
If you are on Windows, could you please make a DMP file, to get more info about the hang?
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the Microsoft ProcDump utility to generate a DMP file, please.
-
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
-
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
-
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder. -
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).
-
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.
- Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or a similar service, please.
After I replaced the USB cable, there are no more problems starting the German Cubase version.
But I noticed another strange behaviour. With some Cubase songs I can select the plugin on the CS12, but the controls on the right-hand side remain dark and no parameters are shown on the CS12 display. What does work, however, is to open the plug-in window using the button on the CS12.
This behaviour only occurs with certain songs. With other songs, everything works as it should.
I even deleted all tracks and plugins in the affected songs and only created a new track with a single Cubase Compressor plugin. The behaviour remains the same - the compressor parameters are not displayed on the CS12 and the controls remain dark.
1 Like
Bummer if that behavior is universal
This sounds like an api issue Steinberg have fixed on their next update. The problems tend to start when switching and activating projects without shutting Cubase down in between. You can try starting Cubase, opening the project with cs12 shutdown, then changing tracks and then turning cs12 on after everything is up and running to get things working again.
1 Like
The majority of plugins respond to the click, since otherwise and initial value would not trigger an automation point. I’ll take a look at the plugins mentioned and see what can be done.
With the mouse over method, many plugins particularly vst instruments don’t support it - that means the control wouldn’t work at all not even after a value change.
Unfortunately, this does not work for me. I can’t edit the plugins in certain songs with the CS.
Is it correct that I have 2 Nektar entries in the Midi Remote Panel?
I don’t know why 2 surfaces appear, some api issue I guess, but it’s fine to just delete the redundant one.
Pm me with a video of the issue if you want and I’ll take a closer look Monday.
1 Like
There might be a chance to circumnavigate the limitations of these plugins but it is not a sexy one.
Most likely the learning will work when you use the Generic Editor of the plugin. You will need to click the turqoise value bar underneath a parameter in order to register it.
I mentioned it here for another issue:
I understand the Generic Editor is not appealing in many cases but maybe it helps you with your plugins. Especially since you’ll have to do it only once per plugin.
@Tim_Chandler FYI.
2 Likes
Thank you for your reply.
No mixer mode for CS12 seems like an unfortunate omission. Are there any plans to implement it?
Are there any plans for updating the Cubase integration of Panorama P6? Currently there are only 8 insert slots reachable from the device. An integrated Control room and channel strip control would be welcomed as well.
Hello,
I am having the same problem with my CS12, I’m in the middle of mixing and during one day session the right side went dark. I did not jump between sessions with deactivating/avtivating but closed one session to go to another one.
Apart from this I am super happy with the CS12, what a great product! I am confident this will be fixed asap, right?
News: today, I found by chance the ControlCore version 1.1.9 released to the NektarTech website. Have not tested though.
1 Like
yes. happens to me from time to time too. when you change the project it loses the connection
Yes, just downloaded and will check out tomorrow! Hopefully it will fix the bug
This is just not working for me. It’s all installed correctly.
Basics work, that is left hand fader and controls, 18 buttons for markers and basic functions. When it comes plug in side nothing seems to work as you would expect.
So I go from a chord track (could be any track just wanted to see the plugin buttons dimmed). Whilst on the chord track the sends and channel buttons are a white colour and the CS12 displays no mix channel. Whilst still on chord track if I press the sends button, the display displays send at the top of the screen and two soft buttons now show level and pre/post. The sends button is now brighter than the channel button. Pressing sends again does nothing. pressing the 9-16 buttons shows 1 to 9 on the display and now sends is same brightness as channel. This is probably all how it’s supposed to be but I would rather the display show the name of the track and the fact that no options are available.
Or is it the case that I can actually program the pots and RGB buttons for commands whilst on the chord track?
So now I choose an instrument track. The track has 3 inserts and 2 sends. Track title is named KK Battery Kick. The sends button is now bright white, the channel button is turquoise. The plugin buttons are 3 different colours. They are brightly lit to indicate the inserts are active. I can de activate each plugin with shift and the corresponding button. Now what doesn’t make sense to me is that the display is showing sends and shows the levels for the 1 and 2 slots, despite the plugin buttons remaining coloured to indicate inserts 1 to 3. At this point the M£ plugin button does nothing. As I have not chosen a specific insert plugin, I would like to see this open the instrument plugin. it does not even with shift. Also for some reason the display is now showing 136 clap where it previously said sends. This is a drum track but no idea what that means?
So I now press 1, 2 and 3 and the do=isplay hi lights my choice but does nothing else. I was expecting the pots and RGB buttons to become active.
This is where things don’t work or work as expected. The manual says press the 9-16 button anytime to see the plugin list.
So until I press the 9-16 button I can happily press each of the 3 insert buttons and they are highlighted with a box around them on the display. (nothing else happens, the pots don’t light up as if to let you control an insert plugin.
At this point the send and channel buttons are lit an aqua colour, I assume this means neither is selected and therefore inserts are selected. This is not clear to me. if I now press the 9-16 button, even though I am already viewing the plugin list, the display goes back to showing track name and 136 claps. If I press 9-16 again the plugin list appears again. All well (other than the fact at no point have any of the pots lit up or the display changed to show I can control the plugin). Now when I try to select one of the the there inserts weirdness happens. I press insert 1 and nothing happens at all, insert 2 is highlighted and remains highlighted. insert three which is an aqua colour on screen and the button previously matched, now has a white button and when pressed it closes the display back to the track details. three insert buttons still lit but number 3 is still white. pressing the 3rd white button does nothing. Sometime one of the inserts will change to a white button, the display still shows red and the insert can not be selected on the display . Despite this the correct plugin opens. So this is totally not working.
When pressing the sends button it changes white and the sends levels are on the display and pots are active to control. However the same three insert buttons are lit up. I thought pressing the 9-16 would show the sends and buttons would light up?
pressing the channel button simply shows the word user 2 on the screen. the two soft buttons show Q ctrls and eq, the channel button remains aqua and does not change to white. Again no pots are available for use, until Q ctrls is pressed and 8 are available. EQ activates the pots and RGB buttons. Enough for now my head hurts.
If you are on the chord track, your behavior is absolutely correct. The chord track has no sends. It is the same for me. Of course it would be better if the word sends was not on the display, but anyone who can use Cubase knows that the track has no sends. I see this as a minor flaw.
I also think it makes sense that the plugin buttons are colored when you are in send mode. That way you can see which type of plugin is in the respective insert slot and access it from send mode. I think that’s very useful.
If you press channel and user1 is there, then you were already in channel mode and selected user1. In channel mode, the page you selected at the end always remains active. So if you are in the EQ window in channel mode and then switch to the send mouse and then back to channel mode, then you are in EQ mode again. I personally think it’s great
I admit, however, that at the beginning I was very confused about how everything was connected.
Especially since sometimes things didn’t really work. But I think it’s been fixed since the last update.
Perhaps you could make a video about the rest of the plug-in potentiometers
would be nice to know what was fixed in the new update
I installed the latest update yesterday and since then the colors I assigned are no longer correct.
I assigned dynamic plugins pink. Some plugins are shown in pink in front of the name in the display but the insert button is red…???
Yes that’s a good point. I use the generic remote editor all the time with the Twisters but didn’t think to see if there is a connection with the CS12 since it seems to have left all the generic remote mappings alone. In all fairness to Nektar, as I remember, plugins like the brainworx stuff can’t even be learned in the generic remote editor, they have to be selected via the assign dropbox, one by one.
Why is that? Are brainworx not applying to standards, or is there another reason?
Errr… the “Generic Editor”, not the “Remote Control Editor”
The Generic Editor does not look sexy and is cumbersome to use when a plugin has a lot of parameters and the developer did not bother to give the parameters good names… but it puts Steinberg in charge of UI and therefore you get the context menu and the ability to click a parameter('s value bar) in order to “learn it”.
In other words: you get access to the stuff the plugin developer could have implemented but chose not to do (most likely because they didn’t want to be bothered).