Ben Staton

Regarding mouse cursors, there are some we've yet to update for high DPI. It's logged and we'll get to it in due course. FWIW, obviously they look fine at 1080p, but they also look OK (not perfect, but definitely acceptable) at 4K too. This is because 4K is exactly 4 times the resolution of 1080p, so the scaled up cursors still look sharp, albeit a little pixellated, because one 1080p pixel equals exactly four 4K pixels. 1440p, on the other hand, doesn't match up neatly with the old cursor size like 1080p and 4K do. Since 1440p can't scale them up perfectly by whole numbers, it tries to fit them in between the pixels, which makes them look blurry. It's definitely something we should address. Thanks for the reminder.

Does this happen every time you open the project? If so, please can you PM me a copy of it?

Please can you send a screenshot of your Windows Settings > Display screen, showing the layout of your monitors. It can make a difference when multiple monitors are arranged side by side, on top of each other, or any number of different alignments given that Windows is very flexible in that regard. Thanks 🙏

@Helene Kolpakova I fixed the 3 remaining Browser and MultiDock docking issues (see a couple of posts up). Fixes for issues 1 and 2 will be included in the upcoming release. Unfortunately, the fix for issue 3 will have to wait for the following release. It's too risky to include at the last minute (needs a full beta/EA testing cycle). Thanks again for your thorough reports.

