Tez

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

Thanks for the response Noel, I don't have a backup script I'm aware of, or for that matter 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. 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 the now activated notice even though I was fully able to save projects ? Any thoughts? Thanks...

With the CbB current 2023.09 installed each time 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 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... This seems like a bug?

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??

Bounce to tracks Bug I’ve set up a test project that illustrates the bug as follows: Track 1: Audio, output: Aux1. Aux1: output: none, 2 sends: Aux2 and Aux3. Aux2: output: Aux4. Aux3: output: Aux4. Aux4: output: Hardware out. On “Bounce to Track(s)” as follows: 1. Select all tracks for the Audio range in the Track pane. 2. Source Category: Tracks. 3. Only select track 5: Aux4. 4. Render with “Render in Real-time" Not selected. Result: The bounced track is silence. It works fine for a real-time bounce or if the source is “Tracks Through Entire Mix". I’ve PMed Noel with a link to a zip of the test project. FYI, the test project is a simplification of a scenario used in my real projects...

Odd Unmute Glitch: On a project originally created prior to 2022.11, some PRV notes were muted, the project was also subsequently saved in 2022.11 with no change to the muted notes, but in the PRV clicking each note with the MUTE tool failed to unmute the notes. Cutting the muted notes and associated events and pasting them back to their original position enabled the MUTE tool to unmute them in the PRV as normal... No biggy just an FYI.

It was temporary, I'll try and recreate it and check if it's consistently behaving as previously described. How do you want it sent? Update: @Jonathan Sasor Hi, I messaged you with a project link.

Bounce to track bug: I setup a test project (44.1-16 WASAPI Exclusive) with 2 identical length stereo audio tracks taken from a similar projects rendered audio files, ergo the audio files are 32 bit. The sends of both audio tracks were set to the same aux track which had a couple FX plugs, and the aux track's send was to a hardware out. All tracks were selected for the range of the audio files. On executing a bounce to tracks for source category tracks the following occurred: 1. Selecting just the aux track not in real-time with the buffer set to "playback" the rendered track was all silence. 2. Selecting just the aux track in real-time rendered the track normally. 3. If the track was rendered as per 1. and the immediately followed by a second bounce as per 1. the track rendered normally. This is odd behavior, it feels like some kind of a timing issue, but wadda I know 🙄

A lucky strike, the consistency will maybe help to resolve the rendering issues 😏

Screen Render Artifacts: I have a MIDI source, Synth Track Folder, 1st Synth Audio and an archived sub-folder containing a couple of additional MIDI tracks. The folder is collapsed and in it’s track it shows the color bars of the tracks it contains as normal mostly, but frequently the sub-folder color bars show as artifacts in arbitrary locations on the track, they can be gotten rid of, but frequently reappear. This is an annoyance that has persisted since before version 2022.09.

Access Violation: Faulting application name: Cakewalk.exe, version: 28.6.0.34, time stamp: 0x62dae0cf Faulting module name: Cakewalk.exe, version: 28.6.0.34, time stamp: 0x62dae0cf Exception code: 0xc0000005 Fault offset: 0x000000000113a3d9 Faulting process id: 0x8ab8 Faulting application start time: 0x01d8d0951dbed3c0 Faulting application path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Faulting module path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Report Id: 7f1d102f-9dea-4586-aa38-c818d1dcbab0 Faulting package full name: Faulting package-relative application ID: No dump was produced, CBB just crashed... I think it was during a MIDI controller edit in the PRV, also this has happened before at exactly the same Fault offset & CBB version, on probably the same project.

All synths in this project render in real-time correctly in a simple test project described above 😟

Thanks so much for the response but... First, I setup a simple test project, one synth out & and one MIDI track, to validate that a real-time freeze render works on my system, just in case there was a potential issue there, and it was successful, although on a the first render the rendered audio misaligned with the midi, on unfreezing & re-freezing the alignment was correct. Second, I ensured everything on your list was adhered to, and just for the record I’m usually, as in this case, careful about my project ends. My project end for this project was clearly defined by the “Go to End” button of the “Now slider” such that a select all (CTRL+A) terminated at precisely that endpoint. Regardless, there’s still something amiss, just as previously described, the render failed to occur and the “Now Time” line moves indefinitely well beyond the project end and the “Freeze tail duration” until the render was canceled... The only thing I can add is that the only other option selected was “Remove silence” and this failure occurs with either dual mono or single stereo outs in this project, and with either "FX" on or off. For me, this is not a critical issue, it's just that sometimes synths glitch, particularly Kontakt, during a bounce regardless of buffer size and one way to eliminate this it is to isolate the track via a freeze , and a real-time audible freeze might be useful. Once again thanks... Update: @msmcleod - Sir it appears there is an edge case for the failure described above. Namely the failure only occurs when the synth output is an aux track. I confirmed this in a test project , one synth out set to an aux track, the aux track set to a hardware output & and one MIDI track and no FX plugins , hence I believe this might be a bug. On setting the synth output directly to a hardware output it functions as expected for a real-time and also an audible freeze, so this is a workaround by temporarily resetting a synths out . In my current project all my synth outputs are to aux tracks, so anyone of them would fail for a real-time freeze

Freeze bug: 2022.06 (build 34) Selecting the "Render in Real-Time" option in the "Freeze Options" causes the render to fail on freezing a track. The Now Time line begins to move and continues indefinitely without a render bar activating until the render is canceled...

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...