Jump to content

[SOLVED?] Setting Up Control Surface Requires CbB To Close & Reopen?


sjoens

Recommended Posts

(i can't translate but) it looks like the controller is sending the same message repeatedly? or an unrecognised message... does it always look like gibberish in that status area? have you checked the controller with another daw/or factory reset on the controller? what's the controller? shouldn't it say "OK" or "Ready" or something similar sensible, human readable?

/goodluck

Link to comment
Share on other sites

Most of the time this is what it shows.  Only once it actually displayed the name of the track it was focused on.  Oddly the maker (Nektar) said they've seen the same thing.  They also said Cakewalk handles controllers differently than most DAWs so I have no fantasies of it ever working 100% as expected.

I've never used it with other DAWs but I might try it with Mixcraft.  However, I don't think MC displays things the same way so maybe Cakewalk is asking more of it than it can do. ¯\_(ツ)_/¯

Edited by sjoens
Link to comment
Share on other sites

On 2/21/2025 at 6:05 PM, sjoens said:

Most of the time this is what it shows.  Only once it actually displayed the name of the track it was focused on.  Oddly the maker (Nektar) said they've seen the same thing.  They also said Cakewalk handles controllers differently than most DAWs so I have no fantasies of it ever working 100% as expected.

I've never used it with other DAWs but I might try it with Mixcraft.  However, I don't think MC displays things the same way so maybe Cakewalk is asking more of it than do. ¯\_(ツ)_/¯

This text is set by plug-in, in this case by Nektar. But I have never tried to use it with international characters. So, if you expect ASCII (english) there, it is Nektar bug. If your track names are localized, that can be encoding issue.

Whatever I was displaying as status many years, as long as that was in english, it was displayed correctly.

--

The only big difference in handling controllers by Cakewalk is that handling is officially documented in public (GitHub). "Most DAWs" hide it, so those who have access to it (f.e. Nektar) can write anything to users, users can't check the claim... At least in DAWs for which handling is known (Ableton, Bitwig, REAPER), the handling is similar.

Nektar is controller producer which hide protocols. For Impact there is nothing they can really hide, but  for "smart" controllers like Panorama that prevents 3d party developers using controllers. Even for NI controllers (which publish no technical details in public) it is possible to get the documentation. Other companies have it in open or don't prevent RE documentation spread in the Internet.

I mean it is not wise accept as trues everything Nektar writes to you. They know you can't check.

Link to comment
Share on other sites

For some reason I can no longer find his response so I can't verify what he said specifically.  Majority of characters are square blocks which a font will display when there's no character for it.  Otherwise there's an EURO dollar sign and a funky p.

Every session is different.  Today I get this:

image.png.abc17128721639ef9f4dba557d933e30.png

Edited by sjoens
Link to comment
Share on other sites

Good to know.  Todays message:
image.png.589045bd3c5048b669bb1f28cd0ffe0a.png

After deselecting "ACT" in the setup window I get this:  which is the 1st assignable control in Dimension Pro on track 1.  It never changes when track banks are moved, so - useless info.
image.png.67fd657994511fd7bc85580c6b5fe6b6.png

Creating a surface entry for Roland V-100 displays the 1st plugin on track 1 which is Dimension Pro. but includes no WAI indicators for tracks and also never changes, so - useless info.
image.png.5e09fa43d1bd7ed589201b2cbffc05f6.png

Creating a surface entry for TascamUS-428 or Mackie displays what should be there: track status - useful info.
image.png.49913560a13c1492843c77235b54a890.png

So Nektar is clearly not providing track info or Cakewalk is misinterpreting it as gibberish.  Roland owned Cakewalk so not sure why V-100 doesn't communicate as expected.  Tascam, Mackie, and maybe others do it right.

BTW, none of these others required me to close/reopen CbB to work.

OAN, Nektar is programed to think the 1st Bus is the Master bus  (Master 1)  but I always move it to the far right, so unless I can change that somehow it's also useless.

Edited by sjoens
Link to comment
Share on other sites

OP - maybe closing/reopening CbB was only necessary for setting up 1st controller as it hasn't been needed after that.  Or maybe just a fluke.

Edited by sjoens
Link to comment
Share on other sites

  • sjoens changed the title to [SOLVED?] Setting Up Control Surface Requires CbB To Close & Reopen?

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...