Ben Staton

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.

@Illogistical Resource Dept Thanks for the report. Does it happen every time you use the zoom control? Presumably you're clicking and holding the left mouse button to zoom, and at some point you release the left mouse button, but the mouse cursor stays stuck in the zoom box? Did you notice this in earlier versions of CbB? Any other clues that might be relevant? Edit: Is the mouse permanently stuck in the zoom box afterwards, or does pressing Esc, left/right clicking again, or anything else 'free' it?

@Illogistical Resource Dept OK, thanks. That's no good. I'll investigate this soon.

@jimlynch22 and @Illogistical Resource Dept Thanks for the report and workspace files. To what extent are you losing mouse/keyboard input during playback? Just in the Track View (for example), or is the entire app affected, including the Control Bar? If so, how are you stopping playback to regain mouse/keyboard control (eg. by using a MIDI controller)? Is the mouse cursor visible or hidden when it happens? Do you have any plugin windows open at the time? So many questions! Feel free to PM me with the details if you like.

@AxlBrutality FYI, I just PM'd you about this

I had a hunch that Windows 7 display scaling might be involved, so we did some tests and managed to reproduce the problem. In Control Panel -> Appearance and Personalization -> Display, make sure you're using one of the 3 predefined options - Smaller, Medium or Larger: It's possible to use a custom setting by clicking 'Set custom text size (DPI)', but doing so seems to cause this issue. It works fine (for us, at least) if you stick with Smaller, Medium or Larger. If you try that and still have problems, try clicking 'Set custom text size (DPI)' and making sure the 'Use Windows XP style DPI scaling' option is enabled/checked (I think it's enabled by default, but worth checking): That resolved the issue in our tests. Hope it works for you too. Let us know how you get on.

Mike was kind enough to forward your video, so I've seen it, and it was most helpful. A picture (well, video) is worth a thousand words indeed! Thanks again. I'm hoping to send you another build to test at some point next week 🤞

Hi Michael, Apologies for the delay (so much to do, so little time!) I've been working on this over the last couple of days, and have made good progress, but there's still more to do. Leave it with me, and we'll get back to you at some point next week. Rest assured we're taking it seriously, and aim to fix it for the next release if at all possible (it seems likely at this point, but no promises). Thanks again, Ben

Glad you managed to sort it! I already have some ideas for a fix to stop it happening again, which I'll hopefully find time for soon.

Yes, the Alt-Spacebar trick is definitely useful for this kind of thing, Panu! Regardless of the workaround, we should really stop it happening in the first place. I've already logged a case and hope to look into it soon.

One more thing - starting CbB in Safe Mode might help (hold Shift while opening a project). If that fails too, then something very odd is going on. Could you forward a screenshot after attempting to open the CV please?

Now I think about it, just switching to a different screenset might sort it out too! Edit: I've logged a case so we can investigate, and maybe prevent issues like this in future.

Actually, you could also replace step 4 above, with: 4. Press the down arrow key exactly 7 times. And then hit the Enter key. That'll potentially force the CV to dock itself back in the MultiDock. BTW, the Alt+Space shortcut simply opens the focused windows system menu, from which you can move, size, maximize, dock etc, hence the down arrow and Enter key steps above: I'm working on the assumption that your CV window is there somerwhere, but is off screen or otherwise obscured somehow.

Very unusual. Haven't come across anything like that before. Be sure to look around for a very small, minimized CV window, just in case it somehow got itself into that state. It might look something like this (on Windows 10): If you see it, just maximize or resize it to get it back to a normal size. Failing that, instead of reinstalling CbB, there's a registry key you could delete that might get things back to normal: HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\View Data\{5579470A-A148-431B-838C-89E9F081317C} It contains Console View specific data that, amongst other things, includes its docking state, size and position. If you're comfortable messing with the registry, then close CbB, delete the above value, and retry (with the usual disclaimer - always backup first, and only edit the registry if you know what you're doing). Doing so won't affect your project. If you're not comfortable doing that, or it doesn't work, this is worth a try too (be sure to follow exactly as written): 1. Start CbB and open a project. 2. Press Alt+2 to open the CV. (at which point, presumably CbB will lose focus, and you won't see the CV). 3. Press Alt+Space. 4. Press the down arrow key exactly 4 times. 5. Hit the Enter key. If you follow those steps, it might maximize the CV and allow you to move/resize it! Hope that helps.

Hi again Michael, Your original post says the problem started happening when you installed 2019.09. However, I tested it in 2019.05, and I'm seeing it there too. Please can you let me know which version of CbB you were using before you installed 2019.09? Just trying to find out if it's an old, existing bug, something we introduced with the recent playlist changes, or if we're talking about different things. Thanks, Ben

Thanks for the report, Michael. I've managed to reproduce the problem here, so we'll take a look. No promises, but I'll try to fix for the next release if time allows.

Hi Florian, Please can you let us know exactly what you were doing when the problem happened, and which plugins you were using? We need as much information as possible to help us find the cause. Your original post suggests there are actually two separate issues? If so, please give us clear information about each. It would also be extremely helpful if you could send us a minidump file. See here for instructions: https://www.cakewalk.com/Support/Knowledge-Base/2007013262/How-to-collect-a-Minidump-file-when-your-Cakewalk-program-crashes Thanks, Ben

Hi all, I've been experimenting with this, based on the the feedback here. It's not really an issue when you're showing two or more time formats in the time ruler (MBT, HMSF, etc), because you can click underneath the selection handles to set the Now Time. But there's not enough space to do that when there's only a single time format showing, so I can see how they might get in the way sometimes. Let me discuss it with Noel et al. No promises, but there may be a way to bypass/mitigate the problem. Thanks, Ben