Noel Borthwick

Read the release notes. Rollback instructions are there. Which version were you using earlier? We don't have any uad systems to test on. Before rolling back make sure you try the latest 2020.11 release that we posted on Friday.

I'll send you a link later. The rollback will take you to the previous major update. I don't the original .11 release will make any difference since i think the crashes are in synchron.

The symptoms sounds exactly like the bug I fixed that's why I wanted you too retest with the new build.

Thanks we'll investigate it.

Not seeing any crash here. It may be related to your video drivers. Can you send a link of any loop you used just to verify that its not content related?

The simple answer is that you have it because you paid for it. There was never a plan to give away all the Cakewalk plugins free. Only the DAW is free.

Why am I sure that if we disable that behavior some will yell that they relied on it BTW its not double clicking that does that. Double click inserts the audio into the current track. What you are seeing is clicking twice on the same file after a short delay. That triggers the rename behavior like it does in Windows explorer itself. Its totally normal Windows behavior in a file browser that we are inheriting because that is a browser control.

Its definitely possible to start auditioning from anywhere within a section. Two ways: 1. First set the now time on the transport where you want to start from. Then CTRL click the play button on the arrangement section (lower pane in arranger) that you want to start from. Playback will start from the set time within section that you clicked on. 2. First set the now time on the transport where you want to start from. Then press SHIFT-ALT-SPACEBAR. Playback will start from the section that intersects with the set time but from that time rather than the section start.

@Matthew Sorrels I think this is related to anything in CbB directly but well investigate. Is this reproducible? It looks like something in GDI+ got hosed when drum replacer was shutting down. > GdiPlus.dll!GpRuntime::GpLock::GpLock(class GpRuntime::GpLockable *) Unknown Non-user code. Symbols loaded. GdiPlus.dll!GdipDeleteBrush() Unknown Non-user code. Symbols loaded. DrumReplacer.vst3!doexit(int code=0, int quick=1, int retcaller=1) Line 628 C Non-user code. Symbols loaded. DrumReplacer.vst3!_CRT_INIT(void * hDllHandle, unsigned long dwReason, void * lpreserved=0x0000000000000001) Line 169 C Non-user code. Symbols loaded.

@Graeme S Brown Can you please try the latest 2020.11 update 1 preview release that we posted today and report back if it addresses this issue? If it still hangs on the splash screen even after this change, capture a minidump for the hang using these instructions and send me a link to a zip file for the same. (it will be big)

This was a limitation for the bypass automation in the Prochannel. It would only work with realtime bounce. I've redesigned it to be independent of playback speed for a subsequent update.

Hi folks, We posted a preview build for update 1 that fixes several user reported issues with the 2020.11 release. We plan to release this very soon but if you were affected by any of the listed issues please download it and report back if it solves your issues here.

Hi folks, We posted a preview build for update 1 that fixes several user reported issues with the 2020.11 release. We plan to release this very soon but if you were affected by any of the listed issues please download it and report back if it solves your issues here. Thanks for all the great feedback.

@Tim Davila I looked at this. The crash has nothing to do with console emulator. Its crashing with an exception in the Waves Shell. VCRUNTIME140.dll!_CxxThrowException(void * pExceptionObject=0x000000000014b020, const _s__ThrowInfo * pThrowInfo) Line 75 C++ Non-user code. Symbols loaded. WavesLib6.1_11.0_Win64.dll!00007ffe05aac889() Unknown Non-user code. No matching binary found. Can you PM us a link to the project file? We can forward it to Waves along with the dump for their analysis. This is not a bug in Cakewalk.

Nice video @babylonwaves

This issue is also caused by a bug in the latest VST3 SDK that we updated to recently. Its the same issue that was affecting strings in some plugins like Console One, Waves and Izotope Neutron. I've fixed the issue and notified Steinberg since the bug will affect any host using the latest VST3 SDK. We'll include the fix in the next maintenance release which should be fairly soon.

Hi Folks, It turns out that this problem is caused by a bug in the latest VST3 SDK that we updated to recently. I've fixed the issue and notified Steinberg since the bug will affect any host using the latest VST3 SDK. We'll include the fix in the next maintenance release which should be fairly soon.

I think this thread is confusing bounce with freeze. The main purpose of freeze is to render instrument tracks to audio in-place AND completely release the resources for the instrument. It does exactly that today. If I understand correctly some users want a shortcut to bouncing a instrument track MIDI to an audio track. This cannot be done in place to the same instrument track because it would double the audio. You can already bounce an instrument track to a different audio track from the bounce dialog. I guess I'm not understanding how this process could be sped up.

Rather than looking at the kitchen sink of chord track like features or what other DAW's do, I'm actually more interested in how you use a feature like this or if you haven't tried it what it would do to improve your workflow with music production.

What plugins are used in this project?

This is the error reported from the dump which indicates a crash inside the Felt Piano module after the synth was inserted. Unhandled exception at 0x00007FFE7EEF6BC7 (Originals - Felt Piano (64 Bit).vst3) in Video_11172020_065320.dmp: 0xC0000005: Access violation reading location 0x0000000000000010.

@Matthew Simon Fletcher please PM me the link as well as the case number you have.

@Osman Hamidov Could you send the project file to take a look at this? You can PM it to me. Edit: Congratulations you just found a bug dating back over 20 years ? It will be fixed for the next update.

Good catch. @msmcleod we can do some checks for invalid characters in names that can prevent the file being parsed properly.

He was suggesting that you switch from ASIO to WASAPI and open the same project and check if the pictures are recomputed. PS: please check your PM messages.