Noel Borthwick

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.

Its not a bug, Workspaces hide access to commands and menu items. They don’t physically remove features like the prochannel and splitters which show tempo strip, video strip etc, today.

His main issue was fixed in 2019 when I reworked automation to address some reports of lost settings with certain plugins. Of course he isn’t around anymore to attest it. Some issues when not reproducible readily can be infernally difficult to isolate. It took working with several users offline and running tests before I was able to resolve it.

@Chris Boshuizen is this reproducable for you and is it specific to a particular project? If so please send a link to the project file.

Thanks, I think the dropout immediately following a bounce to clips, is likely a spurious dropout message caused by an expected scenario with the engine transitioning from offline to online. I’ll look into it for next release. You can ignore that message since its harmless.

The first thing to do would be to try and isolate the problem by rolling back and testing. Also not sure if these do but some plugins that use OpenGL have problems in Cakewalk with certain versions of Windows and video drivers.

@Will Zégal Its very unlikely that the latest release caused any of these issues but have you tried rolling back to the prior release to verify? A link to the rollback installer is always listed at the top of the new release thread. Very often issues are being attributed to the latest release when they are preexisting or externally caused issues so its important to roll back and verify if you have a reprodicble issue. Is the problem reproducible every time or intermittent? Which version of Kontakt are you using?

@Vlad Vilnev Which plugin has this issue? Symptoms looks like it would be a memory leak or bug in the plugin.

USB cables should work. I have the rocksmith and it works fine in Cakewalk. Switch the driver mode to WASAPI shared, select the cable as an input device and select your soundcard output in preferences. Sample rate should be 44.1 or 48k. Ensure Windows is using the same rate. You should be able to hear recorded audio now.

Mario, the refresh activation after an update is simply a convenience so that it does it automatically for the user. It is not a requirement so if a login prompt appears you can skip it and the app will continue with its current activation status. That said we have tested login and it works fine in Windows 7 on multiple machines. So you may want to look into why it is not working on your PC. The only reason we know of is that the Microsoft webview component is not properly installed. You can install it manually and login should work fine. Retest it in the latest 2021.04 release since there have been fixes for some issues there.

Can you PM me the contact for the person you are working with? I will get in touch and try and understand more.

This would be a plugin specific issue so we wouldn't be able to assist with it.

You do need melodyne to do audio to midi conversion. However, even the lapsed demo version (I.e. free limited version) will continue to handle this.

Yes in theory you can uninstall BA now. Although there is no harm leaving it since it is still used for a few things such as offline auth if needed. The reason for the one time log in is because the new release tries to renew your activation state (as a courtesy). Since you had never connected CbB to your BandLab account it asked you to log in. It shoudn't prompt you again now that CbB saved your login so its a one time nag. This is described better in the activation FAQ

No you should use Cakewalk. Everything you need is in the app. I suggest reviewing the updated activation FAQ which should cover all related questions going forward.

If you are that paranoid and mistrustful of software its on you to enforce your requirements, not the companies making the software. Its simple to set up a firewall block that prevents internet access to a specific program. Learn how to do that.

@RBH The activation actually is completely independent of analytics. It doesn’t report any significant data back to Cakewalk. Its a one way street - all it does is make a request to activate the software for that machine and provide a new lease for the software whenever it is needed. We just improved it so that the user is not caught be surprise needing to activate when they are busy at an inopportune time. Now every update of the software will auto renew itself. I’ve installed on 3 of my PC’s and oneof them hadn’t been updated in months. It instantly was renewed for a new lease so I wouldnt be greeted with a timeout the next time I tried to use it.

Lets say that If there ever comes a time that this is needed permanent licenses will be made available. For now there is absolutely no need for this.

No when we refer to logging in we mean using the signin prompt within Cakewalk (where you enter your BandLab user id and password). Different apps have their own sign in so the data isn’t shared. For example signing in from BandLab assistant is different from signing in via the web vs signing in within Cakewalk. Though the credentials are the same there is no sharing between the apps today.

@Toy thanks for the report it has been fixed for a future release.

@brandon Refresh activation is in the help menu in CbB. Everything is handled inside Cakewalk now. There is no need to use BandLab assistant. Please update to the latest version since its not clear what version you previously had. If you cannot sign in to BandLab from Cakewalk, check if you are using the same credentials used to log in to BandLab from a web browser. Try entering your user id and password. I use google sign in so the credentials are the same that I use for google. If you aren't receiving a message when you refresh activation in Cakewalk you likely have notifications disabled. You should either get a notification or if you aren't signed in you will get a sign in prompt.

Im referring to the posts about tempo changes. We had a long window where we were responding to feedback which is the purpose of the early access program. We'll continue to respond to feedback but any changes will only occur in the next release.

We had early access on for over two weeks and non of this was reported. It will now be addressed in the next release.

MPC beats has a problem that we reported to AKAI months ago. You can forward the crash dump and we can verify if its the same issue.