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

[Noel Borthwick]

16 minutes ago, Will_Kaydo said:

Great stuff Noel. Is it really necessary for tracks though? I mean sidechain with tracks serves a different purpose. It's double the work for you and an unnecessary feature. Only do this for Aux tracks. They're more flexible than Buses. ☺

Sidechains and auxes are just different sides of the same problem. Internally they are buses. In Cakewalk when you send to a sidechain its sending to a hidden sidechain bus, Thats how multiple tracks can send to the same sidechain.

[Noel Borthwick]

1 hour ago, AlexHomeStudio said:

The program crashes after applying the Bounce To Clip command

 

@AlexHomeStudio We’ll need a bit more information to solve this. Please list the specific steps you are doing and if you can reproduce this in any project.  Also please attach the dump file for the crash to help us investigate the cause.
Not seeing any problems here bouncing to clips.

[marcL]

Export dialog/bounce to track(s):

1. It would be nice if the dialog height would be configurable as it is a bit too large on laptops with 768 height only (1 line)!
2. In the "bounce to track(s)" dialog the channel format "Follow Source" is missing and this can conflict using a preset with it (here it has chosen stereo for a mono track instead)

AudioSnap/Quantization:

1. Changing the threshold and the resolution (e.g. to 1/16) the detection results are noticeable improved! ?
2. One thing I am more concerned about is that the rendering with the Radius-algorithms still show major transient displacements (note/hit starts moved more than 10ms). Also, in the past it happened sometimes that a transient part was repeated within 1ms or was removed! Using the Elastique-Pro-algorithm I get absolutely acceptable displacements for the note/hit start and end (within 1ms). But zooming in to about -18dB I still determine major degradation within the notes that is also audible. Partly it is even difficult to find similarites of the wave form.

[Will.]

14 minutes ago, Noel Borthwick said:

Sidechains and auxes are just different sides of the same problem. Internally they are buses. In Cakewalk when you send to a sidechain its sending to a hidden sidechain bus, Thats how multiple tracks can send to the same sidechain.

Exactly, but its not what i meant. ?

[User 905133]

Thanks for the borders when categories are expanded.  Much easier to see the choices.

 

[msmcleod]

31 minutes ago, marled said:

Export dialog/bounce to track(s):

1. It would be nice if the dialog height would be configurable as it is a bit too large on laptops with 768 height only (1 line)!

The minimum supported resolution for CbB is 1280 x 800.   But in saying that it does fit on a screen 768 high.

The last size & position of the dialog is stored in the registry, so it remembers it globally for the next time you use it.

31 minutes ago, marled said:

1. In the "bounce to track(s)" dialog the channel format "Follow Source" is missing and this can conflict using a preset with it (here it has chosen stereo for a mono track instead)

It's not missing - "Follow Source" was never available in the bounce to track(s) dialog.

[Noel Borthwick]

1 hour ago, marled said:

Export dialog/bounce to track(s):

1. It would be nice if the dialog height would be configurable as it is a bit too large on laptops with 768 height only (1 line)!
2. In the "bounce to track(s)" dialog the channel format "Follow Source" is missing and this can conflict using a preset with it (here it has chosen stereo for a mono track instead)

AudioSnap/Quantization:

1. Changing the threshold and the resolution (e.g. to 1/16) the detection results are noticeable improved! ?
2. One thing I am more concerned about is that the rendering with the Radius-algorithms still show major transient displacements (note/hit starts moved more than 10ms). Also, in the past it happened sometimes that a transient part was repeated within 1ms or was removed! Using the Elastique-Pro-algorithm I get absolutely acceptable displacements for the note/hit start and end (within 1ms). But zooming in to about -18dB I still determine major degradation within the notes that is also audible. Partly it is even difficult to find similarites of the wave form.

Thanks for the feedback. We don’t really have control with how Radius handles its stretching since it was developed by iZotope and its no longer maintained by them. IIRC radius internally uses its own transients rather than ours so I don’t expect a major change there even though our detection is improved. Do you see better behavior with the elastique stretching? Elastique is more advanced than Radius and is still maintained by zPlane.

[Dave Maffris]

14 hours ago, Noel Borthwick said:

Hi folks there is a new build 99  posted today that addresses several issues noted. See the main post.

Do we have to use the download installer to get it? THere's no toast notification and check for updates says I have the latest version. Assuming the answer is yes?

 

[scook]

11 minutes ago, Dave Maffris said:

Do we have to use the download installer to get it? THere's no toast notification and check for updates says I have the latest version. Assuming the answer is yes?

 

Early Access versions are not distributed like production releases. A link to the Early Access installer is in the original post

 

[Will.]

16 minutes ago, Milton Sica said:

I need help/clarification.

1 - I use a standard project to master.
2 - In this project I inserted two tasks. One to generate WAV and one to generate MP3.
3 - In this project I import the mixed WAV.
4 - I use the ENTIRE PROJECT parameter in the tasks, as it is in this same project that I perform the mastering. So the size of each track/tempo changes with each mastering I'm going to do.
5 - However, the execution of tasks at each import of a new track to master is not executed.
6 - The only solution I have found so far is to RETRIEVE THE PARAMETERS OF EACH TASK, confirm that I want to ENTIRE PROJECT and execute.

