Ben Staton

@torhan Thanks for the report. Unfortunately, we can't reproduce it here, but we're aware that issues like this do happen in rare circumstances. If you see it again, please would you post a screenshot showing the entire Cakewalk window? That can often give us clues that a more localized screenshot can't, such as the general layout of all views at the time it occurred. Thank you! In the meantime, resizing the window (or un-maximizing it and then maximizing it again) usually fixes it.

@Herve Maratrey I just PM'd you a link to a new installer. Hopefully, that will fix your problem. Please let us know how it goes. Thanks again, Ben

@Herve Maratrey We're currently testing a fix for this, which looks very promising. Is it OK if we send you a new build to test?

I'd also like to know which languages you have Windows and Cakewalk set to. It may be relevant.

@Herve Maratrey Please would you also check the Arranger by opening the 'View' menu in the Track View, and then choosing 'Arranger Track Show/Hide'? We're wondering if that also causes a crash for you. Thanks!

Hi @Herve Maratrey, Thanks for the report. The crash dump suggests there might be an issue with DirectX on your PC. Firstly, I would make sure that your graphics driver is up to date. If that doesn't fix the problem, you could try running dxdiag, which is the 'DirectX Diagnostic Tool' that comes with Windows 10. It might highlight any DirectX problems and help you to resolve them. Failing that, dxdiag has a 'Save All Information...' button at the bottom that will save a file containing information about your DirectX installation. If you send that file to us, it might give us some clues (check it first, to make sure you're OK with us seeing the information it contains). Please let us know how you get on. Thanks again, Ben

Thanks for the report. This bug has been reproduced and logged. No guarantees, but hopefully we'll get to it soon.

Hmm, this is a tricky one. Cakewalk literally does nothing at all to change or ignore the Windows scaling setting. It neither opts in nor out of it. Essentially, it just throws its hands in the air and says "Hey Windows, I know nothing about high DPI, so you take care of it!". Do you by any chance have multiple monitors? If so, do they have different resolutions? Do you always run Cakewalk on the same monitor? Do you ever run Cakewalk on another display, whether it's temporarily plugging in a different monitor/TV, or by running it remotely (via Remote Desktop or similar)? Do you change the Windows scaling setting occasionally (nothing wrong with that, but it might be a factor)? I'm also wondering why you're running Cakewalk with admin permissions all the time, which shouldn't be necessary. If Cakewalk is somehow affecting it (again, I fail to see how, but stranger things have happened), running it without admin permissions might prevent it from doing so. If anyone else is running into this, please let us know. I'd like to get to the bottom of it.

Nice idea, but I don't think that's the problem. While we use some CJ stuff, most of the UI is built using other technologies, and this seems to be an app wide issue.

I'm struggling to think how CbB could change your high DPI scaling override setting. I know we aren't doing anything out of the ordinary. On start-up, CbB just tells Windows to handle scaling on its behalf. I wonder if Windows is trying to be 'clever' and is changing it because it thinks it knows better?! A while back, I came across a plugin that was calling Windows DPI scaling functions, which it definitely shouldn't have been doing under any circumstances (it's the hosts job to worry about things like that). Maybe one of your plugins is misbehaving? That might explain it. I did some Googling, and app compatibility settings (of which high DPI scaling is one) are stored in the registry here: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers @jono grant If you're familiar with the registry, please would you send me a screenshot of the Cakewalk.exe entry in there? You might want to try deleting it to see if that makes any difference (at your own risk, of course). FWIW, I tried setting the high DPI scaling override and then deleted the corresponding registry entry with no ill effects.

Hi Jono, That's very odd. I haven't heard of anything like this, apart from maybe one guy who had to set some custom DPI settings or CbB would crash on startup (which should now be fixed anyway, at least in the latest Early Access release). When you say "I'm continually going in and having to set the scaling over and over again", what is it that you're doing specifically? Are you going into Windows Settings to set it to 150% again, or something else? Also, what version of Windows are you using? Thanks, Ben

A fix for this will be in the next release!

I'm working on a fix. In the meantime, using Alt+Tab to switch to another application, and then going back to Cakewalk, seems to 'un-stick' the mouse so you can continue working.

Thanks for the reports. We've logged this issue, and I'm investigating it now. When it happens, does the little zoom window remain visible on-screen, or does it disappear but the mouse is still stuck? Thanks!

