Jump to content

Recommended Posts

Posted

I know things like automation Lanes can cause the project to continue past the end but in this case in a couple of my projects it does stop correctly at the end but the exported file has more dead space at the end. What would cause this? Is there some way to catch it without having to export and test each file? Thanks for any suggestions!

Posted
4 minutes ago, charles kasler said:

I know things like automation Lanes can cause the project to continue past the end but in this case in a couple of my projects it does stop correctly at the end but the exported file has more dead space at the end. What would cause this? Is there some way to catch it without having to export and test each file? Thanks for any suggestions!

Set a "from", set a "thru to" and export that range.

 

  • Like 1
Posted
On 12/29/2023 at 7:25 AM, charles kasler said:

What would cause this?

It sounds like there is a reverb tail perhaps that Cake is including in the final bounce. IIRC (not in front of CbB right now) there is a check box that instructs CbB to include or ignore such things; again, IIRC. 

t

Posted

Do ctrl + end to to find out where it thinks the project ends

Then select the entire range of tracks between where you want it to end and where it does end

Switch on Ripple Edit All

Press delete

Switch Ripple Edit OFF (Important!)

  • Great Idea 1
Posted

I remembered that tip from an old post, maybe it was your post. It's a great tip but for some reason it didn't work this time. It could be user error but I thought I followed the instructions well.

Posted
2 hours ago, Bristol_Jonesey said:

Switch Ripple Edit OFF (Important!)

This can NEVER be overemphasized!

bit me the ***** recently, and I KNOW BETTER!

t

falls in the category of “best laid plans of mice and men”…

  • Like 1

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...