@Helene Kolpakova Thanks for the extra info and report. I did some testing and reproduced all 3 issues. So, to summarize: 1. Custom Browser width is not preserved if Browser is collapsed. 2. Custom MultiDock height is not preserved if MultiDock is collapsed. Not quite the same as the Browser width issue though, since custom MultiDock heights are preserved correctly, except when the MultiDock is maximized. 3. Browser width may become no longer adjustable. FWIW, all 3 are existing issues (ie. not regressions caused by last week's docking fixes). I think 1 and 2 are already logged (I'll check and log if not), and I'll log 3 so we don't forget them. No promises (it's late in the release cycle, and last minute fixes can be risky), but I'll also take a look and see if I can squeeze another fix or two in today.

@Herbert Miron @Kevin Perry Noel and I came up with a fix! Turns out it actually changed back in July with an unrelated fix.

I fixed a bunch of docking issues for this release. CbB is doing some extra work to restore the correct docking layout when loading a project/screenset/workspace, so it's not surprising if there are some minor, noticeable differences. To be honest, what I'm seeing in @Herbert Miron's videos (thanks for posting them, Herbert), although not ideal, doesn't strike me as being particularly bad or cause for concern. To me, it seems like a small price to pay to ensure your projects/screensets/workspaces look the same as you left them. But if you guys are seeing loading delays lasting more than, say, a second or two, then I'd like to see a video of that. It might be worth revisiting. Edit: I notice in Herbert's videos that the Inspector (left) and Browser (right) are both collapsed. I'd be interested to know if the same delay happens when you save the project with them both expanded. If not, that would be a big clue.

Yes, this should work correctly. I just did a quick sanity check. If I float the Synth Rack, then save and close the project, the Synth Rack is floating when I open the project again. Let us know if you still have any problems there.

I can confirm that I fixed this late last week. Thanks for reporting it and for letting us know it's now working for you.

Re issue #2 reported above by @Helene Kolpakova, we're currently testing fixes for that and some related issues (see below). All being well, they should be included in the next release too. Browser/Synth Rack/Help Module docking fixes currently being tested: 1. Browser would sometimes open as expanded even if it was collapsed when the project was saved. 2. Help Module or Synth Rack were docked at the top (above Browser) even if they were below it when the project was saved. 3. Browser docking layout wasn't restored correctly on project load if the Browser was collapsed. This resulted in odd layout appearance and/or incorrect Browser/Synth Rack/Help Module order.

Thanks for the report. Seems to be an isolated incident so far, and I can't think of anything in this release that would cause such behavior. I saw your post about not being able to do a screen capture. Is there any chance you could use your phone to capture it instead? Also, are you running any third party software that customizes the appearance of Windows and/or Cakewalk, and/or influences mouse behavior somehow? If so, it's worth disabling it and trying again. If you do eventually rollback to 2022.02, I'd be interested to know if that fixes it too.

I think we made FX bins scrollable with the mouse wheel post Platinum, so technically it's by design. That is, if the mouse is currently over an FX bin, mouse wheel scrolling will scroll the FX bin, not the parent view. It's useful since you can only see a couple of plugins at a time at default track heights. There might be some minor inconsistencies with the timer Noel mentioned, and we could potentially make it smarter, but it's basically working as designed, and that explains why it's different to Platinum.

Oh, interesting. Same for Microsoft GS Wavetable Synth? It seems OK here, but I'm using Windows 10 English: What language is Windows using? We might be able to duplicate it if we know the OS language.

As far as I can tell, CbB simply shows the name reported by the MIDI device driver. I also verified that our UI is capable of showing Unicode characters correctly in this context (I even tested it with emojis!). I can't reproduce it, but then we only have UWP MIDI devices that return plain ASCII/English names. It's possible that the Virtual MIDI Synth software you're using is returning the name incorrectly when in UWP mode. Does the name show correctly in other software? ps. Thanks for taking the time to share those screenshots.

Thanks for the report. Do you see the same thing if you change 'Driver Mode' to 'MME'? Also, do you know what that port name should actually be? If you can paste it here, then I might be able to reproduce it.

Hi, Thanks for the report. Does the problem only happen while editing text? In other words, does Korean text display correctly until you start editing it? Your screenshot suggests that's the case. If so, there's a known issue with our text editor control which doesn't draw Unicode text correctly. You can still enter Unicode text, but it won't display correctly until you finish editing. That's something we hope to fix in a future update. If that's not it, please let us know and we can investigate. Thanks again, Ben

There's actually a 64 bit version of Spy++ in the same folder as the 32 bit version. Visual Studio opens the 32 bit one by default (via Tools -> Spy++). Since CbB is a 64 bit application, you need to run the 64 bit version of Spy++. On my PC it's here: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\Tools\spyxx_amd64.exe Give that a go and you should be able to view messages.

Very strange! I pinged Fractal Audio tech support and asked for a dev to contact me. Maybe we can work together to figure out what's going on.

Great, thanks for letting us know. I think it's time to remove that setting. It was only ever meant to be experimental/opt-in anyway, and yours isn't the first issue we've seen with it.

Aha! That might explain it. Please try removing the 'EnableWin10DPIAwareness' setting in Preferences -> File -> Initialization File, and then restart Cakewalk.

Thanks for the report. I can't repro @ 300% here though (on a 4K monitor), so some more info would be useful please. Does it always happen, even if you restart Cakewalk/Windows? Are you using the latest version of Cakewalk? What's your monitor's native/current resolution? Which version of Windows are you using? Do you have a custom theme enabled? Are you using any 3rd party apps that customize the appearance of Windows (some are known to cause issues)? Do you have any special options enabled in Preferences -> File -> Initialization File? Are your graphics drivers up-to-date? A screenshot of your entire desktop might also be helpful. Edit: It might also be worth reinstalling PC2A just in case.

We're looking to improve accessibility in Cakewalk soon. Work has already begun behind the scenes, but there's lots to do. It may take a while, but big improvements are coming. Thanks for bearing with us in the meantime.

Thanks for the report. I'm working on some fixes in that area, so I'll PM you to discuss shortly.

Thanks for the report. I'll investigate.

Thanks for verifying. Please would you try adding the following option in Preferences -> File -> Initialization File: EnablePluginMenuFix=1 Then restart Cakewalk and let me know if your plugin menus look any better. To be clear, that option should be enabled by default, so I'm not expecting it to make any difference, but I want to make sure it's enabled to rule out anything unexpected. Many thanks!