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
  #11  
Old 05-04-2020, 08:09 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. Yes, I'm only using AAF files to share work in progress with editor and director. Won't get into the detail, but it's less tedious for me than sharing timestamped WAV files when the project is being constantly recut as I'm exporting cues from Logic Pro X into PT and then want to send a bunch of ideas. My final deliverables as always will be on a PT session with sound team.

I tried moving file start point to frame-based boundary and unfortunately the issue still remains. Thanks for the suggestions.
Reply With Quote
  #12  
Old 05-04-2020, 10:03 AM
Ale Ale is offline
Member
 
Join Date: May 2001
Location: Germany
Posts: 622
Default Re: File Export Bug in 2020.3

Yes i did check 'Enforce Avid Compatibility'
My regions were not cut on the grid and then exportetd
When I import it back into session then the regions get extended (to the next frames) . Everything is in sync.

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
  #13  
Old 05-04-2020, 12:59 PM
originalscottyg originalscottyg is offline
Member
 
Join Date: Jan 2006
Location: Detroit
Posts: 651
Default Re: File Export Bug in 2020.3

Quote:
Originally Posted by Ale View Post
Yes i did check 'Enforce Avid Compatibility'
My regions were not cut on the grid and then exportetd
When I import it back into session then the regions get extended (to the next frames) . Everything is in sync.

Ale
Interesting. The OP didn't actually say that the files were out of sync (and the picture were too small for me to see clearly), only that the timestamps were incorrect. Were there changes in the sync relationship between clips or tracks in the AAF? Or was the whole AAF offset by the same amount? I remember a time when there was a bug with 23.976 OMF or AAF outputs from Final Cut that caused them to be stamped as 24FPS. This would just require the whole sequence to be nudged back into the correct timeline position when importing.

I was speculating as to what would happen if a clip boundary was between frames and there were no handles. Would the clip be trimmed to the next frame edge within the clip boundaries? Would the clip be moved on a subframe level to the nearest frame edge? If the latter, that would definitely be a bug in my book.

Considering that nothing came back incorrect in your tests, I think we must assume its a bug or an issue with the OPs system or particular session.
__________________
Scott Gatteño
Yessian
Reply With Quote
  #14  
Old 05-04-2020, 02:40 PM
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 originalscottyg View Post
Interesting. The OP didn't actually say that the files were out of sync (and the picture were too small for me to see clearly), only that the timestamps were incorrect
The files look like they're in sync but as I said, the imported AAF (exported from the same session) is consistently one frame later.


Quote:
Originally Posted by originalscottyg View Post
Considering that nothing came back incorrect in your tests, I think we must assume its a bug or an issue with the OPs system or particular session.
I wouldn't assume anything. As I said in an earlier post, I'm using two different computers to test this and it's not confined to one session, but any session I open. But thanks for the suggestions.

Last edited by midi sordino; 05-04-2020 at 02:54 PM.
Reply With Quote
  #15  
Old 05-04-2020, 03:10 PM
originalscottyg originalscottyg is offline
Member
 
Join Date: Jan 2006
Location: Detroit
Posts: 651
Default Re: File Export Bug in 2020.3

Quote:
Originally Posted by midi sordino View Post
The files look like they're in sync but as I said, the imported AAF (exported from the same session) is consistently one frame later.




I wouldn't assume anything. As I said in an earlier post, I'm using two different computers to test this and it's not confined to one session, but any session I open. But thanks for the suggestions.
Good to know that it's on multiple systems or sessions. I certainly wasn't implying that it's something you are doing wrong or is wrong with your system, sorry if it came across that way. It could be a bug related to something specific to the workflow you have with the picture department. Are you using MFX media in your Pro Tools session, or converting to WAV or AIF? There have been inconsistencies in the past with the way Pro Tools handles MFX media in sessions.
__________________
Scott Gatteño
Yessian
Reply With Quote
  #16  
Old 05-04-2020, 03:25 PM
midi sordino midi sordino is offline
Member
 
