Noel Borthwick

Your file did not attach properly.

@LeVonne E Johnson Jr the dump you sent was from build 88 which is earlier. So you get the same crash in build 93? You can upload the dump file to any file share like onedrive or google drive and send me the link. This is the preferred way to do it. Also zipping the file will save a lot of space. Something to try. Instead of opening the project from the start screen, please close that and open the file from the main application file menu. Or try File | New. Let me know if that works. How were you opening your project when it crashed? Its crashing because something has prevented the app from initializing fully according to the dump. I suspect that something failed when initializing your audio device. Do you get any error messages?

Please attach the minidump file listed in the error message so we can establish the cause off the crash. Have you tried the latest update release that we plan to release soon?

Another updated build was posted today fixing some reported issues.

A new build was posted that fixes the issues posted in this thread. This will be the last build before we release this officially so please try it asap.

@Herve Maratrey it seems like you are running a really old laptop with a very old BIOS from 2011. It is very underpowered by todays standards and only has 4GB of RAM. At least for the graphics and memory - the CPU is a quad core which should be fine. What is the PC model? BIOS: BIOS Date: 08/10/11 12:28:49 Ver: 04.06.03 (type: BIOS) Processor: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz Memory: 4096MB RAM Available OS Memory: 4002MB RAM Page File: 4818MB used, 3534MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 There are no obvious errors in the log but my guess is our code is incompatible with this version in some way. User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) Can you temporarily change your DPI scaling in windows back to 100% and retry to rule out a scaling problem?

No it doesn't. Once imported the data is lost since the file is transcoded. You will need to redo the data if you reexport.

@steven galutia Can you provide some more information such as a video or screenshots of the problem you are seeing? Also which version of CbB were you using prior to updating. There are no changes in this version that should impact this so there may be some other factors leading to your issue.

The articulations are actually stored in a clip. We'll evaluate of it can be excluded from selection.

Well the articulation is data on the track so this is not that surprising I think? The same happens with envelope data.

Thanks for reporting it. I can reproduce it and well fix it for the main release.

@Andres Medina All three of your dump files are the exact same crash in Vienna Synchron player. Its not related to our release. You should contact Vienna since only they can solve this issue. I will also forward the dump files to them. Your stacks do not show that you are trying to save templates. When do the crashes occur - after the save? You may need to send them the project you are using to reproduce the crash as well since often the dumps are not sufficient. Unhandled exception at 0x00007FFE8B04007B (Vienna Synchron Player.vst3) in Test Articulation Maps Strings ref5_11212020_154833.dmp: 0xC0000005: Access violation reading location 0x00000000D5936058. Vienna Synchron Player.vst3!00007ffe8b04007b() Unknown Non-user code. Cannot find or open the PDB file. Vienna Synchron Player.vst3!00007ffe8aff8803() Unknown Non-user code. Cannot find or open the PDB file. user32.dll!UserCallWinProcCheckWow() Unknown Non-user code. Symbols loaded. user32.dll!CallWindowProcW() Unknown Non-user code. Symbols loaded. > mfc140u.dll!_AfxActivationWndProc(HWND__ * hWnd=0x0000000000200968, unsigned int nMsg=1024, unsigned __int64 wParam=0, __int64 lParam=0) Line 478 C++ Symbols loaded.

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.