Noel Borthwick

If it wasn't already clear there is no need to ever use BA once CbB is installed. Everything is now handled in app including uploading and downloading from BandLab. We are also going to debut a standalone Cakewalk installer soon and allow add ons to be installed from within CbB. IOW BandLab assistant will be deprecated soon.

This is a good way to look at it. If you were getting close to the timeout and happened to be online the lease renewal would happen automatically. That behavior has been in place since we added in-app activation. However you do need to log in to BandLab from within CbB at least once or Cakewalk can't activate automatically.

I'm not sure what you mean by "every time I launch; it needs to be updated". Nothing is being updated every time you launch. Where did you see that?

I think it has to do with conversion from M4A when importing. Microsoft is adding some padding to the start of the loop. I solved a similar issue with MP3 recently but M4A is a bit more opaque since we rely on the OS to handle the import. We'll look into it and see what can be done.

@NoelBrutonMusic your concerns are unfounded. You do not need bandlab’s permission every time you use the application. Where did you read that information? This is how it works: You sign in to BandLab to activate the software once when you first install it Activation is required generally once every 6 months unless something drastic changes on your system like you changed the version of windows or something. In the latest release it refreshes your activation lease automatically when needed to save the user from unexpected discovery of a timeout The lease is automatically renewed when you log in to BandLab, when you install a new version of the software and of course if its about to expire. This only happens if there is an internet connection available. If you don’t want your system to be online you have to handle activation manually using the offline activation workflow. Previously BandLab assistant was used for activation. This changed in the 2020.11 release and everything is done inside CbB now which makes things much simpler for the user. Now users only need to sign in ONCE to Cakewalk and from that point activation is handled automatically when needed as long as you don’t sign out of BandLab of course. Its as unobtrusive as it gets and very standard to how everyone in the industry does this. The changes were in fact made to improve things for users who got the activation timeout messages.

Cakewalk currently doesnt support surround VST’s so only the first two channels will be utilized from the plugin. 3 instances will be used each utilizing the first two channels.

Welcome back! BandLab volunteered to fulfil the lifetime membership responsibility so there was effectively no change for lifetime members

Does anyone on the planet read release notes?

@Andres Medina thanks we'll investigate it. did you hit the delete key after selecting all? If you can share the project file before the crash.

Freeze basically saves a snapshot of the clips state and then renders the clips to audio. On unfreeze it restores the original location of the clips. I don't think it has anything to do with moving the frozen audio dive it should still restore the clips if you unfreeze. If you send a project we can investigate

