Tez

Agreed, as noted above, from faulty keyboards, or my favorite, an incompatible plugin to a system issue.... But none the less it is ubiquitous 🙄

Space bar has been a problem for eons, I've had it crash CbB occasionally on pressing it for play, tech has to know. it's old issue....

Same here for CbB guess it's a server error a 502 bad gateway... For the latest CbB and I guess the the Nu Sonar they started using new servers, and I believe the endless activation-reactivation issues folks have been having, in my case daily, might be due to these servers. With any luck maybe they're fixing it!! UPDATE: Should be working now... Yippee yo ki yay !

Every day after booting up windows, the 1st CbB launch gives me the RED Popup, I immediately shutdown CbB and relaunch and Voilà it's activated!! Noel Borthwick claims it not an error, but a failure to complete a browser handshake ergo a local system problem! Well, a load of us seem to run into this and it wasn't happening to versions prior to the final versions, So, go figure ?...

Thanks Noel, but I'm not sure I understand what the "the browser handshake" is? Something internal to CbB or is it related to the default system browser in my case Firefox as CbB shows I'm signed it? Thanks again ?... UPDATE: I signed in to Bandlab using Firefox (my default system browser) and stayed signed in. Rebooted my system, performed sundry activities, following which I launched CbB and had no activation issues, or related activation notifications. Hopefully, in my case, this fixed the issue, we'll see going forward ? UPDATE2: Well, the above was short lived and it's back to the the activation issue today (3/14/2024)... Ho hum ☹️.

I documented my experience, others have a similar issue and for me this did not occur to CbB versions prior to "2023.09". The question is how to track this down if it only occurs to some of us, A windows task manager dump may not capture what's initially blocking the handshake which for me subsequently disappears on a relaunch with a now activated notice, incidentally when the Bandlab membership promo notice popped up there was no following activation issues and clicking check for updates shows the CbB version is up to date. Any suggestions?

It was fully documented on feedback Noel knows about it & subsequently ignored as a singular issue ?

That's good to know, thanks!

This is very thorough, and thank you BUT... The link I posted above refers to "2023.09" but it's equally applicable to "2024.02 Build 98" and for my system none of your suggestions are necessary as all I have to do when the toast pops up that says it is "Not Activated” is close CbB and relaunch and viola it gets activated. I don't know if the OP can do this? I thought it might be the AV and excluded the "Cakewalk.exe" from real time scanning to no effect & I have no blocked connections! This did not occur to CbB versions prior to "2023.09"! It appears that I'm not unique so it seems that maybe, just maybe it's condition caused by these final versions released after "2022.11", at least, for some of us. It's a largely a worrying annoyance, but I wish support would look into it ?...

I used and alternative for the TTS-1 percussion, as TTS-1 is flakey... see NOTE All the other instruments are also available for conversion...

I have the what looks like the same issue see So far no resolution.... So, if it's not just me hopefully it will get addressed ?...

With the CbB current 2023.09 installed many times it is launched for the 1st time after booting up Windows it pops up a toast that says it is "Not Activated” contrary to which I believe it should be, I then have to immediately shut CbB down & relaunch, which then pops up the activated notice and is good for the rest of the windows session... The “Not Activated" toast doesn't occur on every reboot, but despite that, on a subsequent launch of CbB I'll see on occasion the now activated notice even though I was fully able to save projects? On 10/3/2023 at 1:15 PM, Noel Borthwick said: “Pretty unlikely. Once the app is activated it doesn't retry until the lease expires which is quite long. Check whether you have some backup script or something that is restoring some state when you reboot. If so, that might explain why Cakewalk is not activated again after a boot.” I don't have a backup script I'm aware of, or know what could restore state on a reboot? If either existed, wouldn't it have affected the previous version? The odd thing is when the toast popped up that says it is "Not Activated” I checked Help, and it shows that I'm signed into BandLab so I'm at a loss as to what's going on. It doesn't stop me from using CbB, but it is a bit annoying, and I hope nothing is else out of whack... If it's not a bug, any suggestions as to what’s going on would be helpful, thanks

If the bounce plays as expected in CbB try copying the bounced track directly from the audio folder and paste to the Desktop, that always works for me...

@msmcleod Thanks, that totally makes sense, explains why inserting 1st worked for me ? Since I use it as a substitute for the GS Wavetable percussion, last night I found an alternative, SF2s found at this link: https://musical-artifacts.com/artifacts/1549 and used "sfZed09" sfz format editor at this link: http://steveholt.drealm.info/sfZed.html, to convert the SF2 percussion to an SFZ then loaded it into Rapture Pro, which eliminates TTS-1 issues & my ol' SF player's not reliable, All the other instruments are there in the SF2 and can be extracted as individual SFZ's! I'm sure a lot of folks here are already familiar with this, but thought I'd list the info just in case it helps someone...

