Noel Borthwick

Nothing to do with this update. 

I've seen clips not display when the audio driver is not connected.

2022.11 has been released. Thanks for everyone's help and feedback on this release!

Thats great. Thanks!

Sorry but your file is completely corrupted - likely due to HD corruption.
Here is a screenshot of the bad file vs good file in a hex editor. You can see that the data is random in the first file.
It's not just the header the entire file has garbage data in it.

Thats normal. I disable it when MMCSS is off. It's supposed to tell you that the setting isn't active unless MMCSS is on.
When you turn MMCSS off with Enable for ASIO on, we don't clear that state but gray out the box.

>>Running great without either checked.  I'll leave it alone...
One of the mysteries of the universe only UA can reveal/solve.

Yes, the driver is running in MMCSS mode.
Did you capture that with "Enable MMCSS for ASIO driver" on or off?

1 hour ago, Max Arwood said:

It would be cool to have a count of how many have been fixed since Bandlab took ownership.

In the range of 3000 bug fixes. Of course, this also includes fixes in the new features.

1 hour ago, Milton Sica said:

@Noel Borthwick

I downloaded the new EA and it still remains as follows:

- Either delete or change all FX, even if TRACKS and BUS are selected, it only works within the TRACKS or BUS scope, depending on where the right button has been clicked to access the MENU.
If this is the expected behavior then I suggest it be clarified in the functionality detail.

All quickgrouping in Cakewalk has worked this way for the last 10 years or more. Its not new behavior.

CTRL needs to be held down at the time of picking the effect not when opening the menu and you need to have all the tracks selected from which effects are to be replaced.

37 minutes ago, Helene Kolpakova said:

Expectations:

1. Project is opened with both multidock and browser collapsed.
2. Expanding multidock and browser restores their sizes as I adjusted them to my liking in steps 2 and 3 of the scenario.

I suspect 2 is expected behavior and unrelated to workspaces. If you save the project with the multidock expanded and open, it does retain the size and width, correct?

Please note: The main post has been updated to 28.11.0.012

This build contains the following additional improvements:

Quick group support for:

• Track effect bin Bypass
• Track effect bin Delete Effect (hold down CTRL+SHIFT to also remove an effect from any FX Chains within the selected tracks)
• Individual effect bypass

Fix: Orphaned envelope cannot be reassigned after replacing effect

Fix: Envelopes are orphaned after undoing track effect bin Delete Effect

Fix: [Regression] Track Inspector flickers and draws after the main app window is drawn when opening a project

Yes, RME does handle MMCSS properly from the get-go, back in 2008. I'd worked with the driver developer together on this and we came to an understanding. If it's enabled in the driver, they set the thread to pro audio priority. However, I think it defaults to MMCSS off. 
BTW even though cakewalk shows it as 18, it's really running at priority 26. The only way to see that is by running Process Explorer, however. We don't have a way to programmatically get the true MMCSS priority of existing threads unfortunately so it shows as 18.

@Helene Kolpakova To clarify you are saying that both the multidock and the browser sizes / collapsed state is not being retained after open, correct? 
Please deselect a workspace and redo your test. It's possible that the workspace is restoring the view sizes to what they were in the workspace. Remember that Workspaces are a way to set a project to a certain view configuration so if you don't want this behavior, you should select None as the workspace.

Note that the Advanced workspace as shown in your screenshots, is authored with the Window Layout settings checked. This means if advanced is selected, it will always restore the window layout to the workspace, overriding what's in the project.



You can also make your own custom workspaces without the Window Layout checked if so it wont try and force the layout of the workspace.

Additionally, you can turn off Apply Workspace on Project Load from the workspaces menu as below. This should prevent the workspace being auto applied when you open your projects.

Please don't mix multiple issues in a single thread. It gets very confusing for others to follow.

Well, its important to report the version where the problem occurred
It was being implied that the latest release introduced the drawing problem when in fact it did not.

So the history is that back in July, I changed the startup code to work around a bug in Vienna Ensemble that was wiping out queued windows messages to draw the app. I changed it to not defer the final app redraw and instead do that synchronously.

The result of that is that it "opens the stage" so to speak too early now, before some other parts have completed drawing. This makes it look a bit flickery. We now ensure that we handled all queued redraws before showing the final app. 
 

5 hours ago, Olaf said:

 

Anyway, really like this update. And can't wait for the next improvements.

 

Glad that its fixed some of your problems. Some bugs really need repros to find otherwise it can be impossible to triangulate. After working with @Helene Kolpakova  I got a reproducible case for the browser drawing bugs and crashes and that made it much easier for Ben to fix. It was still very complex though.  

Quote

And so I agree with @Milton Sica that mass delete should also be possible (since mass insert and replace already are), following the same principles, and ALSO mass On/Off of rack FXs - that's a big one. That's really useful for a quick comparison across the board, to see what a

Mark has now added support for quick group delete fx as well as bypass effect so it will be in the final release.
 

Quote

On this topic, you should be able to click-select an Insert FX and delete it by pressing "DEL" - obviously, also for mass Delete (+Ctrl). Doing that doesn't work now, and I've had the experience - this I believe should be checked - of trying that, while in the Console View, and have it do nothing, only to find later on, that my pressing "DEL" DID do something, which was delete an audio clip that was selected in the... Track View, which is an major no-no. So, first of all, pressing anything should not do things you don't know about, in other views that are not selected, and secondly deleting FXs should be possible via pressing DEL, which would be an intuitive and common sense option.

