Noel Borthwick

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

Unfortunately there is no easy way to capture a minidump for hangs so they are large. As Scook says zip it and send me a link privately.

@ChristopherM Its likely a plugin issue but while its in the hung state capture a minidump and send a link to the dump file. We may be able to see at what stage its hanging and forward to the developer.

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

Good news. I got a message from the Vienna developers saying they have addressed the issue on their end.

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.

@vlefteris did you see this in the release notes? Note: If you are using a non-English version of 2020.11 Update 1 (build 26.11.0.098) and experience blank articulation map menu commands, please download and run the Cakewalk 2020.09 Rollback installer, then reinstall 2020.11 Update 1 (Help > Check for Updates).

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 final build has been released. Head to Help | Check for updates to download it!

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.

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.