Ben Staton

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

Hi Adam, Thanks for reporting this. I've been able to reproduce the problem, and we'll try to fix it for the next release. Ben

I've been able to reproduce the Browser plugin layout crash. Thanks Esteban, we'll get that fixed ASAP.

Hi Bill, That doesn't seem right. I'd expect to see something more like this: Any chance you could PM me a copy of your project? If so, I can take a look and try to figure out where it's going wrong for you. Thanks! Edit: The light gray colors are there to indicate muted clips (not shown in my screenshot). Could that be what you're seeing?

Hi all, So the 'ghost cursor' thing is a known issue that shows up from time to time. We know what causes it, but it's not a trivial fix so please bear with us while we figure it out. Fortunately it's totally benign, and tends to clear itself up quickly. @winkpain Your issue is unrelated but no less important. Thanks for the video, which is always useful when tracking bugs down. In your case it helped me to reproduce the problem right away, and we'll try to get it fixed for next release. Thanks! Edit: @winkpain I just fixed your specific issue, so look out for it in the next release. To clarify, we're still working on the ghost cursor issue, which isn't resolved yet.

Thanks for the report. I've managed to reproduce the problem, and have logged it. Hopefully we'll get to it in the next release.

We ran into this recently too, and logged it with Focusrite. I believe they're looking into it. I suggest maybe rolling back to the previous driver version and/or sticking with ASIO mode. It also wouldn't do any harm to log it with Focusrite directly.

I know Jon and Morten are on the case re clip help text issues, and the floating Help Module issue is also logged and in my queue for the next release hopefully ?

Good suggestion. I'll log a new feature request so we don't forget.

lol, that's me misusing online shorthand for "Original Poster" (ie. you)! I meant to say "described by the OP". Keep an eye out for the next Early Access release and let us know how you get on ?

Thanks for your feedback. I've already fixed one of the issues described in the OP, and another is in the works. Look out for fixes in the next release, or consider participating in the Early Access Program if you want to try it out sooner (release dates tbc).

Thanks for the detailed report. I've been able to reproduce the bug, and will look into it later today. Reports like this are extremely useful to us. It's impossible for us to fix a bug we don't know about, or can't reproduce, so thanks again for reporting it and including all the necessary steps ? Edit: Fixed! Will be in the next release.

It should already be possible to switch lenses without changing the window layout. 1. Open the 'Lens Manager' (select 'Manage Lenses...' in the Lenses dropdown menu). 2. Select the lens you want to modify. 3. Uncheck 'Window Layout' in the 'Settings' section. 4. Click the save button to save your changes. Now, whenever you switch to the above lens, your window layout won't change. As Noel mentioned, lenses are a superset of screensets. By following the above instructions, you're effectively turning off screenset functionality for your lens. Does that help?