One issue I’m having is with the plugin open/close, it worked in the beginning but is now only showing the plugin when holding the plugin button but then playing is not possible. Something strange with momentary latching the plugin window.
Thanks, @Tim_Chandler. I ordered a CS12 now. Appreciating your/Nektars commitment to their customers.
Able to isolate the issue a little bit more. It happens when you have Channel selected to see/edit the plugin and then open/close the plugin window. When Channel is not selected, there is no issue with opening/closing the plugin window.
Is there an version history available? Because I don’t know what all the reported issues are 
1 Like
Thinking of getting one to replace my CC121 - How much Control of the Channel Strip does it allow ? I know it does the EQ, but from the site I hoped it could control ALL 6 or more modules - Is this a feature coming or is it already available?
Finally I did try a wrapping plugin a few years ago - from a different company, and it corrupted my VSTs some how - Is this one pretty transparent ?
My main use would be to control the Channel strip, as well as a general controller.
Finally am I correct it can control the Tempo in real time ?
I was also looking at Console 1 mk3 , which is more premium , but limited in terms of Cubase control - I am hoping now they have Midi mapping, you will be able to control the Channel Strip of Cubase fully.
Cheers
Yes,you can control the channes strip,The module you are interested in only has to be activated.
1 Like
“… activated in Cubase”, since only “activating/deactivating a Cubase channel strip module” is not yet controllable from outside of Cubase (Steinberg needs to enhance here - sounds to me like a minor effort change).
Bypassing one or all channel strip modules is already possible from the CS12, all well as adjusting their parameters
Hi, not sure I understand this. Both turning on/off or bypassing the channel strips components can be handled by remotes.
That’s what they (Nektartech) wrote in their most recent manual of the CS12 (downloaded today). I do not know which technology actually is used behind that tbh. Maybe we just have to wait for the next version, @Tim_Chandler ? Or do you have some detailed hints, @m.c ?
I don’t have this device, at least not yet. However, I’m sure NektarTech is using the MR in-sync with its Control app.
I recall when dealing with the mOn property of the channel strip effects that I got to think that this method was not working. This was because I inspected the UI of the channel settings window, and I didn’t notice a difference when I was turning on/off the components of it. However, I found out (by hearing the audio signal) that it is most probably an issue with the UI not updating accordingly, or perhaps I don’t quite understand a difference somewhere in it. So, I may be wrong on this, hard for me to remember exactly what was my final conclusion, BUT, the method is surely there. I have it in most of my controller scripts.
If I change parameters or names in Nektarine and then save it with the save change function, a file is saved under Documents. But when I then load the plugin into Cubase, the changes are not there. Doesn’t Cubase access the file that I save in Nektarine? Or what am I doing wrong?
1 Like
no. the update didn’t solve the problem. seems to be due to cubase
For the cases where we are sure the “Steinberg side” needs to adjust, we can raise a feature request in an extra topic. As for me, I am not expert enough to be sure of “which side” needs to adjust, though.
1 Like
Is the .npm file saving with a number at the end in the Inserts location for you? [ eg: ‘Dark Memory_2.npm’ ].
Have had some of these occur when remapping and saving. Renaming the file [ and moving the original ] doesn’t seem to help. Have a ticket open with this [ the new build hasn’t changed anything for me ].
The existing limitation with controlling modules in the channel strip is you have to have a plugin loaded in the module. Can’t load plugins from a control surface yet as far as I know.
1 Like
Mappings made in Nektarine can be used in Cubase. If this isn’t working, could you please contact support?
If the .nkm map is in the Inserts directory, controlCore should pick it up. If it doesn’t, restarting controlCore will find it. ~/applications/nektar/controlCore is where the control panel to toggle controlCore is located.
Here’s a list of reported problems addressed in v1.1.6:
- some plugins not recognised
- Channel Volume control issues in localized versions.
- connection drop outs in localized versions
- Scrub control was not smooth
- Plugin+channel button not toggling instrument window
- Shift+tap fader: 0dB position was offset unless max value was 6dB.
- Insert plugin activate state was not recognised
New features added:
Control room is the default secondary fader mode (shift+select). Mapping:
- fader = control room level
- Pan pot = listen level
- Arm = listen on/off
- Solo = talkback
- Mute = mute
- hold select button and turn data/menu to select between master channel and control room.
Like I said thanks for all the feedback.
I will be at NAMM this week booth #16223.
6 Likes
@Tim_Chandler is an update to the Panorama P6 Cubase integration in plans?
Regarding the CS12 - does it have a Mixer view that allows one to control the volume of multiple channels at once with the knobs?
Does CS12 use *.npm files directly within Cubase for instrument mappings like Panorama P6 does, so I can build complex mappings with names for different sections in Nektarine and use them without Nektarine within Cubase? The Manual for CS12 doesn’t explain that clearly.
1 Like
Wow, it’ll be amazing!
Is it possible to assign the keys not as a key but as a switch with more than two states? I couldn’t find anything about this in naktraine and I didn’t read anything about it in the manual. That would of course be a shame