Tez

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

It would seem you're right. I set only the Vsti (Pianoteq vst2) to Upsample On Render and the Fast Bounce worked just fine. FYI: The plugins used in the previous case were all Ozone 9 individual vst3s from Ozone 9 Advanced. Hope this helps...

Upsample On Render Setting a VSTi to Upsample On Render for better performance and the FX plugins used, I found these issues using Fast Bounce. With the VSTi and 1 FX plugin set, the render proceeded at the pace of geologic time and hence canceled the render, with more than 1 FX plugin set CbB crashed without a dump. Is this a bug? I found nothing in the documentation prohibiting Fast Bounce for Upsampling... Not using Fast Bounce works fine!

Upsample On Render Setting a VSTi to Upsample On Render for better performance and the FX plugins used, I found these issues using Fast Bounce. With the VSTi and 1 FX plugin set, the render proceeded at the pace of geologic time and hence canceled the render, with more than 1 FX plugin set CbB crashed without a dump. Is this a bug? I found nothing in the documentation prohibiting Fast Bounce for Upsampling... Not using Fast Bounce works fine! PRV copy/paste Under Editing, “Use Paste Special Options on Paste” and Under Paste Special “Paste into Existing Clips” are both selected, but in a MIDI clip in the PRV, when a copy of a note sequence from one part of clip is then pasted into different location using Ctrl + V, it’s pasted as new clip the length of which is equal to the start of the sequence being copied to the end of the original clip. This forces the use of Paste Special to paste into the existing clip, is this a bug?

Agreed, if you don't know exactly what your doing, e.g. any midi tracks associated with a shifted synth have to have their outputs reassigned to the new position, similarly if it's a percussion midi track using a drum map, the map assignments have to be reassigned to reflect the position change. Regardless, shifting synths in the rack ain't something I'm inclined to do anyway, and if I really wanted too it would be done carefully...

Take a look at this post: http://forum.cakewalk.com/Palliative-alternative-to-reorder-synths-in-the-synth-rack-m3588508.aspx#

I learned something so, checked boogex out, you're right! The Cabinet Sim/Convolver is mono, guess that means it's a mono plug and on a stereo track it's only left sensitive, I wonder if that's typical for mono plugs?

Thanks again, I am aware of Launchpad, and appreciate your generosity in providing useful tools, it was the compatibility check that was a news update that I'm glad to know, and in general I've never rolled back, my interest is a comparison between current and previous for some feature at best, if at all 😊

That's good to know, thank you, and I assume for automation you're referring to CW130Auto.dll, and of the 4 dlls that have gotten updated this release, that CW130auto is the pertinent dll as I think Splat also uses 3 of the updated dlls plus CW120Auto.dll. The others in shared utilities appear to be no later than 2019. So, going forward keeping a copy of the current CW130auto along with the "Cakewalk Core" might be an idea if desperate to run a prior version of CbB, unless the compatibility check some how prevents it?

This has to be so, because I assume by that, changes can occur to folders other than "Cakewalk Core" but FWIW I keep all versions of the "Core" backed up and I was able to run "Cakewalk.exe - 2021.01 bld 098 (Update 1)" from a renamed "Core" folder, and this version has the prior tempo features operable, maybe that's all Sam Stalos requires? This time running a prior version to the latest currently installed, I saw that there was no notice that a newer version was available, and following that on a startup of the current CbB there was a refreshing activation notice?

Ditto

I think you misunderstand, no offense, the shell loads 3 distinct 64 bit plugins which only get scanned once when the "shell plugin" was first installed and the vsts are registered, after that it's just the shell that gets scanned each time CbB starts up, the shell is just the front end for each plugin which the shell extracts, in my case, from a "WavesLib1.14_12.7_Win64.dll" file, there is no individual vst plugin dlls or vst3 files except the shell which for the vst3 is "WaveShell1-VST3 12.7_x64.vst3". Now I'm assuming that the shell maybe generic, capable of loading vsts from other libs if and when a new lib is installed and then the vsts that get loaded would be scanned when first registered. Again, no 32 bit plugins are involved and plugins loaded by the shell are scanned when first registered, and appear in the plug-in manager. It's possible the shell gets scanned every time to see if a new lib was installed, that's my conjecture. As for AAS the old installers splattered vsts all over the place, I know all the locations, but the only ones I'd delete were in the Cakewalk\VstPlugins folder the only location on my CbB's and Splat's vst path I didn't specify. The new installer is cleaned up putting the 3s in the default location and the 2s where you tell it, yahoo! I believe I saw this in one of your prior posts, that was what I implied by "a vst3 may not be suitable for all cases" and FWIW I also seem to remember that some vst2s were needed to take advantage of NKS support despite an available vst3.

Yes, it's a matter of choice keeping both vst2 & vst3 versions of a plugin, a vst3 may not be suitable for all cases depending on the plugin and it's intended use. In this case the shell loads all 3 plugin flavors so only the shell needs to be on the CbB's vst path, and it seems that the plugs the shell loads get scanned once on the first time loaded, but the shell gets scanned each CbB startup, this behavior, albeit normal for a shell, was something new too me hence the OP. Regardless the shell scan is lightning fast. The plug-in manager lists all plugins loaded by the shell with unique VST IDs, but all have the same filename which is the shell's and there are no individual .dlls or .vst3s for these VSTs which I think are embedded in a lib .dll file 🙄...

I think basically you're right which is good to know & now to be expected thank you very much. This plugin loads in 3 flavors and on an initial 1st time scan I'm sure I saw multiple scans resulting in 3 new plugins per vst2/3, but on subsequent startups it's seems only the shell for each vst gets a token scan which is really fast and not significantly adding to the startup time, if at all. So, right now an auto scan is just fine.

My scan option is set to Automatic Background Scan, and typically on a CbB startup when there’s no new plugins the scan popup will show either searching for plugins and/or the Scan Complete no new plugins found list and no plugin scan notice, but since adding a Waves Audio plugin this shows up as being scanned, albeit very swiftly, prior to no new plugins found list each time on a CbB startup. The WA plugin is an indirect Shell to the actual plugin, is this why the scan occurs or, in general, a quirk of Waves Audio, or something else?

I second the question, maybe you'll get a reply, I didn't see my post It's the same issue but as a reply in a different topic. good luck...