Jump to content
Morten Saether

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

Recommended Posts

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.

image.png.e4d9986eb2ca3539635387b001d64e53.png

Share this post


Link to post
Share on other sites
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?

  • Great Idea 1

Share this post


Link to post
Share on other sites
3 hours ago, msmcleod said:

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

add a timestamp to the filename?

Share this post


Link to post
Share on other sites
Posted (edited)

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 by Light Grenade

Share this post


Link to post
Share on other sites
22 minutes ago, Noel Borthwick said:

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.

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
16 minutes ago, Noel Borthwick said:

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.

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

Share this post


Link to post
Share on other sites
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.

  • Like 1

Share this post


Link to post
Share on other sites
16 minutes ago, Noel Borthwick said:

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.

so only the automation depends on the buffer size, unrelated to possible dropouts that might occur with realtime bounce/export? i think i mixed up the automation resolution with bounce/export

thx for your patience :)

Share this post


Link to post
Share on other sites

EXPORT

 

1 - When clicking on EXPORT, the application checks if the final file exists. If there is question if it is to replace. The same does not happen when clicking on RUN TASKS, even though the TASK is equal to EXPORT. I don't know if this is from the application's specification or I shouldn't do the same in order to alert the user.

 

image.png.d28f48c27ab70789ff202c568c99907c.png

 

2 - Under certain conditions that I did not identify the export using tasks generates a new file with an index

image.png.179295da014667da723c2a25e596bd64.png

Share this post


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

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.

image.png.e4d9986eb2ca3539635387b001d64e53.png

So you want to export all vocals as a stereo mix? If so why not just bus them to stems in your project which is a standard way to do it.
You can send them either to buses or to individual aux tracks.
Then you can use source category tracks or buses to pick these and export.

  • Like 2

Share this post


Link to post
Share on other sites
3 hours ago, Noel Borthwick said:

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.

Thanks Noel.

Grateful for all for sure. I understand your pov about tasks, but for me the task of creating an mp3 is almost always the same as is my wav file export from mastering. I rarely use anything else other than my original 24/48 mixdown file.

Mp3 presets would be a tremendous saving!

  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, Milton Sica said:

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.

This is expected. You can easily recheck all the tasks. Press CTRL-A in the task window and then press SPACEBAR to toggle them back on.

  • Thanks 1

Share this post


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

Thanks Noel.

Grateful for all for sure. I understand your pov about tasks, but for me the task of creating an mp3 is almost always the same as is my wav file export from mastering. I rarely use anything else other than my original 24/48 mixdown file.

Mp3 presets would be a tremendous saving!

You have noticed that the MP3 and Windows Media audio settings now have a checkbox to use the same settings for all output files?

Share this post


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

So you want to export all vocals as a stereo mix? If so why not just bus them to stems in your project which is a standard way to do it.
You can send them either to buses or to individual aux tracks.
Then you can use source category tracks or buses to pick these and export.

Yes I have to export the contents of each Folder as a stereo mix with all downstream FX  ( i.e. to send to the mastering engineer who can do a better job with 5-6 stems than one stereo file  )

Routing them to a group bus is not always an option because sometimes the bus FX is not suitable for every track within the stem. i.e. a Drum bus with heavy compression is great for kick - snare - room - overheads....but it can destroy the sound of the cymbals. So cymbals are often routed straight to the Master bus but are still part of the Drums stem.   

Folders group things together perfectly with flexible routing so being able to pick them to export would be a huge workflow advantage.

Share this post


Link to post
Share on other sites
Posted (edited)

More issues in need of explanation?

OK... I finally managed to wangle getting an empty project to have saved my tasks and attempting to use it?

Processing goes as expected but files are not in the NEW folder that was selected. To do that it appears I need to create new tasks that contain the folder info? I don't know because I'm not finding the files there either?

I'm also wondering how the song name inside the mp3 is going to change from the settings used previously while creating the template...?

Sorry to say it, but so far I'm not seeing this helping yet... Not for this situation anyway... In the right direction, but it would require some major changes in my work model to figure this out.

I simply use a song project as my mastering template for many songs in need of simple, quickie mastering so one project covers all songs. But this implementation will not allow for that. Folder paths, internal mp3 naming etc....

 

So it helps a tiny bit as I can create the two tasks I need and walk away not needing to do each separately, but that's all it will do. I must create new tasks for every song mastered this way.

 

I'm feeling a bit deflated...

 

 

Edited by Keni

Share this post


Link to post
Share on other sites
4 hours ago, Noel Borthwick said:

Can you verify that this is not an issue with VST3 plugins?

I rechecked the version of String-Studio VS-3 I was using when this issue occurred. It was actually the VST3 vsti of that plugin.

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...