Noel Borthwick

Which version of Cakewalk are you running? In case you can't open the app you can check the version in windows via the file properties of the exe file. Make sure you have installed the latest 2020.11 release which is build 99. If you are unsure you can uninstall the program and then re install via bandlab assistant.

@Erlend Holm your crash is different from the OP, its not the same issue. Its failing in the Waves 12 shell. This is something you will have to follow up with Waves on since its their crash. Please contact waves tech support and give them the same dump file AND the track template containing the waves plugins. If you send me the template file I can also forward it to them. Unhandled exception at 0x00007FFA19D6B3C3 (WaveShell2-VST3 12.0_x64.vst3) in Track 1_11282020_015537.dmp: 0xC0000005: Access violation reading location 0x0000000000000019.

Are you running the latest version of Cakewalk? Which browser drop down are you referring to? Please post a screenshot.

Yes if the request for to check for an update took long it was delaying the app start. This has been resolved.

There have been no changes to that area in the .11 release. What build were you running before you upgraded?

Historically I've found Intel multicore systems to be more deterministic with realtime apps. But I've been out of the loop with AMD for awhile so don't know much about how they stand up today.

Yes its possible that the other virtual cores are being preempted by the OS and not able to process as much as the main cores. @Jim Roseberry may know more about that CPU. Lookahead is really pre-buffering in parallel. Its possible at some point for us to look into. Of course that will cause latency when playing since audio is being processed ahead of time.

Interesting. I don't know much about the internal architecture of that CPU but are the virtual cores running at lower speed than the physical ones? That could explain why this helps because if a high workload is assigned to a low powered core it will delay the rest of the processing by that amount. In real time multithreaded streaming the thread that takes the longest processing time will scale down the performance since all other threads have to wait for it to complete before a buffer is complete.

Have you enabled the option to give keystrokes to the plugin in the plugin view?

The 2020.11 update 1 release is now available (help | check for updates). This fixes the above issue along with several others.

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.

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

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.

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.

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

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.