Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Software > Pro Tools 2020

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 05-02-2020, 03:39 AM
midi sordino midi sordino is offline
Member
 
Join Date: May 2001
Location: Dublin
Posts: 238
Default File Export Bug in 2020.3

Hi all,

Noticed a weird bug in PT 2020.3. When I export tracks as an AAF file and re-import the file into the same session (Import >Session Data), the timecode stamp of the imported files is late by exactly one frame every time.

Can anyone else please explain/ replicate this?

In case anyone else tries this, the session in question is 25fps/ 24 bit & 48khz and I'm using WAV files.

Thanks,

M

(PT 2020.3 / iMac Pro/ OS 10.13.6)
Reply With Quote
  #2  
Old 05-04-2020, 04:11 AM
Ale Ale is offline
Member
 
Join Date: May 2001
Location: Germany
Posts: 622
Default Re: File Export Bug in 2020.3

Hi
I did a quick test. Did Export import with 20.3 The region sits as before. No delay..

Sorry no help from me.
Did you delete the prefs?

When things get weird it helped me a lot since 2019.10.. Before that i rarely had to delete prefs,

Ale
__________________
3x PT HD Ultimate 2020.03 6/12-Core Westmere/ 48 GB / OS 10.13.6 / 96 I/O / 192 I/O / Omni / BM Intensity Pro (Driver 11.4.1)
1x PT 2019.6 / MacMini Server late2011 / 16 GB / OS 10.13.6 / 002


www.tonstudio-gress.de

www.facebook.com/TonstudioGress

Last edited by Ale; 05-04-2020 at 10:05 AM.
Reply With Quote
  #3  
Old 05-04-2020, 06:50 AM
midi sordino midi sordino is offline
Member
 
Join Date: May 2001
Location: Dublin
Posts: 238
Default Re: File Export Bug in 2020.3

Thank you for checking. Appreciate it. Are you on High Sierra? I've tried trashing prefs but it does not solve the issue. I use an iMac Pro and a MacBook Pro and the issue is on both computers. Both are using 2020.3 and both are on OS 10.13.6.

I'm exporting stereo files using 'Enforce Avid Compatibility'. Want to send to an editor using Media Composer. I've attached files showing an example of the issue using a stereo track. I export a track (St Mix) in a session as an AAF file. When I re-import the exported AAF file back into the same session (Import >Session Data), the timestamp is one frame later than original. This happens in other projects also, so not a corrupt session. If anyone's interested I've attached screenshots of an example.

I've opened a support case with Avid. Let's see if someone can work this out...

M
Attached Images
File Type: jpg Export Track as AAF.jpg (67.0 KB, 0 views)
File Type: jpg Import Track back in as AAF.jpg (64.4 KB, 0 views)
File Type: jpg Original Timestamp of St Mix.jpg (66.4 KB, 0 views)
File Type: jpg Timestamp fo imported AAF file.jpg (66.3 KB, 0 views)
Reply With Quote
  #4  
Old 05-04-2020, 07:00 AM
originalscottyg originalscottyg is offline
Member
 
Join Date: Jan 2006
Location: Detroit
Posts: 651
Default Re: File Export Bug in 2020.3

Just a thought, but are you sure your clip boundaries are on exact frame boundaries? The "Enforce Avid Compatibility" setting will constrain everything to frame boundaries, as NLEs can't edit finer than frames, usually. In theory, it shouldn't be shifting audio placement, just changing in/out points. But if there is no handle, and the clip edge is between frames, perhaps this is the result?
__________________
Scott Gatteño
Yessian
Reply With Quote
  #5  
Old 05-04-2020, 07:03 AM
Ale Ale is offline
Member
 
Join Date: May 2001
Location: Germany
Posts: 622
Default Re: File Export Bug in 2020.3

Yes High Sierra
Double checked again with mono and stereo tracks.
No difference.
Ale
__________________
3x PT HD Ultimate 2020.03 6/12-Core Westmere/ 48 GB / OS 10.13.6 / 96 I/O / 192 I/O / Omni / BM Intensity Pro (Driver 11.4.1)
1x PT 2019.6 / MacMini Server late2011 / 16 GB / OS 10.13.6 / 002