@Angelo DiBraccio Thanks for the crash dump. That should pinpoint the code in question. Investigating... Edit: The crash dump helped me find the cause. I'll try to fix for the next release.

@Angelo DiBraccio Thanks for the quick response, Angelo, and for the extra info/screenshots. By default, the 'Override high DPI scaling behavior' checkbox should be unchecked, but I realize that causes the startup problem in your case. It's possible that checking it will cause some layout issues, but you might be OK because your 'Scale and layout' setting is 100%, so there's no scaling involved either way. I've tried to reproduce without any success so far. I'll let you know if I figure it out, but I'm pleased to hear you're up and running anyway.

These example screenshots show the kind of info I'm looking for:

Hi @Angelo DiBraccio Very strange. I'd like to investigate, but I need a bit more information. Firstly, what version of Windows are you using? Secondly, please would you attach screenshots of these three things: 1. Settings -> Display (the 'Scale and layout' section, in particular)? 2. Right click on Cakewalk.exe, choose Properties from the menu, then select the Compatibility tab. 3. Click the 'Change high DPI settings button'. That might help me get to the bottom of it. Many thanks! Ben

That's great news! Thanks for the update Michael.

Hi @Michael Vangerov, Apologies again for the delayed response. I still have the video you sent a while back. At least I think I do (the above link has expired, so I can't verify). It's the one showing you queuing a song during playback, which then opens with 3 minimized Lyrics windows that remain minimized when the song begins playing, right? As far as I know, that particular issue has been fixed for a while now. Can you confirm you're no longer seeing it? Regarding the screenset issue, I admit I'm still not 100% clear on what the problem is. Would it be possible to share another short video that demonstrates it? Alternatively, maybe a remote session (eg. via Skype or Google Hangouts) would be helpful if it's convenient? Thanks for bearing with us, Ben

@Canopus Thanks. I've logged the scroll bar inconsistency. Unfortunately, it might be a while before we get to it since we're very busy working in other areas of CbB right now. That said, we're hoping to give the UI some much needed attention later this year.

@jono grant I'm also using 4K monitors with Windows 10 at 150%, and haven't noticed CbB doing anything unusual (it always opens at 150%). As far as high DPI support goes, CbB asks Windows to take care of scaling the UI, and that's all there is to it. We're not doing anything beyond that, so if there's a problem, it could be a Windows issue. Firstly, are you using Windows 10? If not, which version? All bets are off if it's Windows 7 I'm afraid. As well as no longer being supported, high DPI support in Windows 10 is much improved over Windows 7. Secondly, I notice the 'Override high DPI scaling behavior' checkbox is checked in your screenshot. Unlikely, but FWIW it's unchecked on my PC (which I believe is the default). Edit: You mentioned that CbB is the only app with this issue, but if it's also the only app that you've changed high DPI settings for, then it could still be a Windows issue. Edit 2: I see from your screenshot that you're on Windows 10, not 7 or 8, since I can see 'Windows 8' in the 'Compatibility mode' dropdown!

@Michael Vangerov Apologies for the late reply. I've been crazy busy lately, and completely forgot to get back to you. Fortunately Noel noticed this thread and nudged me yesterday. The good news is that I already fixed the issue you reported in your original post, so you might want to try the latest release (2019.11) and let us know how you get on. Regarding the other issues you reported, I'll need to spend a bit more time investigating those, so please bear with me. I'm on leave for the Christmas period, but by all means PM me in January if you have any further information, or are just looking for an update.

Thanks for the report. That definitely shouldn't happen! I'll get it logged and hopefully fixed in the next release.

Good news! @AxlBrutality and I finally got to the bottom of this, and his issue now seems to be resolved. I'm pleased to say that it wasn't a Cakewalk problem. Indeed, Reaper exhibits the same symptoms with the same plugins. The instability was down to a gaming utility called Nahimic Sound Tracker, which is, I believe, installed by default on some MSI systems (an MSI gaming laptop in this instance). It runs in the background, and displays an in-game HUD showing where your opponents are based on any sounds they make: https://www.nahimic.com/gamers/ Uninstalling it fixed the problem. They have 15 million users if their website is to be believed, so it's possible other DAW users are running into it too. I strongly advise anyone running a DAW on a gaming rig to uninstall any unused gaming utilities, or at the very least disable them when running DAW software.