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

[Heinz Hupfer]

HI:)

Export Improvements are a great forward! I always faught with the settings before and had some strange results some times.

???

 

Bassman.

 

[marcL]

This is really great, thanks!

The AudioSnap improvements sound very interesting, as well as the new export module! I almost gave up AudioSnap some time ago, but it seems my calls have not been unheard!

As soon as possible I'll give the new version (early access) a try! It sounds very amazing! Great improvements! ? ?

Edited August 26, 2021 by marled

[msmcleod]

1 hour ago, Milton Sica said:

Export procedures are a major evolution and we know we will go much further now.

A question that came to me from this format.
Is the final file name and location saved according to the task?

If I enter different names and locations in the stored Tasks it will generate like this or will name and location always be those contained in the task parameterization box?

Yes.  But you'll want to have unique filenames so each task doesn't overwrite the results of the previous.

You can use the {taskname} tag in the filename if necessary.

1 hour ago, Milton Sica said:

When exporting clips it is not possible to configure or there is no tag to export the clip with its name

Tags 

this name without or with the index

    

If you set the filename to something like:

{projectname}-{tracknumber}-{trackname}-{laneindex}-{clipindex}-{clipname}

You'll get the clip name at the end.

If you just want the clip name, set the filename to:

{clipname}

[msmcleod]

13 minutes ago, Milton Sica said:

Thank you, but your guidance does not work as I want to parameterize.

Even selecting clip export the clip name (Marhino) is not generated.

 

 

 

I'd need to see the whole of the export dialog to try to figure out why this is happening.

[Mark Morgon-Shaw]

This is brilliant - I look forward to using ☺️

Do you think it will be possible to add  Folders as a source in the " What To Export " section ? 

[msmcleod]

1 minute ago, Milton Sica said:

I believe there may be a problem with the translation into Portuguese.

I don't see the parameterization in my language.

At the end, the name is generated in this format.

Marhino(69).wav

I want to generate the final filename without the index (69)

Only like this:

marhino.wav

 

The index is in fact part of the name.



You'll need to rename the clip to remove the index.

If you've got lots of clips on the track, and want them all with the same name, do this:

[Keni]

5 hours ago, msmcleod said:

A task basically =  Bounce Settings + Project Selection + Checked Sources

• The Bounce Settings can be stored as a preset in the top preset dropdown.   The filename is now also stored with the preset, so if you use the new filename tags it can pick up what it needs from the project properties, or alternatively make it blank before saving the preset.
• Project Selection + Checked Sources are obviously project specific.

In most cases, the bounce settings presets should suffice.

There's no reason why you couldn't save your tasks as part of a project template though.  You might need to recall/update them if you change or add new tracks though.
 

Thanks ms...

It's gonna take me a few minutes to wrap my head around this.

Yes, handy as is for many things. Already a saver for my mastering template. All that remains in that path are the mp3 dialog settings so in need of presets! ?

 

...but for building new projects, the ability to use presets including tasks seems an obviously handy tool!

 

...Please don’t take me wrong. I love the new features and see a few extra elements to make it a more "complete " job?

 

 Thanks again for your time explaining. Age is making me more confused than drugs ever did!

[Noel Borthwick]

48 minutes ago, Keni said:

Thanks ms...

It's gonna take me a few minutes to wrap my head around this.

Yes, handy as is for many things. Already a saver for my mastering template. All that remains in that path are the mp3 dialog settings so in need of presets! ?

 

...but for building new projects, the ability to use presets including tasks seems an obviously handy tool!

 

...Please don’t take me wrong. I love the new features and see a few extra elements to make it a more "complete " job?

 

 Thanks again for your time explaining. Age is making me more confused than drugs ever did!

Also to add to what Mark said, tasks are by definition per project so it doesn't make sense to share them across project since they contain information that is keyed to a specific project. MP3 presets would be a different feature that we may consider in the future.

[Promidi]

Excellent update.

However, I have noticed something with the export results using different export buffer settings that I am not sure if it’s expected.

If I have a VSTi (in my case, AAS String Studio VS-3) that has sequential pitch bend events applied to achieve a glide from one note to another, the higher I set the export buffer setting to, the more stepping in the pitch bends I can hear.   I am using pitch bends i9n the PRV controller lane. I have net tested it using automation as I use CCs in the PRV for my workflow.

To achieve an exported file with a smooth pitch bend generated glide, I need to set the buffer to 1. 

To make sure it was not a String Studio VS-3 issue, I tried the same thing in a Rapture Pro patch that had just one sawtooth  -  same ting happened there as well.  I get stepped pitch bend.

