Jump to content

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


Recommended Posts

Thanks for the update. 

I'm gona have to disagree on the sidechain with AUX tracks. This adds more work to it, by adding an extra track.

For this to work as shown in my video, Aux tracks needs to be added to SOURCE CATEGORY instead of with the tracks. I believe it is not what the member requested? 

With  buses you just get the signal source. 

Link to comment
Share on other sites

23 minutes ago, Milton Sica said:

@Noel Borthwick

If you can enlighten me.
I was having popping issues when exporting using any amount of buffers. I only managed to generate well with the value 0.
I saw that there was the inclusion of a parameter 140 (1024).
Was there any evolution for the other parameters or should I test only with this new parameter?

image.png

You should be able to test with any export buffer size now and not get timing problems or lost MIDI. The numbers there are just dividing the range of values to give you some convenient multiples to pick. You should be able to manually enter any in range value for the buffer size if you wish.

Note that VST2 plugins and some VST3 plugins do not support intra-buffer automation so if you have plugin envelopes you may notice aliasing at higher buffer sizes.   

  • Thanks 1
Link to comment
Share on other sites

46 minutes ago, Will_Kaydo said:

Thanks for the update. 

I'm gona have to disagree on the sidechain with AUX tracks. This adds more work to it, by adding an extra track.

For this to work as shown in my video, Aux tracks needs to be added to SOURCE CATEGORY instead of with the tracks. I believe it is not what the member requested? 

With  buses you just get the signal source. 

As mentioned before aux tracks and buses are not exactly the same thing. A source category for them is not the solution.
There are some further steps to potentially improve this behind the scenes without adding unnecessary and confusing user options.

What was fixed was a fundamental issue with source category tracks that was preventing rendering of outputs to aux tracks and sidechains. This was the root problem.

Link to comment
Share on other sites

1 hour ago, Noel Borthwick said:

You should be able to test with any export buffer size now and not get timing problems or lost MIDI. The numbers there are just dividing the range of values to give you some convenient multiples to pick. You should be able to manually enter any in range value for the buffer size if you wish.

Note that VST2 plugins and some VST3 plugins do not support intra-buffer automation so if you have plugin envelopes you may notice aliasing at higher buffer sizes.   

I am sorry if this has already been explained: why is a bounce buffer size user selectable, I mean, what is the use case or benefit of changing that?

Thanks!

Link to comment
Share on other sites

1 hour ago, Noel Borthwick said:

As mentioned before aux tracks and buses are not exactly the same thing. A source category for them is not the solution.
There are some further steps to potentially improve this behind the scenes without adding unnecessary and confusing user options.

What was fixed was a fundamental issue with source category tracks that was preventing rendering of outputs to aux tracks and sidechains. This was the root problem.

With the highest respect to you. Yes, I'm aware its not the same and I think that is the reason why the request for this to be added to SOURCE CATEGORY is so high. 

Due to the obvious routing limitations with buses, which AUX tracks dont have. In EDM you sometimes end up with 8 AUX tracks within the project just for a single source. This then becomes a problem when the client request these trackouts of these effects, cause sometimes you have to sidechain a flanger on top of a phaser from an FX VSTi that does not have an sidechain input. Personally, for me its not a problem. I know my way around the routing system in Cakewalk to get exactly what i want. The only thing is, its more work - that's it. 

 

Edited by Will_Kaydo
Link to comment
Share on other sites

10 minutes ago, GreenLight said:

I am sorry if this has already been explained: why is a bounce buffer size user selectable, I mean, what is the use case or benefit of changing that?

Thanks!

A higher buffer size will be faster at exporting, but at the expense of using more memory.

Setting it to zero will default it to the playback buffer size.

  • Like 1
Link to comment
Share on other sites

Great upgrade! Thanks a lot -

I found two things that seems to be not working :

1. After the update, the title menus of the insert audio fx/plugin, got darkened and unreadable) - See pic 1.

2. When trying to export from track sources, the selection of the Mix and Render option regarding BUS FX is not working. The rendering bypasses the inserted plugin. See pic 2

 

Imagen1.png

Imagen2.png

Link to comment
Share on other sites

3 minutes ago, msmcleod said:

A higher buffer size will be faster at exporting, but at the expense of using more memory.

Setting it to zero will default it to the playback buffer size.

Thanks! Ooh, nice to be able to speed up exports. :)

Two quick thoughts:

  1. Would it be a good idea to have a mouseover popup explaining just that? It's not self-evident how an export buffer affects operations, even to a long-timer like me. (But maybe I'm just a slow learner... *laugh* don't answer that. ? )
     
  2. Any ballpark figures of how much faster the new export could be compared to the old for a "reference" project?

 

 

  • Like 1
Link to comment
Share on other sites

This is pretty tangential to the actual functionality that's been built this time around, I know. But just throwing this in:

What would improve my working life, vastly, on a near-daily basis, would be the ability to queue up multiple projects for export. So a list of projects would load, export with current settings, automatically close, then automatically load the next, and so on.

I can see that's outside the scope of current developments, but it seemed like a natural place to float the idea.

 

  • Like 1
Link to comment
Share on other sites

44 minutes ago, Noel Borthwick said:

First world problems? The toast is displayed so that people who walk away can see it. Close it if you are done with it. It's one click.

It’s one click repeated 20-40 times a day for me (sometimes).

That extra click and being forced to mouse over to it gets old real fast.

 

So all I ask is for an option so that it times out.

 

Edited by Keni
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...