I'm not using TTS-1 from scratch mainly if importing or opening some midi that uses the Microsoft GS Wavetable percussion, which once known can get substituted, and also it shows somewhat the original intent; non-percussion instruments just get substituted. TTS-1's a geriatric DXi & I looked for an alternative, didn't see anything appealing, any suggestions?

I have a template with 1 instrument all outputs mono, and a slew of aux tracks & FXs, using optional sends for FX signal paths & various configurations for 5.1 hard out targets, and NO busses... After adding TTS-1 (1st Stereo out) set to channel 10 for percussion, on playing any TTS-1 note CB crashes with no dump. If first, I delete the 1 instrument, then add the TTS-1 as before followed by adding back the 1 instrument configured as before deletion, it all works as expected, no crash, and a template created from this working configuration also has no problems... Also starting with a blank project adding the 1 instrument first followed by theTTS-1, both defaulting to a hard out, again no problems... Any reason for the crash??

What I do to set a section of a midi to a different tempo from the rest of the project is to use the Tempo track mark the midi section start and end set the the temp at the start and set the project tempo at the end. After that, go to the now time and position to the end marker copy the time (I use H.M.S.F format), then delete the tempo changes in the tempo track. After that, select the marked section of the MIDI track then select "Process>Fit to Time..." from the control bar menu select Event time option, paste the copied time in the "New Thru" box & press OK... Voila, the clip is set to the desired tempo differing from the project tempo... Hope this helps...

@msmcleod Cheers... Another access violation bites the dust!

@Dave Brian Little yes sir! All work is lost... You're the 1st to reply and I can only hope support has taken note! For the time being I'm being careful about using "Paste into Existing Clips" so as not to lose another work session ?

UPDATE: The crash as described below only seems to occur for "Paste Special" and "Paste into Existing Clips" is selected and the now time cursor is outside of any clip in a blank portion of the track. Further, this can also, if not consistently, cause the crash if the paste is made in the same project as the copy, and once again this does not occur with version 2021.11 (build 18, 64 bit). I believe this is bug... This is a consistent CbB Crash after installing 2021.12 where a copy from one project followed by a paste into a second project results in the W10 active spinning blue wheel followed by an immediate closure of CbB, without a crash dialogue or a mini-dump. This can occur on a copy/paste as follows: 1. Both the 1st project (source) opened in CbB and the 2nd project (target) opened in CbB. 2. The 1st project (source) opened in CbB and the copy performed and closed within CbB, followed by the 2nd project (target) opened and the paste performed. The test projects used each consisted of only a single Midi track and no buses, and a single Midi clip was copied. After both scenarios CbB crashes following the paste and in both cases the Fault offset is the same where a typical “Error Event” is shown below. This should hopefully help resolve this issue. Last, I confirmed this does not occur with version 2021.11 (build 18, 64 bit), using the same projects tested in the above scenarios... Error Event: Faulting application name: Cakewalk.exe, version: 27.12.0.102, time stamp: 0x61bb7276 Faulting module name: Cakewalk.exe, version: 27.12.0.102, time stamp: 0x61bb7276 Exception code: 0xc0000005 Fault offset: 0x0000000000de512e Faulting process id: 0x6ccc Faulting application start time: 0x01d7faa3817a46ed Faulting application path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Faulting module path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Report Id: ec43dc72-d8c5-4e7e-a60f-6c125533d500 Faulting package full name: Faulting package-relative application ID:

Thanks @Noel Borthwick

On a bounce to tacks what buffer size is equivalent to the 2021.06 "Fast bounce" option?

I think I suggested this and was just looking for confirmation, if that's what you mean by

I am not confused, maybe I wasn't clear enough for you, as I said before I set the plugin (TTS-1) to “Upsample on Render” which only works if the global "Plug-in Upsampling" is enabled, I thought it was clear that on the render that's what I did, enabled the global "Plug-in Upsampling". Ergo the sample rate was doubled for the TTS-1 on rendering to a value of 88.2kHz, since the projects sample rate is 44.1KHz. I know how to use plugin upsampling, and as I said before at the doubled rate the TTS-1 worked fine, on render and also playback if set to “Upsample on Playback” with "Plug-in Upsampling" enabled . You can easily verify this with a 44.1KHz test project...

Thanks for your extensive reply, but the point I was trying to make, if I understood correctly what CbB does for a plugin when set to “Upsample on Render” , namely lets you specify whether a VST or DirectX plug-in effect or instrument should be resampled at 2x the project sample rate when bouncing, which is exactly what I did for the TTS-1 in a project with 44.1KHz sample rate which implies for the render it was sampled at 88.2kHz sample rate and Mr Anderton said the TTS-1 won’t function at function at that rate, the purpose of doubling the sample rate is because "some plug-ins can produce unwanted artifacts when running at lower sample rates". What CbB does to achieve the higher rate weather it's to increase buffer sizes or "inserting zero-valued samples between original samples" I wouldn't know. Regardless of the mechanism the rate was doubled to a value of 88.2kHz and the TTS-1 worked just fine in this context.