Herbert Zio

5 minutes ago, Noel Borthwick said:

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. 

I expressed myself badly, it would be another lag that started to occur after I update.

@Noel Borthwick Is the group split behavior I reported in the private message normal for Cakewalk, or is it a glitch?

2 hours ago, Colin Nicholls said:

I'm not sure what I'm looking at... apart from the beautiful theme, of course

When loading a New Project, there is a delay in loading the "Inspector", from the "View, Options, Track..". and "Browser", in the previous version's, loading was performed together with Track View.

On 11/3/2022 at 4:30 PM, Noel Borthwick said:

I'm not sure what you are referring to as a crash. There is no crash in your video. It just shows the views loading normally.

If you notice in the second video, when loading a New Project, there is a delay in loading the "Inspector", from the "View, Options, Track..". and "Browser", in the previous version's video, loading was performed together with Track View.

I found the option to replace the plugin inserted in the track cool, it would be interesting if there was an option to delete all plugins inserted in the track at once, instead of deleting one at a time.

Another bug that is happening is when saving the Workspace with the Control Bar collapsed, when closing the DAW and opening it again, the Control Bar Collapsed is all unconfigured.

Control Bar Collapsed = Before closing the DAW

Control Bar Collapsed = When reopening the DAW

As I mentioned in another thread, after updating to version 2022.09 (Build 039), the DAW started to have these crashes when opening a new project.
I uninstalled the DAW and installed version 2022.06 (Build 028), and it does not have this crash, but when I to update to version 2022.09 (Build 039)  appears.
To better illustrate what I'm talking about, I recorded the screen of both versions.

Version: 2022.06 (Build 028)
 

Version: 2022.09 (Build 039)

I posted in another thread, but decided to bring it to this one. After the 28.09.0.027 update started to present this crash when loading a new project, I installed the 28.09.0.039 update, and this crash continues, would it be a bug?

@Noel Borthwick, After the 28.09.0.027 update started to present this crash when loading a new project, I installed the 28.09.0.039 update, and this crash continues, would it be a bug?

Whenever I post suggestions, or report any "bug", some always appear to throw sand in the fire, I don't know if they really want the DAW to evolve or if it stays still full of "Bugs", I think the second option is the most appropriate.

It's the same when we talk about improvements or new features to improve Workflow, conformists appear talking about leaving things as they are.

@murat k. As for improving video support, I agree with you and it really has nothing to do with the system that it goes black when we pause, but rather it's a problem with the DAW.

Below are the videos with the white video you made available, running on Cakewalk and Cubase 12 Pro.

Cakewalk.
 

Cubase 12 Pro.
 

1 hour ago, Mark MoreThan-Shaw said:

All hail the mightly Console Inspector

When I referred to the "Arranger Track" and "Tempo Track" I didn't mean the "Arranger Inspector" or "Tempo Inspector", but the visualizations in the "Track View".

All hail the mighty Track View. 🥴🤪

If you didn't see the image with an example I made, check it out again above! 👍

You must enable "When clips are select, select track envelopes too" in "Selection" as in the example I did on the video below.

The "Track Manager" is excellent, the only problem is that it is not so practical, since with each change we have to press the "H" key all the time to be able to visualize it. It would be much more practical if we had the option to leave its visualization permanently and that as soon as we uncheck the box referring to the track or folder, we wouldn't need to press "Ok" for the action to be carried out, but that it would be something simultaneous.
The way @murat k. presented would be interesting, if you didn't want to compromise the "Inspector", it could be something connected to the "Console" itself, which you could enable or disable the panel view in the "Options" above, already in the "Track View" in the "Inspector" in the tab "Track Properties" would be nice.

You already have the option to open the "Track Manager" in the "Strips" menu, just put it to open it in the "Console", see the example I made in the image below, the "Track Manager" on the left inside the "Console"....

It would be like the "Arranger Track" view, or "Tempo Track", you have the option to enable or disable the view.

12 hours ago, Mark MoreThan-Shaw said:

It looks exactly the same as the Track Manager but in the Inspector instead of a pop up menu.

I mean - what's quicker, pressing H or mousing to the top of the Inspector to choose a tab ? I don't think there is much in it.

Personally I think it would use up valauable space on the Inspector tabs at the top, it's already full with ProChannel  - Track Properties - Clip Properties - Tempo & Arranger. I wouldn't want it to replace any of them, I don't think I've ever used it anyway even on session swith 100+ tracks.

If you want a true solution the request should be about giving the user configurable Inspector tabs  so " we " can choose what we use the most..and have a host of options including a track manager for those that want it. Personally I would much rather have an improved Midi inspector with proper humanise features and not rely on CAL.

I'm sure everyone has their one set of preffered tools.  

I hear you, but my suggestion would not be to link the track manager to the "Inspector", but something that is linked to the "Console View", and that has the option to select the display of this panel in "Options", where once active I don't need to keep pressing any key every time or hovering to display it. In the video I posted above as an example, I didn't need to hover or press any key for the track management panel to appear, it was just there!

As I told sjoens, something like the "Inspector" in the "Console View" and not exactly in the "Inspector".

You can find this feature in Cubase, Nuendo, Harrison Mixbus, Ardour, in other words, it's not a whim but an ease!

9 hours ago, sjoens said:

As long as the list pane itself can be collapsed or disappear completely.

Yes, something like the "Inspector" but that you have this option to activate or not this strips pane in options, in the same way when we activate activate the visualization of some elements, such as outputs, icons, narrow and widen strips, etc.

When the nesting folders feature was released, I had suggested that we have this option in the "Console View", I was told it had the "Track Manager", where I could hide the tracks I wasn't working on. I know that the "Track Manager" is an interesting feature, however, my suggestion was to have something more accessible so that I didn't have to always use shortcuts and select "Ok" for the action to be executed.