www.tonstudio-gress.de

www.facebook.com/TonstudioGress
Reply With Quote
  #6  
Old 05-04-2020, 07:11 AM
midi sordino midi sordino is offline
Member
 
Join Date: May 2001
Location: Dublin
Posts: 238
Default Re: File Export Bug in 2020.3

Hi Scott,

I think you're on to something. When I uncheck 'Enforce Avid Compatibility' and also make sure in this scenario not to select 'Quantise Edits to Frame Boundaries', the issue goes away and imported AAF files have the correct timestamp. Thank you. But as you say, I didn't expect the AAF file, re-imported into the PT session from which it was exported, to shift audio placement...
Reply With Quote
  #7  
Old 05-04-2020, 07:15 AM
midi sordino midi sordino is offline
Member
 
Join Date: May 2001
Location: Dublin
Posts: 238
Default Re: File Export Bug in 2020.3

Quote:
Originally Posted by Ale View Post
Yes High Sierra
Double checked again with mono and stereo tracks.
No difference.
Ale
Thanks for double-checking. Do you check 'Enforce Avid Compatibility' when exporting the track(s)?
Reply With Quote
  #8  
Old 05-04-2020, 07:16 AM
originalscottyg originalscottyg is offline
Member
 
Join Date: Jan 2006
Location: Detroit
Posts: 651
Default Re: File Export Bug in 2020.3

Understandable. I'm not sure how big your session is (it doesn't look to huge in the screenshot, unless that is just a test of a small portion), but I think your best bet is to set the grid to Frames and grid divisions to 00:00:00:01, then trim all your clips to frame boundaries. Then you can be sure that all the clips will translate seamlessly over to Media Composer.
__________________
Scott Gatteño
Yessian
Reply With Quote
  #9  
Old 05-04-2020, 07:54 AM
midi sordino midi sordino is offline
Member
 
Join Date: May 2001
Location: Dublin
Posts: 238
Default Re: File Export Bug in 2020.3

Thanks Scott. Yeah, that was just a test session. I will try that. Good idea.

You seem to be well-informed about AAF file export. It's new to me as I want to start using it instead of sending WAV files to the edit. Anyway, clip gain settings seem to translate over to the AAF file (albeit not precisely, which might once again be a frame-based issue), but I had expected to be able to export/import volume automation from my PT session using AAF. But no dice. When I import the AAF file, there's no volume automation...
Reply With Quote
  #10  
Old 05-04-2020, 08:01 AM
originalscottyg originalscottyg is offline
Member
 
Join Date: Jan 2006
Location: Detroit
Posts: 651
Default Re: File Export Bug in 2020.3

AAF export from Pro Tools is not as fully implemented as AAF export from NLEs, AFAIK. The usual workflow is for picture dept to export assets for sound dept to do audio post, then sound dept outputs final deliverables.

There are many others who are far more knowledgable than myself regarding AAF workflows. You might get more info posting this in the Post & Surround Forum. I have never really had to export AAFs from Pro Tools, so I am not sure what features are actually implemented.
__________________
Scott Gatteño
Yessian
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Bounce to Quicktime Movie File Crashes Pro Tools in 2020.3 JRV Pro Tools 2020 6 04-19-2020 07:41 AM
Pro Tools (2020.3) on MacBook Air 2020 compatibility pellekuipers Pro Tools 2020 1 04-04-2020 08:01 AM
New Avid Link 2020.1 - launched today 1/16/2020 marianna Licensing & Accounts 8 01-16-2020 11:43 PM
mp3 export doesn't show correct file size til another export done obidon Pro Tools TDM Systems (Mac) 0 12-09-2010 01:13 PM
How do you export an omf file???? NEIGHTD 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) 7 03-01-2006 11:04 AM


All times are GMT -7. The time now is 08:42 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com