sjoens

Not sure if that applies to CbB but I'm currently testing it on my Win11 system and it's working correctly there. I will miss Win10 but it's just too buggy anymore and sanity is too valuable of a commodity to mess with going forward.

Bouncing clips would sometimes remove clip names but I've never seen tracks lose their names so not sure what would cause that.

My guess is most users use one or the other, not both, so they never noticed.

If you keep the default name, Replace synth will change it. If you type in a new name, Replace synth seems to keep the one you typed forcing you to change it again.

Unfortunately the reference guide uses screenshots from CbB with raster graphics, so not a good reference for this.

Just checked it on a Windows 11 system and it works as expected, so it must be a Windows 10 issue specific to my laptop. Just one more glitch telling me it's time to retire this one.

Most bizarre issue with new 34" Samsung ViewFinity S5 monitor (3440x1440) when it's zoom is 125% or higher. Issue: Oversized buttons and text. Affects: most Cakewalk plugins. Issue persists when UI is opened after screen zoom is set to 125% or higher. No issue if screen zoom is 100% before UI is opened even if zoom is changed afterward. No issues with 29" LG Ultrawide (2560x1080) monitor. Only happens with plugin inside Cakewalk. Standalone displays correctly.

If you have Boost 11 it shows graphically what's happening to the sound.

Not all mouse sensitivities are created equal, so the slightest movement in the wrong direction can be applied before you even think you moved the mouse.

Interpret this as you may, but if Cakewalk has proven anything over the years it's how different it operates on different systems by different users. The magnetisphere may be messing with you as well.

Holding Shift should lock the clip horizontally when dragging up or down to another track. Make sure you're not moving the mouse even the slightest bit right or left when dragging as it can be touchy. Other wise it could be a bad key so check both left & right Shift keys. Then try a different keyboard.

Today the window opened normally when I posted in another thread. Then I watched it switch to this broken one before I started typing. So something's misbehaving. Maybe this glowing symbol on the lid has something to do with it... ¯\_(ツ)_/¯ Probably explains everything.

Still happening (not even a day). I'm writing this off as unfixable barring a full system reinstall. Maybe the last Windows update for Win10 will fix it but I'll probably move on to another PC b4 then.

In MOTU world "hybrid" means USB. The original mk3 was firewire only and is discontinued including driver downloads as the hybrid drivers work on it too. I bought this unit used and reached out to see if I can get it re-registered in my name but no answer yet. Other forms of comm are currently unavailable. I posted on MOTUNation but the few responders weren't that helpful. The issue is probably unique to me only. I'm giving the last round of troubleshooting 2 or 3 days before I say more.

SFC found an repaired several files. DISM only says it completed successfully. During the wait I remembered we've had a couple of power outs/spikes that may have contributed some issues.

DC power is a given for me and I never rely on USB power if there's an option. (The MOTU MIDI micro lite is USB only) Sorry I always forget the obvious required info - It's the hybrid which has firewire and installs the firewire driver (as noted), but my system has no firewire so never thought it would be an issue as disconnection should relate to USB. It'll take a few days to confirm tho. I originally installed the latest hybrid drivers as they are the only ones updated now. When the issue began, I tried going back to older drivers to verify or eliminate the driver. Since then I've reinstalled the newest ones but the issue remains, so I'm still leaning toward it being a Windows update. Doing that now. Thanks, will be checking those out too.

I interpret the documentation to mean the overall size of the VKB is determined by touch screen or no touch screen, not how many keys it shows. But I can't find anything beyond the help files on it. Speaking of suppositions or theories, I also think VKB coding is internal and relies on how Cakewalk interprets system video settings. Including how many octaves are shown.

Put " @ " before a user's name in your post and it sends him a notification for which he might respond to. You can edit your post to do that. Hover over, or click on, a user's name will show you the last time they were on the forum. If it's been a year or more, they may not respond.

So far all I see is an application error for MFWAKeys.exe which created a series of app crashes and dump files. It's for MOTU Firewire Audio Pedal which isn't used as I have no firewire. I've disabled the file but have doubts it's to blame.

That just simply is not fair! Must be a bug as the tiny octave picker only shows 3 octaves - so which 3 are displayed? Maybe a line in the Initialization file could be added to set displayed octaves??

Aaaaand we're back... to sq1. This time I noticed the system froze briefly a couple of times then went back to working. Then after another freeze up, the dreaded warning returned today. Is there a way to log Windows events to show what's happening to cause the warning?

I've never seen the clip icons disappear, even with Maximize Waveform selected.

The notes disappear? That's not good. Most DAWs do the same. FWIW, Separate clips on one track can be set to open different editing views.

FWIW, the VKB has always had display issues depending on monitor setup. But 5 octaves??? I posted last year about it, but after a complete system reinstall and a new 2nd monitor it's resolved these issues.

If nothing else it marks the end of the clip which is handy when looking for unbounced clips in a track.