I was testing another DAW, and I saw in it the idea that I had suggested, I thought it would be interesting to share it here so that you can see and maybe implement the idea in the Cakewalk, it would make the workflow a lot easier.

See that on the left side of Ardor's "Console View", you have the option to "Show/Hide Strips" and at the bottom of "Show/Hide Group", without having to access the option through shortcuts, such as the "Track Manager ".

It would be interesting if this idea were implemented in Cakewalk!

18 hours ago, Kevin Perry said:

It's even more nuanced than that.  Steinberg tried to change the VST3 license agreement, which would have allowed them (theoretically) to stop those with existing VST2 licenses from developing new VST2 plug-ins (and hosts?) at an arbitrary time of their choosing.  That was reversed out of the license agreement, but it would have potentially meant no new VST2 plug-ins and only updates to existing ones, so if you had a VST2 only host, your supply of plug-ins would dry up and - reading between the lines - a host developer would have to drop VST2 support on a new version of the host (although when that would apply...dunno).

To give that control over your technology to a competitor...whoah!

Exactly!

If, depending on the contract with the developer, there was any clause that limited the license period, revoking it upon reaching the expiration date, not even updates would be possible, with time certain Plug-Ins would stop working! There are some Plug-Ins that no longer work due to lack of updates, as there are some that are no longer recognizable on some systems.

Of course, that's drawing a hypothetical scenario!

On 2/3/2022 at 9:41 AM, msmcleod said:

@Herbert Miron - The discontinuation of VST2 plugins only really affects Plugin manufacturers who didn't sign a developer agreement prior to 2018.  Those who have a developer agreement signed before 2018 can continue to release VST2 plugins if they wish.

What Steinberg's statement is saying is that new developers cannot release VST2 plugins - only VST3 ones.  

Also, as far as I can tell, this affects the releasing of plugins, not plugin hosts (such as Cakewalk and other DAWs).  Cakewalk will continue to support VST2 plugins and has no plans to discontinue support for them.

Thank you very much for clearing this doubt regarding Cakewalk when hosting VST2 Plug-Ins!

I can think about several things at the same time, and that doesn't stop me from making music, unless I had some problem, like attention deficit, maybe I wouldn't be able to perform such an action.
Anyway, more information should be provided about how much the fact that Steinberg discontinued VST2 can imply, and it won't take 20 years for problems to occur in the usability of Plug-Ins, even more when it comes to Plug-Ins that have already been discontinued, or even from developers who no longer exist.
And no matter which DAW you are using, the developers of the other DAWs will not stand by and try to make the DAW run that old Plug-In of yours, they will all follow the market standard dictated by Steinberg.
It's one thing when Steinberg released VST3, then threads everywhere on the internet were speculating about the end of VST2, another thing is Steinberg making it obsolete, which happened 14 days ago.
Anyway, you don't need to waste time here on the topic, if it gets in the way of making your songs. I just raised a question regarding the Plug-Ins belonging to the Sonar Platinum package. 😉

Maybe Steinberg is already working on some bridge to run VST2 as VST3, after all, they can make a flash money selling this solution, after they created the problem themselves. 😂

Let's wait and see what will happen!

3 minutes ago, Keni said:

 

Seems crazy to me. I could easily understand stopping their own development of such, but why affect the world's use of things already acquired? I mean, we still have dx support even though nothing new is made.

Shouldn't this be the same? No new official vst2 products, but old should continue to function. I feel like I’m being abused!

Business, generate profits, even more so when it comes to Steinberg, who charge everything they can charge, forcing users to buy new Plug-Ins according to new established standards where the domain will always be theirs.

2 minutes ago, Keni said:

Well, at first I figured they were dropping vst2 support in their own products, but didn’t think this would force the end of vst2 continuing to function elsewhere would occur.

 

This talk is leading me to think this is not the case? All vst2 devices everywhere are about to stop working? That really hurts for use of legacy products. It’s gonna crush my current work model.

 

Sad. I hope I’m wrong.

 

 

I was reading an article, and their idea is "evolution", unfortunately there are many good VSTs that developers don't even exist anymore, and if the trend is for all DAW developers to adapt to the new market standard, VST2 is probably with its days numbered. =/

10 minutes ago, scook said:

When Cakewalk was shutdown, Don't Crack offered a discount to Platinum owners for the unlocked version of the Blue Tubes bundle.

IIRC, recent public sales have been even more aggressively prices.

Don't Crash puts them on sale regularly.

Ah yes, but the solution is to wait to see if there will be any update by Nomad for VST3, from what I could see, VST2 is still the commercialized Plug-Ins of the Blue Tube line at least. So, for me I don't see much advantage in purchasing them now, since I can continue using the package that came with my Sonar Platinum.
Anyway, thank you for your attention!

I see, I thought there was still some contract between Nomad and Cakewalk regarding Sonar Platinum users, as it was part of the Platinum package.
So I thought that at least for users who had previously purchased Sonar Platinum, they could have the plugins that came with the DAW updated to VST3.

Thanks!

At first, the change will occur in Steinberg's own software, but we know that the tendency is that all other companies will end up adjusting to the new standard.
Since 2018 Steinberg no longer grants a license for VST2 developers, only for VST3, my question on the forum is if this happens, will there be any updates of some Plug-Ins included in Sonar Platinum from VST2 to VST3, or will they simply be obsolete in Cakewalk ?

I recently saw that Steinberg announced the end of support for VST Plug-Ins within 24 months.

As for the Plug-Ins that belong to the Sonar Platinum package, for example, will there be any support for them, such as the Nomad Factory - Blue Tubes Plug-Ins and others, will there be any updates for VT3?