Jump to content
Morten Saether

[CLOSED] Cakewalk 2021.09 Early Access [Updated to build 137]

Recommended Posts

15 hours ago, Milton Sica said:

Thanks.

I explain the relevance that this little information would have for us to improve our projects in terms of efficiency.

We know that VST3 plugins have better performance and, therefore, in the inclusions we made we already prioritized making them with this type, as the inclusions menu brought us this.

It happens that we can open projects where the option to choose between VST3 and VST2 plugins was not possible/visible as in the current menus.
So, with the addition of this little information, as I suggested, it would help us to improve the performances of our current projects, either by being able to choose to include the VST3 version for the old plugin if it exists or by improving the way we work with it. within the application with the setting for JBridge when VST2.

I hope I was able to clarify the reason for my request.

Thanks.

Please update your knowledge on vst2 and vst3. Especially vst2 32-bit and 64-bit where the performance could play a roll.

More exactly, very few vst2 in use today are 32-bit and have a need for jbridge.

  • Thanks 1

Share this post


Link to post
Share on other sites
47 minutes ago, Kurre said:

Please update your knowledge on vst2 and vst3. Especially vst2 32-bit and 64-bit where the performance could play a roll.

More exactly, very few vst2 in use today are 32-bit and have a need for jbridge.

And VST3 performance is definitely not necessarily better than VST2.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

@Kevin Perry @Kurre

Thanks for the feedback.
In general I always prefer 64-bit VST3s.

With your opinion, I was wondering what was the reason for putting these details in this menu....

image.png.6469969378c6074a36dd0b069ae72663.png
And not be able to be in this help message as well???

image.png.82e4f497b48ecb6d41caba162e6d710a.png

 

 

Share this post


Link to post
Share on other sites
1 hour ago, Milton Sica said:

@Kevin Perry @Kurre

Thanks for the feedback.
In general I always prefer 64-bit VST3s.

With your opinion, I was wondering what was the reason for putting these details in this menu....


And not be able to be in this help message as well???

Noel wrote that there was no time for this release, I don't think he dismissed the idea completely. 🙂

Note that VST3s can still sometimes be buggier and have less features than their VST2 counterparts. This was the case for many years with u-He synths like Diva... (as an example, see this old u-HE FAQ that was true for many years, but note that it's no longer current news).

Edited by GreenLight
  • Thanks 1

Share this post


Link to post
Share on other sites
19 hours ago, Hung HIT said:

I updated to 2021.09 build 120. And right after that, continued to update build 123

I really like the new Export. Very fast and convenient rendering of individual tracks, but still through full FX. This is something I've been waiting for for a long time.
Many thanks team!

Currently I am having the following error:
I can't play the project without the SOLO button on for all the tracks. Same picture.

image.png.d07b945b220ae2aca2a8d2b4b62f2b92.png

This does not happen with all projects. But this is the 2nd project that I encountered. To play the project, you must enable SOLO.

In previous updates, August and earlier, I never had this error.

Hope someone can help me fix this error, or, the next update will fix this, for example.

 

 

Just confirming I've also experienced this, except strangely in mine, it's only guitar that will play unless soloed!

I was wanting to do a little bit more testing given that i'd recently raised another bug that turned out not to be specific to this release!
This isn't occuring on all projects, but on the project that I have encountered it, it seems to remain if I go back to pre-release build. I was going to work around it by opening up an older working version of the project and then copying across new changes.

I can send over a project with this issue later that may help to diagnose this if you need another example?

 

 

Share this post


Link to post
Share on other sites
37 minutes ago, Matthew Simon Fletcher said:

 

Just confirming I've also experienced this, except strangely in mine, it's only guitar that will play unless soloed!

I was wanting to do a little bit more testing given that i'd recently raised another bug that turned out not to be specific to this release!
This isn't occuring on all projects, but on the project that I have encountered it, it seems to remain if I go back to pre-release build. I was going to work around it by opening up an older working version of the project and then copying across new changes.

I can send over a project with this issue later that may help to diagnose this if you need another example?

 

 

@Matthew Simon Fletcher please send a project that can repro this ASAP. I’d like to investigate it before we release

Share this post


Link to post
Share on other sites

Couple of observations regarding the export process.

1) When creating and renaming tasks,  and then 'updating tasks with current settings' this fails to refresh the filename until the 'recall task settings' option is used.  

