GreenLight

It might not be the cause in this case, but there are reports of problems with unbinding shortcuts that are not related to Workspaces, see topic link below.

Very well put! I thought about that as well – using the same shortcuts for different actions in different views – and how that could be really nice in some scenarios. For some time I've been using NUMPAD + and - for zoom in/out in Track View, which btw has been a great workflow enhancer for me. And then I thought it would be cool to use the same combo for zoom in/out in PRV as well... but maybe it's a bad example, since it has been very convenient to be able to zoom in/out in Track View even when working and having focus in PRV.

Ok, my aim is always to try to write forum posts that have constructive content and that are useful and interesting for the topic at hand, but...

I have now checked how my Cakewalk is configured: "Save Changes for Next Session" is checked under Preferences/Keyboard shortcuts. I don't think it's ever been unchecked. Workspaces are configured as seen below. Are you saying I should enable "Apply Workspace on Project Load" even though I'm not using workspaces? 🤔

Thanks a lot for this, Superrabbit 🐇, very interesting. I have downloaded and installed them and will definitely try them for my next melodic techno track. The page on the B Rock website was very ambitious in its explanation of these. In summary, there are 32 different arp patterns and each of those is also available in 15 different variations, truncated to shorter lengths to make it very easy to achieve polyrhythms when layering them on top of each other or other sequences. Cool! It makes me think of the arp in U-He's Diva synth. It has a Restart parameter which lets you do the same thing, i.e. it allow you to restart the arp sequence earlier. Very useful for more organic patterns!

Thanks for chiming in, Peter, interesting to know there's more with the same problem.

It would be fantastic if the "Global" aspect/concept you describe could be indicated more clearly in the Preferences GUI. It is a bit confusing the way it's currently displayed. 🥴

Appreciate your help, as always, Will! Will (pun not intended) check it out. 😁 (Note though that I'm not using workspaces nor screensets.)

I have tried to find some pattern in the disappearing shortcuts, but have so far not succeeded. As a backup, I constantly export my binding setup as soon as I make any changes to my shortcuts. I try out new configurations pretty often, so I have a lot of backups. About the "unusualness" or "system-specificness" of this problem – all I can say is that I have reported in a bunch of very odd, and very difficult-to-reproduce Cakewalk bugs lately, that the Bakers have fixed swiftly and competently once I managed to reproduce them and report them. Some of the bugs to me literally years of enduring to get a repro on (I'm looking at you, "preview bus suddenly changing bug". The obscure bug existed for years, and it was very annoying for me! But victory to those who persist! 😁) As I wrote elsewhere in this forum recently, I think the Keyboard shortcuts preferences part of Cakewalk could use a facelift (not least with the long delays in opening the window) a trip to the gym and makeover, if you so will. 🏋️‍♂️🙂

I also have the problem of my own bindings occasionally randomly unbinding... it's very annoying. I am not using either Screensets or Workspaces. @Michal Ochedowski Did you isolate your shortcut unbinding problems to Workspaces?

Brilliant, thank you for the fast work!

Thanks a lot, mate! Always appreciate your input, David. Pinging @msmcleod... Houston, we have a bug! 🚀😃

That's a very interesting workaround, I will give it a try. Thanks for the tip! 👍

You describe Cakewalk's scaling problem with current hi-res/hi-DPI screens correctly. Unfortunately, it's difficult to find a good compromise with that screen size and resolution. There are some small mitigations that you can try with Windows' High DPI settings on the Cakewalk shortcut, I think they were described earlier in this thread. As I created this thread, I thought a lot of people would have problems with it, but surprisingly many don't. For example, the people responding in this thread are either using very large screens (32") or lower resolutions, creating situations where you don't need scaling. Then there are probably also those who don't care or notice if things are a bit blurry as well... Noel from Bandlab said a couple of years ago that they are aware of it: "This is a known issue and we have plans of gradually addressing it. Its not impossible but its a significant amount of work for the UI to fully handle DPI scaling in the app"

I really appreciate all the work you put into this, and together we will improve Cakewalk, but I believe your findings will make a bigger impact if put more succinctly. Let's start with the the looping issues... first, are the two bullet points above talking about the same thing? I use looping all the time but cannot recall having problems with automation being ignored in a loop. (I mostly edit my automation on the main track, without expanding the automation lanes, but I wouldn't think that should make any difference.) Is the looping issue reproducible for you?