This is an interesting case. You were running in build 144 which had the strict error checking enabled by default. It turns out that you have a shell extension that ends up generating a read access violation when displaying an icon. Our handler caught it and reported it. However it seems like the Windows shell handles this problem internally and thus the end user would normally not see this issue. Its a few issues like this which are the downside of doing the strict error checking so I disabled it by default from the main release. In the next release we may consider logging issues like this rather than reporting them via the crash dialog since its impossible for us to tell whether a given access violation exception is benign or not. Some are not and can cause the app to shut down and lead to data loss! In any case you shouldn't see this in the latest build anymore. Unhandled exception at 0x00007FF860764B89 (KERNELBASE.dll) in Untitled_05182021_133526.dmp: 0xC0000005: Access violation reading location 0x0000000000000000. KERNELBASE.dll!RaiseException() Unknown Non-user code. Symbols loaded. [Managed to Native Transition] Annotated Frame [Frames below may be incorrect and/or missing, no binaries loaded for kda.dll] Annotated Frame [Frames below may be incorrect and/or missing, no binaries loaded for kda.dll] Annotated Frame [Frames below may be incorrect and/or missing, no binaries loaded for kda.dll] Annotated Frame [Frames below may be incorrect and/or missing, no binaries loaded for SharpShell.dll] Annotated Frame [Native to Managed Transition] Annotated Frame shell32.dll!CFSIconOverlayManager::_GetFileOverlayInfo() Unknown Non-user code. Symbols loaded. shell32.dll!CFSIconOverlayManager::GetFileOverlayInfo(unsigned short const *,unsigned long,int *,unsigned long) Unknown Non-user code. Symbols loaded. windows.storage.dll!CDrivesFolder::_GetIconOverlayInfo(struct IDDRIVE const *,int *,unsigned long) Unknown Non-user code. Symbols loaded. windows.storage.dll!CDrivesFolder::GetOverlayIndex(struct _ITEMID_CHILD const *,int *) Unknown Non-user code. Symbols loaded. windows.storage.dll!CRegFolder::GetOverlayIndex(struct _ITEMID_CHILD const *,int *) Unknown Non-user code. Symbols loaded. windows.storage.dll!CIconOverlayTask::DispatchTasks() Unknown Non-user code. Symbols loaded. windows.storage.dll!CIconOverlayTask::InternalResumeRT() Unknown Non-user code. Symbols loaded. windows.storage.dll!CRunnableTask::Run() Unknown Non-user code. Symbols loaded. windows.storage.dll!CShellTask::TT_Run() Unknown Non-user code. Symbols loaded. windows.storage.dll!CShellTaskThread::ThreadProc() Unknown Non-user code. Symbols loaded. windows.storage.dll!CShellTaskThread::s_ThreadProc() Unknown Non-user code. Symbols loaded. SHCore.dll!ExecuteWorkItemThreadProc() Unknown Non-user code. Symbols loaded. ntdll.dll!RtlpTpWorkCallback() Unknown Non-user code. Symbols loaded. ntdll.dll!TppWorkerThread() Unknown Non-user code. Symbols loaded. kernel32.dll!BaseThreadInitThunk() Unknown Non-user code. Symbols loaded. ntdll.dll!RtlUserThreadStart() Unknown Non-user code. Symbols loaded.

@Michael Reynolds you share a reference test project that has this problem with instructions on how to reproduce it? Also are you running the latest version of Cakewalk?

I looked at both your dump files there and they were reported with exception severity 7. I couldn't fully figure out what was causing the exceptions from the dump file unfortunately. They didn't appear to be plugin related issues. The latest release shouldn't report those issues since we default to severity 1 now.

Hi folks, thanks for your help in making this a great update. Update 1 has been officially released. Head to Help | Check for updates to download the final build.

That makes sense since 3 and 7 are the only levels that check for type access violation.

Have you got the log file open in a text editor? This will prevent the log being written and is one possible cause of that error. Scanning doesn't use these settings currently. We could but it may flag many more plugins than it does today.

If you reference the case number here I can look it up.

Ironically I have a macbook here also used daily. The macbook needs to be rebooted at LEAST once a week or audio goes wonky on it. My Windows development PC stays online without a reboot sometimes for months and it gets a LOT of abuse. Not to say Windows doesn't have problems but stability these days isn't a major issue.

Guys you absolutely do NOT need to be connected to use Cakewalk! I think you are misunderstanding what activation does. 🤯 You can run cakewalk anytime anywhere without internet. The bandlab integration features are completely optional and those do need an internet. Even activation can be done without an internet connection from the PC you use Cakewalk with.

@bertus weyers Have you reported these issues to NI? Also did you send crash dumps to us? If so what is your case number? We have a good relationship with NI engineering and can forward any issues if any,

@Keni You sent the dump file to support?

Please capture a hang dump file if you get the not responding error and send a link to us. Instructions are in the FAQ for problem reporting. As far as Ozone goes thats something you will have to follow up with their support. Please attach a sample project file that has the issue so we can double check it.

Leaving it on doesn't automatically help us. Its up to you to follow up and report the issues or contact the vendors concerned.

There is no manual reactivating required. It all happens automatically and transparently. The only time you will ever get this prompt is if your PC has been offline and it needed reactivation AND if you have not updated for 6 months. If you have updated ever within the 6 month period you will never see the activation prompt. As mentioned above one requirement is to keep the software up to date. If you follow these simple steps activation is a non issue.

The music industry is full of people with biases. I doubt this was Korg’s policy but coming from someone in support who was a Mac user. The same thinking goes around in some educational institutions like Berklee unfortunately. I wonder what musicians would feel if a company told them that if they were a serious musician they would use a Gibson instead of a Fender lol.