Tez

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

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.

@Craig Anderton I read in your article on the TTS-1 synth, that it won’t function at function at 88.2kHz sample rates. I created a 44.1KHz project from a multi-track Midi file for the Microsoft GS Wavetable Synth, where I used all the non-percussion MIDI tracks in equivalent VSTis, but the percussion was simple enough to use the TTS-1s channel 10. I set all VSTs, VSTis and the TTS-1 in the project to “Upsample on Render” and bounced 2X to a track and the percussion came out fine, which implies that 88.2kHz sample rate works for the TTS-1 or CbB ignores upsampling for the TTS-1. So, I’m a tad confused. Would you kindly explain if I’ve got it wrong? Thanks...