Noel Borthwick

Can you post a screenshot of the dialog you are seeing? Checking for updates doesn't require you to be logged into your bandlab account. Its completely different. However its worth checking if you are able to sign in to BandLab from within cakewalk and browse the BandLab library.

Yes change the track name after that and then save the project and it should stick. I don't see how it could persist without the project being saved. Definitely not happening here so maybe you are confusing something. When a project loads it sets the bus to whatever was saved with that project so if you did not resave it after changing the bus you would get the last saved settings. I can send you a build with the fix to check later.

I've fixed the issue where the preview bus was not showing the project as modified after changing it. I think that is the root problem from your recipe. You can verify by changing anything in the project such as a track name and resaving after modifying the preview bus.

You should log in from Cakewalk. Logging in from BA will only lead to you getting the same issue a few months down the line.

>>Because the name has changed, Cakewalk will not open the Neve 33609 in older session files because Cakewalk identifies plugins by their name rather than a plugin ID#. I'm not sure where you got that from. Cakewalk has always utilized the plugin ID. However for VST2 plugin its not sufficient to do so (because the ID is not guaranteed to be unique and many vendors make mistakes). So we use an expanded ID scheme that utilizes part of the file name (in this case its the 8.3 file name). Many years ago I improved on this to be less dependent on 8.3 file names. However you must save your projects with the plugins for this scheme to kick in. If you have old projects they will not benefit from this obviously. Also look into the details that Kevin posted above. If the session isn't opening its because the something more drastic changed in the name resulting in the ID's not matching. We don't have any UAD plugins in-house to test this with. Are the plugins still tied to UAD hardware? If you send a dump of your VST inventory from the registry and a sample project file that won't find the plugin, I can take a look at why it fails to load.

Is this problem still occurring? It could have been a connectivity issue on your end.

@paulo can you provide us with the project that has the issue? Also something to try - replace Kontakt with some other VST synth. See if the same issue occurs with that synth. Also you are running a very old Cakewalk build - We fixed several issues with recording aux tracks and synths in the April release. (Although that isnt directly related to this specific issue necessarily)

Improved VST support doesn't mean we can magically fix preexisting bugs in plugins We added some VST3 features to support some upcoming new VST3 plugins based on feedback from the vendor.

Almost surely a bug in the plugin. You should report this to the developer and send them the session file to test.

There is no loss of information in fact there is a lot more information than before. With virtual instruments Cakewalk groups all outputs into pairs. However the mono stereo listing was arbitrary because there is no guarantee that a plugin output is stereo or not. The numbers now clearly indiscrete which output is being used unlike before. Most other DAWs do the same. For your purposes you can assume 1 means left 2 means right and 1+2 is stereo. What are you missing?

I'll look into this. It is an oversight.

Maybe the opt out is only when using friendly names?

Thanks for the explanation. Its difficult to find something that works for every possibility when it comes to numbering. In the ADAT case, yes the driver is NAMING them as 1 & 2 but strictly speaking they actually are 9+10 as far as their position in the output list. CbB has no idea that they are ADAT outs. We considered allowing suppressing the prefixes. Where it gets messy is there are cases where the prefixes are necessary, eg WASAPI, or when they are used for synths so its difficult to get something that works sensibly everywhere.

In Cakewalk all inputs and outputs are grouped into pairs of channels by default. The I/O simply let's you pick one or both of the channels. This way a track can address one or both of the channels without complicated routing. If the track produces a mono signal because of interleave or plugin settings and it's output is stereo the mono signal will be sent to both the channels. Conversely if the track is stereo and the output is mono the signal will be summed and sent to the mono output. Routing is (and should be) a decision the user makes not the program.

No way to suppress it today. However I'm curious why you are assigning all your outputs to the same name? Without the automatic numbering you would have no way to know which I/O you were assigning something to. Why do you want to suppress it?

Linked clips are different from normal clips in the fact that changes to one clip are reflected in all copies automatically. Read up in the help.

IMO it would be more confusing and unexpected for I/O connections to change based on interleave. Interleave affects signal flow not connectivity in the engine.

No because the output has nothing to do with the bus interleave setting. All that does is force the effects track to mono or stereo. It's up to you to route there bus output to whatever you want. I.e routing and interleave are not related in any way

Hi folks in case you haven’t spotted it, we posted a preview of the 2021.06 release here. We’ll likely release it next week but we would appreciate you kicking the tires and providing any early feedback. This allows us to fix any potential problems quickly before it hits the street. Thanks for your support.

Are you sending to a hardware out, bus or aux? Please post a screenshot since its not clear what the routing is.

Could you please post some screenshots or video with the error message? Which version of windows are you running?

Did you know that Billie Eilish is the neice of an old ex-cakewalk employee - Jamie O’Connell?

We should be adding support for this soon (importing back to back on a single track)

We have custom code to integrate with the Console One. We don’t have a MK II to test with but I assume that the integration is the same.

VST2 plugins have no way to distinguish between reset CC data sent when playback is stopped. CbB resets certain CC’s on playback stop such as CC 0, CC 64. Generally you should not use such CC’s to control plugin parameters for this reason.