If you hold down the forward and rewind for more than about a second, do they then scrub through the track? That’s what happens on mine - as you say, about a second ‘nudge’ unless held down.
Steve
That isn’t what’s happening with mine. I know I’m not helping you, but just pointing out you should be able to set this up without any start delay. Nektartech updated the firmware for the CS12 a couple of days ago - have you downloaded the latest software for the device?
Steve
We always found REW and FWD imprecise and not very useful. REW and FWD buttons on CS12 follow the grid size setting. If you don’t see the grid setting in your Cubase toolbar, Ctrl (right) click on the toolbar to open the setup Toolbar dialog. The image below illustrates how to view and control the grid setting. Personally, I use the setting "adapt to zoom, which means the control resolution of the REW and FWD buttons adapt to your focused view.
1 Like
This is not usual behaviour. Please first ensure you are using a supported version of Cubase. CS12 requires Cubase v13.0.51+.
Other than that, I’m wondering if something went wrong when trying to re-assign the FWD and REW buttons. I suggest reverting those changes and using the Grid Size setting to increase resolution as explained above. The CS12 script is complex - the transport controls duplicate over many pages so user edits here are not recommended.
To make user settings updates I suggest using the MARKER buttons, or use the USER pages 1 and 2 in CHANNEL mode as these are specifically designed for user override.
To revert all mappings for the CS12, delete the CS12 json file at ~/Documents/Steinberg/Cubase/MIDI Remote/User Settings
If you still have issues with delayed playback, please contact Nektar support.
Yes, I have adapt to zoom. The rewind (-) and forward (+) shortcuts on my keyboard work fine. When I press them they just ‘jump’ and not keep running until I stop them (like my CS12 does).
Before I reassigned the buttons they were on nudge (in seconds) but didn’t adapt to zoom or anything. They just kept nudging in tiny increments. They from the start worked nothing like I’ve seen Dom do on YouTube. The rest of the unit seems to work fine, it’s just these 2 buttons.
I wish those buttons behaved like the - and + on my keyboard.
I’m on Cubase Pro 14.0.32 (newest version)
I did as you asked, I deleted the the json file. But when I opened Cubase again, the 2 buttons (and the buttons above, which I also changed before to jump between markers) are empty and are back to where they were when I installed them. So the function is again ‘Nudge cursor right’ and ‘left’ instead of forward and rewind. But the nudging is in miniseconds (it doesn’t adapt to zoom) which is unusable.
Btw: The delayed playback thing I described earlier has nothing to with the CS12 - I found out - it was just in that Cubase Project I was working on.
Ok, I’m sorry for the many replies (I don’t mean to spam) but I think it works now. The rewind-nudge and forward-nudge now work as they should (they move in bars when zoomed out and in shorter notes when zoomed in).
I just found the rewind and forward buttons on the CC121 nicer for podcast editing because it can cross greater distances so the speak. But I think i’ll just use the keyboard for that.
Sure I can see that use case.
Would setting up markers not be more suited to crossing greater distances? You only need to use SHIFT+MARKERS on CS12 and this will mark your current location. Then hold markers and use M1, M2 etc to jump directly to that location.
You can also hold MARKERS and the DATA/MENU dial will scroll through set markers which is a lightening fast way to navigate greater distances.
Let me know if this works for your situation.
You can also hold REW/FWD and scroll through the arrangement with the DATA/MENU dial, or hold SHIFT to set the TEMPO dial to “Playhead (Jog)” to scroll through the arrangement using the TEMPO dial without holding REW/FWD down.
2 Likes
How did you change the color of the plugin slot button again? The manual says to press the button and turn the data menu knob. No, it doesn’t work for me.
Is there any news on this? When will it be ready?
1 Like
It’s not working here either.
I installed on a new computer [ M4 Mac Studio Mac, was on an M1 Ultra ] and installed the latest build.
Changing knob colors is working but not the Slots.
Seems like this is an issue, as the user mapping file [ nk_user_insert_maps.xml ] is not including the color information line [ PluginMapColor=“red2” ] when a new user mapping is saved [ either from within Cubase or Nektarine ].
[ I added the color line back in and resaved the xml, didn’t make any difference. ]
Off to support to create a ticket then. 
A OK. Then the bug must have appeared with the last update. It worked before that. Let’s see what they say. But can you tell me what I have to do to make it work? If it gets fixed. I already know how to do it with the potentiometers (turn the data knob in learn mode and then select set color).
Yeah, can confirm it was working fine for me on the M1 Ultra with the previous build.
Waiting to hear back from support, couldn’t find a way to make the Slot colors work. Will post here when I get a reply,
1 Like
Apparently it’s a known issue.
Scheduled to be fixed on the next update. No timeline given.
1 Like
Where can I find this information? I’m only asking because I’d like to browse other forums about it 
The info was provided via a support ticket. Here is the exact reply:
”Yes, we are aware of this issue. We were hoping we could fix it before releasing ControlCore v1.1.38 but it was very critical for us to release that update for customers who are using Logic 11.2 and later.
The remaining updates/fixes will be included in the next update for ControlCore but I’m afraid I can’t say when that will be ready”
1 Like
Just an FYI, this has been fixed. The new update should be out next week, all being well.
4 Likes
That’s really good news Tim, thanks for letting us know.
I see there was an update yesterday (Sept. 5), anyone know what’s included?
1 Like
where? I checked the cs12 downloads site at https://support.nektartech.com/my-account/
and downloaded Panorama_CS12_ControlCore_v1143_fw_v010202_WIN but the contained Control Core installer is ControlCore_Installer_WIN_1.1.19, and I already have ControlCore_Installer_WIN_1.1.38 from 19/07/2025.
are you talking about a new Cubase Version? It would really be nice if the devs would provide change logs with all versions. it would be a good sanity check whether one is moving forward with bug fixes…
1 Like