I agree with this. Unfortunately there is no concept of effects selection so delete applies to the last selected object. However the fact that it deletes some random clip or object that the user has forgotten about and is potentially not visable has also bugged me since the beginning since it can lead to data loss. Obviously there is room for improvement in that area.

Quote

 

I don't get this, though - not the point of it, but how to interpret the behavior:

• Note: If the tooltip shows "Time Critical" when MMCSS is enabled in ASIO mode, it's possible that the driver is not using MMCSS, or has set up MMCSS incorrectly.

On my Audient ID4 mk2 - haven't tried the Evo - when Enable MMCSS is toggled off, I get "Time Critical", and when it's on, I get "Realtime" - in ASIO, obviously.

Does that mean that the audio driver CAN manage MMCSS on its own, or that it CAN'T?

 

I don’t blame you for the confusion. I’m just following the guidelines for the ASIO spec. (which I actually disagree with since I think its misguided information and the host should be setting thread priorities not drivers, because realtime audio threads need to behave identically as a group)
If its showing time critical by default when enable ASIO MMCSS is off in cbb, there is a possibility that the driver is NOT setting the priority to MMCSS. If its showing Realtime, when you enable MMCSS then it means we were successfully able to change the driver’s thread priorities to match our engine threads (which is a good thing).
Unfortunately in Windows its very hard to check existing MMCSS priories accurately so its possible that that the driver is actually setting MMCSS, but just not a high enough priority. The best way to check (assuming that you can identify the driver thread for your ASIO device) is to run Process Monitor and look at the priorities for the ASIO driver. For MMCSS it must be running with a dynamic priority of 24 or higher to be a pro audio thread.

See this thread for instructions.

Quote

Last, but not least, the automatic update within Cakewalk - which is really nice to have - doesn't work well with EA releases - there a mismatch there, which complicates updating - particularly since no links are provided for the official releases, for a reason I don't understand.

There is some confusion here. We have both soft and full public EA releases. The soft releases are only announced on the forum. This release was originally supposed to be much smaller so we chose to make it a soft release. However it grew legs and turned into 2022.11. We chose not to publicly push it until release in this case. When we release obviously everyone will get update notifications. (If it was a public EA you would have got an in-app notification)

Quote

By the way @Noel Borthwick, if you've gone through the trouble of signing all the .dlls - which is really useful, cause Windows Defender is an absolute bitch, and there's no way of fully getting rid of it, it even blocks itself, Windows components, full installations, EVERYTHING portable, so on - I don't think I've ever had a virus that was so damaging to the computer as this "antivirus", in the most proper sense - it never remembers any permissions, so on, many times it doesn't ask, doesn't even inform, anyway, complete and utter dementia - why not provide the link to the full installer, so that we can actually make full use of the signed dlls? What's the point in making that improvement, if people can't have access to it?

We don’t publicly expose the full installer because its large and incurs higher download costs. However if you need it ask support or PM one of us and we can send you a link when the full release is available.

@HOOK Yeah, that's pretty useless I can't tell either. Same issue with Focusrite.
If you install the latest 2022.11 early access build, I added a tooltip to the performance module that shows the thread priority. If you run that build let me know what it shows there. Thats the only way to know.

It should work. I just tested it with my Arturia Keylab and plugging in the device while CbB is running works fine. I get a device inserted prompt and when I choose yes, the MIDI device works fine, and I am able to record MIDI.

Are you getting the device Inserted prompt and choosing Yes? Sometimes if you unplug and replug multiple times in a session you won't get the prompt because we avoid displaying redundant prompts.
If not, you can also CTRL-click the "Reset Audio and MIDI" icon on the toolbar. This will force Cakewalk to reload the driver. If that doesn't work either the issue is with your device.

AFIK Z3ta doesn't output MIDI so I don't think it's possible to do.

That is not a crash and is normal. A crash causes program termination.
Timing for loading of views can be system dependent. There is no change I know of that could cause a behavior change here. 

@HOOK you can try it in whatever build you have thanks.
The 2022.11 EA build is quite solid however and we'll be releasing in a few days so there is no risk to try it. It also has a readout for the audio thread priority in the performance bar tooltip, which makes it easier to check what the driver is doing.

2 hours ago, apt said:

Thanks for the update!

But it's kind of weird that Quick Grouping only works on that new feature, but not on other "more basic" operations on effects, such as plugin on/off, rack on/off and deleting plugin.

Every quick groupable operation is custom code. You don’t get it for free. We’ve only made the most commonly used features quick groupable.

12 hours ago, scook said:

Deleting a plug-in from an audio FX rack is incomplete if the plug-in has automation driven by remote control.

Immediately after delete, the plug-in label is retained in FX rack but is inaccessible. The plug-in is actually deleted and is gone when the project is re-opened, however; the automation is orphaned.

Is the label persisting a new issue? Automation being orphaned is as intended but the plugin placeholder should be removed. I’ve never seen this…

When a plugin is deleted any related envelopes are orphaned and can be reused for something else or deleted. They are also kept in case you undo the delete, in which case they are reassigned to their parameters.

12 hours ago, scook said:

Replacing a plug-in that uses MIDI I/O does not preserve the MIDI setup.

IOW, plug-in properties of the new plug-in has "Enable MIDI Input" and "Enable MIDI Output" deselected regardless of the plug-in's capabilities and the settings of the plug-in being replaced. Moreover, any routings to and from the plug-in to instrument/MIDI tracks are also lost.

Replace is not intended to handle routing. You will have to set that up manually.

PM me the link. It may be days before it gets reported by support.