rocstudio

1 hour ago, Mark MoreThan-Shaw said:

I am a bit confused.  You seem to say you do use the Browser but are requesting changes to the Plugin Manager ? 

If you already use the Browser then I can't see why you would use the Plugin Manager too. 

Sorry for the confusion! This has to do with strictly taking notes in the Notes section of the browser. I document many things in the Notes section about the mix version that I'm working. The notes get lengthy and there is no vertical scroll bar when the notes go past the bottom. 

Hope that helps! Thanks

Roc

My suggestion is to have a vertical scroll bar for the main Browser selected under the View Menu. I enter a lot of notes to keep track of changes I make and if the notes go far enough to go below the browser area you have to use the down arrow key to get to the end of the entered text.

Another option could be that the Mix stores all the notes pertinent to the mix so when you recall a past mix you have the information related to the mix that you're listening to. You probably need a  scroll bar even if this functionality was available.

Thanks

Roc

Matthew... Excellent! You are correct!

Thank you very much and Happy New Year!

Roc

Hello Matthew, I went back the both original themes (Tungsten and Mercury) and the Archive button is still being displayed incorrectly. I was assuming the Tungsten and Mercury are original. I'm not sure what to do to fix it if they are.

Any ideas?

Thanks

Roc

Thank you very much! I guess I missed that in the release notes! I appreciate you taking the time to provide the answer!

For some reason, the tab to transient completely stop working on all my projects.

I really the subfolders. Definitely helps with organizing tracks! It appears the Vertical Zoom function is not working on the Folders and Sub Folders. I don't know if that was intentional.

Thanks

Roc

20 minutes ago, Noel Borthwick said:

I can repro it with your file! I'll investigate it thanks.

Interesting... I just opened the file I sent to you and right clicked on the guitar clip and Bounced to Clip and got the same result. No audio!

I'm not sure what's going on! I hope you find it!

Here is a screen shot of the Export window.

Thank again@

Roc

13 minutes ago, Noel Borthwick said:

@rocstudio I'm not seeing any cases where audio disappears when you do a bounce to clip with buffer size set to 350. If you can reproduce this can you share a zip of your project folder so we can look at it?

I took my project and deleted all but two tracks. Created a copy of each track and bounced the copy to show there is no audio. The export buffer set to 350. Link below.

https://drive.google.com/file/d/1o0p48ZkTzQ91W7g8YdhpZYasxrmDhQ3t/view?usp=sharing

Thanks for looking at this!

Roc

3 hours ago, Noel Borthwick said:

Yes the that buffer size is global so is used by bounce to clip as well. That part is not new to this release.
Perhaps we should ignore that setting for bounce to clips since it has no UI.

I like your idea about ignoring the setting because there is no UI! It's not critical but that would probably eliminate any miss understanding.

Thanks for the explanation!

Roc

19 hours ago, Noel Borthwick said:

Fast bounce is not related to the buffer size option directly. All it means is that Cakewalk exports as fast as it can and is not gated by realtime playback.
The custom buffer size itself only applies when Realtime playback is unchecked in the 2021.09.

The only change in 09 is that fast bounce is now renamed to "Render in real-time". So to do the equivalent of a fast bounce make sure render in real-time is unchecked.

With buffer size set to "350" in the Export window and selecting Bounce to clip on a single track, the audio disappears. I set the buffer size to "Playback" in the export window went back to the clip and selecting Bounce to clip on a single track and it work fine. So the buffer size in th Eport window has an impact on just regular clip bouncing. It seems strange that the Export function is impacting just regular editing of clips.

Thanks

Roc

On 9/17/2021 at 2:18 PM, Noel Borthwick said:

We just updated the EA build to 134.  Build 134 has a single fix to address a hang with the Realtek ASIO driver. If you have this driver installed you can update to this build to try it. We've unblocked this driver from the compatibility list for now.

 

Thank for your support! This version is great! The new transient function saves me a ton of time as well as the new export functions!

If you can let me know what to do about the UAD duplicating track issue I have, it would be greatly appreciated. I can contact UAD if you don't see any issues with Cakewalk. Also, if I need to start a thread for this let me know.

Thanks again!

Roc

12 hours ago, Noel Borthwick said:

@rocstudio 

uad  can't handle multiple plugins in the same session set to the same sample rate.

Issues like this can be project specific so if you have a recipe save a simple project file with audio and send me a link.

 

 

Noel,

