Tez

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

@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 🙄

This post maybe, should have been added here. Is anyone else experiencing this?

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