Export all tracks STILL cutting off the end of files randoml

[The Beatsmith]

Hello,

 

I've spent most of today exporting audio using the 'export all tracks' function. I've come up with a slightly tedious workaround for the fact that Logic X can't export all tracks within a certain cycle region.

 

I'm now checking the files and to my horror, i've found that Logic is cutting off the end of the tracks. I thought this bug was fixed years ago?! I've seen complaints about this from like 2006-2008!

 

See the picture below. The greyed out audio is the original, the blue audio underneath is the exported audio. As you can see the end point is random and it's cutting off the end of the audio!!

 

Why aren't the files all the same length, and the same as the original audio? I'm trimming the beginning and end times of the project.

 

No plugins, volume, pan or anything is used on these files, i'm just trimming and editing audio.

 

I really hope someone can help because this seems utterly ridiculous.

 

Please help me avoid this! I have to re-do an entire days work... what an utter waste of time.

 

Cheers,

 

Ed

[The Beatsmith]

I'm going to experiment with giving the project a little bit of 'space' after the regions, making the project longer, to see if that helps.

 

Edit: didn't work... how is this option even usable, then? I know this problem existed for years, but i was sure it was fixed...? What's the 2014 workaround?

 

Anything better than a 'put a bit of a silent region at the end of the project', because that didn't work at all for me (Logic still sees it as 'silence' and cuts it off).

 

I've seen a solution is to put a bit of 'noise' at the end, but I really would like to avoid doing that with this project - it looks incredibly amateurish!

 

Thanks!

[The Beatsmith]

Another anomaly: if you tick ' Bypass Volume/Pan Automation' (there is none, this is a new, plain project with no plugins, all faders/apn at unity, and no automation) when exporting, the exported files are double in size!

 

All files in the project are mono.... but for some reason the file becomes stereo when this is selected?

[Eric Cardenas]

Another anomaly: if you tick ' Bypass Volume/Pan Automation' (there is none, this is a new, plain project with no plugins, all faders/apn at unity, and no automation) when exporting, the exported files are double in size!

 

To be able to include pan automation you need to have a stereo file.

You can always route everything to a mono output instead.

[The Beatsmith]

That makes a bit of sense - however you'd think it'd be clever enough to know that the files are mono, and nothing is panned, so to keep the file mono?!

 

I've had the problem confirmed as a bug with someone, that occurs at 96KHz. I'll report it to Apple.

 

I'm also getting a further bug that: the gaps between regions are throwing the audio off. See pink original audio vs grey exported audio.... they are not in sync.... does nobody ever work/export files at 96KHz?!

 

I can't 'join' all the tracks as the project is huge and it would take me days.

 

Not sure what to do at this point.

[Ashermusic]

I can confirm this issue with cycle @96.

[The Beatsmith]

Hi Jay!

[slipperhero]

Yep, this is still an issue more than a year after the last post. I've tried this with both 96Khz and 44.1Khz projects and have audio tails being cut off in both. Does anybody have a workaround? Adding silence (or regions containing normalised audio content) at the end of each track don't fix the issue for me. And when this problem affects midi tracks, i also tried adding additional midi data long after the last midi notes, and that doesn't help there either. The tracks are still cutoff long before the effects tail is completed.