Any tips for the tasks to be executed considering the new sizes/times of the inserted track?

Maybe ask a moderator to move this to the Q&A section and we'll be happy to help you answer your Question. 

[Kurre]

@Milton Sica

I just wanted to point out that you don't have the checkboxes in the task queue activated. In any of your images.

msmcleod has them checked. Probably have something  to do with your different experiences.

[JoseC]

About Bounce to Tracks dialog: would it be possible to make the chosen track to persist until changed? I often sample soft synth loops when browsing presets, make them groove clips and drag them to the browser. I use to set a track in the project for that purpose, and it is unconvenient that by default the Bounce to Tracks dialog suggests a new track.

[Noel Borthwick]

3 hours ago, Milton Sica said:

I need help/clarification.

1 - I use a standard project to master.
2 - In this project I inserted two tasks. One to generate WAV and one to generate MP3.
3 - In this project I import the mixed WAV.
4 - I use the ENTIRE PROJECT parameter in the tasks, as it is in this same project that I perform the mastering. So the size of each track/tempo changes with each mastering I'm going to do.
5 - However, the execution of tasks at each import of a new track to master is not executed.
6 - The only solution I have found so far is to RETRIEVE THE PARAMETERS OF EACH TASK, confirm that I want to ENTIRE PROJECT and execute.

Any tips for the tasks to be executed considering the new sizes/times of the inserted track?

Entire project refers to the selection time range  in the project. However if you add new tracks to the project later they won't be included in that task.

IOW tasks are very specific to the project state at the time the tasks were created. If you change the project later you have to make a new task or update it. Tasks are not intended to be valid for the lifetime of a project if you make changes to it. It's cheap to make new tasks so just delete the old ones and create new tasks.

[Noel Borthwick]

57 minutes ago, JoseC said:

About Bounce to Tracks dialog: would it be possible to make the chosen track to persist until changed? I often sample soft synth loops when browsing presets, make them groove clips and drag them to the browser. I use to set a track in the project for that purpose, and it is unconvenient that by default the Bounce to Tracks dialog suggests a new track.

Not easily because there could also be more than one track as a source.

[JoseC]

2 minutes ago, Noel Borthwick said:

Not easily because there could also be more than one track as a source.

I meant the destination track.

[Noel Borthwick]

Just now, JoseC said:

I meant the destination track.

The dest track is based on the current track. If your set that before opening the dialog then it should default to it.

[JoseC]

24 minutes ago, Noel Borthwick said:

The dest track is based on the current track. If your set that before opening the dialog then it should default to it.

I cannot seem to be able to get that behavior here. If I:

1. Select a midi clip in an Instrument Track.

2. Open the Bounce to Track Dialog

In the Destination Track field I always get <#> New Track, no matter what track is current. I would like to be able to select a destination track within the dialog and make it persist every time I open it until I wish to change the destination track. 

[Noel Borthwick]

7 minutes ago, Milton Sica said:

Many thanks for the reply.
So, if I understand, choosing ENTIRE PROJECT when saving a task records the constant selection times of the project, it does not re-evaluate it when executing the task.

Example:
I have a 4 minute project and I generate a task with ENTIRE PROJECT.
If this project extends to 6 minutes or reduces it to 3 minutes if the task is executed, it will be under the parameterization of time when it was generated, that is: 4 minutes.

And so ?

Actully if you selected entire project for the task it should adapt to the duration changing. 

[marcL]

6 hours ago, marled said:

Export dialog/bounce to track(s):

1. It would be nice if the dialog height would be configurable as it is a bit too large on laptops with 768 height only (1 line)!
2. In the "bounce to track(s)" dialog the channel format "Follow Source" is missing and this can conflict using a preset with it (here it has chosen stereo for a mono track instead)

 

5 hours ago, msmcleod said:

The minimum supported resolution for CbB is 1280 x 800.   But in saying that it does fit on a screen 768 high.

The last size & position of the dialog is stored in the registry, so it remembers it globally for the next time you use it.

It's not missing - "Follow Source" was never available in the bounce to track(s) dialog.

1. Export/Bounce dialog height: Perfect, in this case my wish is already realized! I have tested the dialog(s) size change and it runs with success!
2. Follow Source: You are absolutely right, this configuration value is also not present in Sonar Platinum! But IMO it would be great if it was! Why not?

[marcL]

5 hours ago, Noel Borthwick said:

Thanks for the feedback. We don’t really have control with how Radius handles its stretching since it was developed by iZotope and its no longer maintained by them. IIRC radius internally uses its own transients rather than ours so I don’t expect a major change there even though our detection is improved. Do you see better behavior with the elastique stretching? Elastique is more advanced than Radius and is still maintained by zPlane.

Thanks for the information! Though it is a pity that Radius is no longer maintained, because it sounds so much better than Elastique Pro!

Yes, rendering with Elastique Pro gives definitely better results in respect of shifting! The shift of note starts and ends is within 1ms, what is absolutely okay. But regrettably the Elastique algorithm is not so accurately reflecting the original wave form as the Radius ones. But I guess today most other DAWs also use Elastique Pro primarily? (I know that Reaper and Samplitude do!)