2) It would be very nice to have a save tasks option. I'm using tasks in a batch export process to improve the mastering workflow e.g. exporting streaming/CD/mp3 files which are common to every mastering project. I can of course create a mastering template to do the same but the utility value of task presets would be a nice option. 

 

Share this post


Link to post
Share on other sites
1 hour ago, Noel Borthwick said:

@Matthew Simon Fletcher please send a project that can repro this ASAP. I’d like to investigate it before we release

Has I stated a little earlier in this thread, I believe I have the same problem. I have a project that can reproduce it and I can send it to you.

  • Like 1

Share this post


Link to post
Share on other sites
4 minutes ago, Matthew Simon Fletcher said:

Not that I could see unfortunately - also that would mean the global solo toggle button isn't working correctly.

Maybe a level deeper then. An archived frozen track with solo enabled?

 

...just thinking.

Share this post


Link to post
Share on other sites
10 minutes ago, Keni said:

Maybe a level deeper then. An archived frozen track with solo enabled?

 

...just thinking.

I appreciate your thoughts :)
I don't use the archiving functionality and couldn't see anything else obvious.
I toggled the global solo button several times, so my expectation would be that that would clear anything anyway.


To be fair I do doubt myself often, so hence not raising this immediately, but when other people mentioned a similar issue, it seemed beyond coincidence and hence was more likely to be triggered by something in the newer build.

  • Like 1

Share this post


Link to post
Share on other sites
24 minutes ago, Matthew Simon Fletcher said:

I appreciate your thoughts :)
I don't use the archiving functionality and couldn't see anything else obvious.
I toggled the global solo button several times, so my expectation would be that that would clear anything anyway.


To be fair I do doubt myself often, so hence not raising this immediately, but when other people mentioned a similar issue, it seemed beyond coincidence and hence was more likely to be triggered by something in the newer build.

Sorry. Only good intentions. Trying to help.

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, Jacques Boileau said:

Has I stated a little earlier in this thread, I believe I have the same problem. I have a project that can reproduce it and I can send it to you.

@Jacques Boileau - please send this project to @Noel Borthwick .  We're currently looking at this issue right now.

Share this post


Link to post
Share on other sites
5 hours ago, Matthew Simon Fletcher said:

I was wanting to do a little bit more testing given that i'd recently raised another bug that turned out not to be specific to this release!

My own experience tells me that the solo issues alone aren't specific to this release either. On my production PC I still have Cakewalk v2021.01 and there are already some un-solo issues there, have to click more than once to un-solo tracks whereas it used to work just fine with earlier versions. Can't tell with exactly what version the issues started.

Edited by chris.r

Share this post


Link to post
Share on other sites

I have also experienced the soloing problem in the early release [123] .  It happened on only on two occasions. Once, I restarted Cakewalk and the problem disappeared.  On the other occasion, I just started soloing and un-soloing random tracks (and the master solo too) then after a while normal operation resumed.

Share this post


Link to post
Share on other sites
1 hour ago, Keni said:

Sorry. Only good intentions. Trying to help.

I'm very grateful! :) apologies if I didn't sound as such.

 

Chris.r - I personally haven't had this problem before this pre-release, but absolutely not to say that it isn't an older issue.

Sailor55- I tried a number of things such as soling/unsoloing and reloading the project but didn't find a last fix, so hence was going to go back to an earleir project version.

Edited by Matthew Simon Fletcher
update

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...