Join Date: May 2001
Location: Dublin
Posts: 238
Default Re: File Export Bug in 2020.3

Thanks. Yeah, the sessions I’m checking this on are pretty empty. No plugins and only a movie file with audio imported from the movie. Then some audio tracks with stereo clips of music cues imported from Logic Pro X. I recently updated to 2020.3 and haven’t changed anything from the default settings since download. But perhaps there’s a setting somewhere that is causing this issue. Will have another look tomorrow. Cheers, M.

Last edited by midi sordino; 05-04-2020 at 03:49 PM.
Reply With Quote
  #17  
Old 05-04-2020, 06:05 PM
laki laki is offline
Member
 
Join Date: Dec 2005
Posts: 512
Default Re: File Export Bug in 2020.3

Hello all!

I had a .Wav file that I exported (not as AAF just .wav) to an editor to do some re-cuts on a completed show. He resupplied me my mix as an Embedded AAF so that I could conform his edits.

The timestamp of the file start was off by 1 frame.
All the timestamps at each edit point were off by 1 frame.

I imported this into 2019.12, timestamps were fine.

I believe that this is an IMPORT issue not export.
Reply With Quote
  #18  
Old 05-05-2020, 02:17 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 laki View Post
Hello all!

I had a .Wav file that I exported (not as AAF just .wav) to an editor to do some re-cuts on a completed show. He resupplied me my mix as an Embedded AAF so that I could conform his edits.

The timestamp of the file start was off by 1 frame.
All the timestamps at each edit point were off by 1 frame.

I imported this into 2019.12, timestamps were fine.

I believe that this is an IMPORT issue not export.
Thanks for chiming in. As far as I can tell, this issue - timestamp on stereo WAV file late by one frame when re-importing an AAF file into the same PT session - occurs in Pro Tools 2020.3 when exporting an AAF and checking the box 'Enforce Media Composer Compatibility'.

If I don't check this box, the re-imported timestamps on the wav files using AAF import are correct. But I want to enforce media composer compatibility, so it looks like this may be an issue when exporting an AAF file from PT using this option (which might as well be called 'Enforce Pro Tools Incompatibility')
Reply With Quote
  #19  
Old 05-05-2020, 02:25 AM
Frank Kruse Frank Kruse is offline
Member
 
Join Date: Dec 2002
Location: old europe
Posts: 5,505
Default Re: File Export Bug in 2020.3

Quote:
Originally Posted by midi sordino View Post
Thanks for chiming in. As far as I can tell, this issue - timestamp on stereo WAV file late by one frame when re-importing an AAF file into the same PT session - occurs in Pro Tools 2020.3 when exporting an AAF and checking the box 'Enforce Media Composer Compatibility'.

If I don't check this box, the re-imported timestamps on the wav files using AAF import are correct. But I want to enforce media composer compatibility, so it looks like this may be an issue when exporting an AAF file from PT using this option (which might as well be called 'Enforce Pro Tools Incompatibility')
The "issue" is actually a feature to work around the fact that AVID MC can only refer to time stamps that are on the full frame grid, so in order to not move the audio in MC, PT will add additional media to fill the gap to the next full frame. The only way to avoid this is to always edit on the full frame grid.

F.
__________________
PTHDn 2020.5 (OSX10.14.6), 8x8x8, MacPro 5,1 3.33Ghz 12-Core, BM DeckLink SDI, SYNC HD, all genlocked via AJA GEN10, 48GB RAM, Xilica Neutrino, Meyersound Acheron
Reply With Quote
  #20  
Old 05-05-2020, 06:17 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 for your reply. I exported using the full frame grid (something I thought I'd already tried) and that finally sorted it. I can now send files that will match timecode stamps when imported into Media Composer & Pro Tools. Appreciate the feedback. Is it possible to also export volume automation into Media Composer or is it only clip gain?


Cheers, N.

Last edited by midi sordino; 05-05-2020 at 06:36 AM.
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 05:11 PM.


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