Hope you are well!

I used the project I sent you before but made it very small. One guitar track with multiple plugins on the track. Every time I duplicate that track with Events, I get a Sample Rate Error and a Buffer Size Error.

I put the project on Google Drive link below.

https://drive.google.com/file/d/1MGZU0jzDyYJ4pH5nNcMU_75vdGribJKr/view?usp=sharing

Thanks for your help!

Roc

1 hour ago, Noel Borthwick said:

@rocstudio 

uad  can't handle multiple plugins in the same session set to the same sample rate.

Issues like this can be project specific so if you have a recipe save a simple project file with audio and send me a link.

 

 

Great information! I'll be able to send you something tomorrow. Maybe tonight, depending on how late I get home!

Thank you!

Roc

18 hours ago, Noel Borthwick said:

Weird. We'll check that its initializing with the same sample rate as the project.

Noel,  Just curious if you had time to find anything out about this UAD sample rate message I get when duplicating a track. I'll contact UAD if you don't see anything.

I won't be able to test today but I'll be able to communicate.

Thank you for all you support!

Roc

2 minutes ago, Noel Borthwick said:

@rocstudio thanks for doing these tests. I appreciate it. Based on my findings it  appears that UAD plugins don't really process much faster than realtime so this might be a known limitation. 

I'm trying another optimization to parallel process this which may help. I will PM you directly to try something soon. BTW did you try bouncing at your playback buffer size instead of using 350? I wonder if UAD plugins don't like large buffer sizes and that causes an issue.

I did not try that... I will!

Thanks

1 hour ago, Noel Borthwick said:

@rocstudio A quicker test may be to start out with all FX bypassed from the global FX bypass on the toolbar.
Then go to each individual bin one by one and unbypass, retesting the bounce each time. When the delay comes back you have the plugin causing it.

 

I tried your suggestion. I did not find any one bin with or without UAD plugins that caused the delay in the progress bar starting. So I tried a couple of other tests.

1. Starting point - all effects bypass like you suggested, but then starting with the first track with effects, I unbypassed that bin ran Track export via Run Task. Then I unbypassed the next track with effects and ran Track export via Run Task. I continued that process, adding track with effects  and running task and each time I added a track with effects, it got about 1 to 2 seconds longer then the previous run before the progress bar would start.

2. So then I just bypassed only the UAD plugins and the progress bar started relatively quickly! So it does appear to be the UAD plugins.

3. I did get an error one time that I could not duplicate (below), but I thought I'd let you know anyway. This happen one time when going through the original process you suggested. I tried to duplicate what I could have possibly done to cause that, but was unsuccessful.

Thanks again!

Roc

8 minutes ago, Noel Borthwick said:

Sure you ran 126? If so I'm not sure why those plugins are blocking processing for so long. I'm definitely informing the plugin about offline bounce now.
Does the same issue happen even with normal exporting without a task queue?

You can narrow it down by bypassing your plugins one by one till you find which ones cause the issue. My hunch is this is UAD specific.

Yes... I did run 126.

Yes it performs the same way with just a regular export and same parameters as Run Task.  About 35 Seconds to Progress Bar Start and about 40 seconds after Progress Bar complete.

I can perform the test you are requesting. Just some clarification...

You want me to bypass each effect type, run export/task export and turn that type back on and go to the next type... Right?

Obviously turn them off without turning them back on, won't really tell much... but I do want to be clear on what you're asking for.

I'll get started on that in about an hour! I gotta finish up some stuff!! 🙂

Thanks

Roc

21 minutes ago, Noel Borthwick said:

@rocstudio can you please try this new build 126  with BounceFlushTailsMaxDurationSec set to 20.
It now properly signals offline mode when bouncing. Hopefully there is no predelay with this one.
Let me know...

Results from testing this Build 126... 

I preformed the Track Export via Task Queue Run Task function twice. 30 to 35 seconds before progress bar started. 35 to 40 seconds after progress bar finishes. This is the screenshot after the progress bar is complete but waiting the 35 to 40 seconds to finish/complete. 

Something new... When preforming this I happened to hit Run Task again (for my second test) and it did not give me the "Are you sure you want to overwrite existing files" message. So I did a test on the Export button and I do get the message every time, even if I cancel and Export again. So the Run Task does not seem to match that functionality.

Thanks again!

Roc

34 minutes ago, Mark Morgon-Shaw said:

I don't know if anyone else has the same experience but this release seems more prone to falling over when duplicating a VSTi track ( inc note data )

 Sometimes it works , other times the whole thing freezes and stops then closes without warning  - I suppose it could be a plugin on my end, more testing required

I just tried this with tracks on my project that have UAD plugins. I received pop messages from my UAD plugins that indicate sample rate did not match what was expected. This appears to be a UAD problem.   

The duplication of track without any effects worked fine for me.

51 minutes ago, Noel Borthwick said:

@rocstudio "much better" as in there is no pre and post delay for the bounce?
I suspect I know what is going on. Your UAD plugins are processing in realtime and slowing down the export. I've made a change that should solve that issue if so.
I'll send another build to try shortly. In the meantime you can verify this by bypassing all your UA plugins and exporting with BounceFlushTailsMaxDurationSec  set back to 20 msec which is the default.

Answering... "much better" as in there is no pre and post delay for the bounce? Correct!

Part 2... I set the BounceFlushTailsMaxDurationSec back to 20 second, restarted Cakewalk, and selected Bypass FX Rack via right clicking on all tracks and buses with effects. Not just UAD but any effects, regardless of manufacturer. Also, I did not bypass any Cakewalk ProChannel effects. The export tracks worked great!

Thank you!

Roc

2 minutes ago, msmcleod said:

This is there to allow reverb tails to continue after the end of the audio. If you have reverbs on your track (and you're bouncing with effects), they'll get cut off if this is set to zero.  

20 secs is the cut-off point where it just gives up, but most of the time it'll cut off well before then unless you've got a really long reverb.

Thank you for explanation! I have, on occasion, had to have a long reverb tail at the end of a track, but I always use automation to kill it where needed. It's never been 20 second! 🙂 

Thanks again!

Roc

12 hours ago, Noel Borthwick said:

@rocstudio So the same issue occurs with bounce to track when bouncing the full project correct? That means the delay is happening when flushing effects tails with some of your plugins. Do you have some plugins that are generating audio even with silence or very long reverb or delay tails?

You can try changing this variable in the configuration file BounceFlushTailsMaxDurationSec

Go to Preferences |configuration file | Edit Config File
Search for BounceFlushTailsMaxDurationSec and set the value to 0 and save the file. 
Then close Cakewalk without changing anything else
Restart Cakewalk and retry the bounce. 

This should perform the bounce without doing any effects tail flushing. Let me know if this solves the issue.
 

 

My BounceFlushTailsMaxDurationSec was set to 20. That must be a default because I have never updated that. I set that to zero and it works much better. Sorry but I have to ask... Do you happen to know why 20 is the default and when would I ever need a value other than zero? 

Thanks again for your help! This new version will save me a ton of time!

Roc

4 minutes ago, Will_Kaydo said:

How long is the clip? The entire project length? Are you bouncing to clip? To track or bounce to export? 

The clips are project length of 4 minutes 10 seconds. It appears that the bounce to clip works much better with build 124.  When ask to perform the test on bounce to track. That was done via export. I don't know how  else to do it. Sorry I was unclear. I selected all 25 tracks when performing the bounce to track through the export function and experienced the 35 seconds before progress bar about 45 sec to complete after the progress bar. I assumed that Noel's request was for me to test it that way. But if there is another way, I'm happy to try it.

Thanks again!

Roc

4 hours ago, Noel Borthwick said:

@rocstudio looking at the video I can't fully see whats happening but it appears that the lag is happening before and after the actual bounce happens. i.e. before and after the progress bar runs from 0 to 100% and shows activity. Is this correct? If so this means that the actual bounce happened quickly but the startup and shutdown took time.  Please confirm that this is what you saw.
Also if you select the same time range for all tracks in the project and do a bounce to tracks instead of bounce to clips do you see a similar lag?

Your project didn't include audio but it contains several UAD plugins. I suspect something expensive is happening there. I can send you a build to test with my optimization in case it helps. Perhaps you could upload the file "Top Snare (Bounced, 326).wav"

 

Sorry I missed your response and questions.  I agree with your assessment and it appears you did fix that problem. I will test the bounce to tracks on this Build 124 to see if it has any issues.

I just tested the bounce to tracks on the original project with all the tracks with Build 124. It took about 35 seconds for the progress bar to start and after the progress bar completed about 45 sec to complete. So it appears that this is a problem with that function even on this new build.

Thanks for thinking of that test!

Roc