Is this expected behaviour if I set the export value is set to higher values?

[msmcleod]

11 minutes ago, Milton Sica said:

EXPORT

1) The information of the folder chosen for export is not kept with the saving of the project. Every opening it returns to the default value.

2) Tasks after being performed are unchecked. If you want to run the tasks again you need to close the window and reopen it or check each box. It would be nice to have a box that allows you to check/uncheck all tasks and that, after their execution, they are not unchecked.

 

 

 

Both of these are intentional.

[msmcleod]

1 minute ago, Milton Sica said:

Exporting to MP3 only works the first time you include the Task. The next few times it is run, it is not run.

The options dialog is only shown when you create the task. It isn't shown when running it.

[Noel Borthwick]

1 hour ago, chimkin2 said:

This is brilliant - I look forward to using ☺️

Do you think it will be possible to add  Folders as a source in the " What To Export " section ? 

Not sure what you mean by "Folders". What to export refers to sources within the current project such as tracks, buses, arrangements.

[Chris Boshuizen]

omg I have been waiting for this for so long! Congrats to the CW team, this looks like a monster releaese! Thank you!

[Mark Morgon-Shaw]

2 minutes ago, Noel Borthwick said:

Not sure what you mean by "Folders". What to export refers to sources within the current project such as tracks, buses, arrangements.

Hi Noel ☺️

Yes- For example in this project if I needed to export all the Guitars or all the Vocals which are organised within the project into Folders , hope that makes sense ?  It would be much quicker than selecting individually.

[Noel Borthwick]

2 hours ago, Promidi said:

Excellent update.

However, I have noticed something with the export results using different export buffer settings that I am not sure if it’s expected.

If I have a VSTi (in my case, AAS String Studio VS-3) that has sequential pitch bend events applied to achieve a glide from one note to another, the higher I set the export buffer setting to, the more stepping in the pitch bends I can hear.   I am using pitch bends i9n the PRV controller lane. I have net tested it using automation as I use CCs in the PRV for my workflow.

To achieve an exported file with a smooth pitch bend generated glide, I need to set the buffer to 1. 

To make sure it was not a String Studio VS-3 issue, I tried the same thing in a Rapture Pro patch that had just one sawtooth  -  same ting happened there as well.  I get stepped pitch bend.

Is this expected behaviour if I set the export value is set to higher values?

This is a symptom of running plugins that don't support sample accurate automation. i.e only VST3 plugins can deal with sub buffer automation.
If you have pitch bends or other plugin automation, when you  run at a high buffer size, unless the plugins support sample accurate automation you will hear it applied at the buffer boundaries, hence you get quantization. There is no solution to that other than running at a lower buffer size.

One thing I can potentially consider in the future is artificially running plugins are a lower buffer size when they have automation to work around this limitation.

BTW @Promidi this problem should not happen for VST3 plugins because we are already sub decimating buffers to 5 msec boundaries. So even if you had a buffer size of 350, VST3 plugins should receive periodic sub buffer automation timestamps every 5 msec.
Can you verify that this is not an issue with VST3 plugins?

[Light Grenade]

Amazing update, especially re exporting. I have been waiting for this for awhile, it was genuinely the only feature that nearly made me switch fully to Reaper, happy days! 

Probably the best update yet. 

Edited August 26, 2021 by Light Grenade

[tecknot]

Thank you, Bakers!  This is an update I can really appreciate; improving and redefining existing features is what I look forward to.

Kind regards,

tecknot

[TheSteven]

Thank you!
This fixed the problem I had with Output Thermal v3 crashing Cakewalk!

[Noel Borthwick]

58 minutes ago, pwalpwal said:

i thought buffer only affected realtime playback/recording, not export, i thought export just took as long as it needed?

Buffer size affects performance. Processing 1000 small buffers vs 1 large buffer is a lot more expensive and therefore takes longer. 
Same reason why low latency is prone to dropouts.

[Noel Borthwick]

3 minutes ago, pwalpwal said:

my memory is probably failing, but i swear that it was previously stated that buffer size didn't affect the "offline" processes (bounce, export, unless it was "real time" selected) and the offline processes just took as long as needed

but there's a fair chance that has changed

thanks for responding

Nothing has changed - you misunderstood the statement that offline processes are not dependent on buffer size as far as dropouts go.
IOW unlike realtime playback a realtime export cannot fail even if it is running at a sub 1 ms buffer size because there is no such thing as a drop out for offline export. Of course this doesnt apply to a realtime audible bounce.