![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
I did a short TV documentary this week. Imported the aaf - no errors.
But when I was premixing there were several regions which showed the correct waveform information (I compared them to the rough mix from the edit department) but playing back something totally different - in fact they all played back the same take but different regions of that take. So I asked the editor for a new aaf. That helped - the new clips were playing back the correct audio. I finished the premix on Monday. Today - Friday I recorded the voiceover and began the final mix. And the problem was back again. Even in regions I did audio suite processing on. I always import the aaf into a basic folder and copy the audio to the tracks in my template. When opening the folder the audio on the tracks inside was ok which was good for me because I could get the mix done with minimal hassle. But the general problem is scaring me ![]()
__________________
MacMini 8,1/ 32GB Ram/ OSX10.15.7/ ProTools Ultimate 2023.6 + 2022.10 + 2021.12/ MTRX_Studio/ Yamaha AIC 128D/ BM Decklink Studio 2/ Avid S3 |
#2
|
|||
|
|||
![]()
Are you copying or forcing to target format in the import window options? I've seen random issues like yours when referencing external mxf media. But I've never had a problem forcing to BWF.
I guess begs the question was this an embedded or referenced AAF? Wave or mxf?
__________________
~Will |
#3
|
|||
|
|||
![]()
I always use "force to target session format" cause I also have experienced errors when using "link to source media".
__________________
MacMini 8,1/ 32GB Ram/ OSX10.15.7/ ProTools Ultimate 2023.6 + 2022.10 + 2021.12/ MTRX_Studio/ Yamaha AIC 128D/ BM Decklink Studio 2/ Avid S3 |
#4
|
|||
|
|||
![]()
Did you have issues re-linking any audio files?
If you render those clips now, will they show a different waveform, matching the (false) audio? |
#5
|
|||
|
|||
![]()
UPDATE: Problem solved - sort of...
Had the bug appear again last week. Seems it only happens when exporting an aaf from Premiere 2024 (regardless if embedded or not). When exporting an omf - file (separate audio due to the 2GB restriction of embedded omf) everything imports as expected in ProTools.
__________________
MacMini 8,1/ 32GB Ram/ OSX10.15.7/ ProTools Ultimate 2023.6 + 2022.10 + 2021.12/ MTRX_Studio/ Yamaha AIC 128D/ BM Decklink Studio 2/ Avid S3 |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Missing Clips in Matching Alternates list | dB-Pro | Pro Tools 12 | 0 | 01-22-2018 12:01 PM |
Default Matching Alternates behavior with MIDI clips | SigFriedChicken | Pro Tools 12 | 3 | 11-03-2017 04:11 PM |
Field Recorder Clips Not Matching Timecode? | Cheesehead | Post - Surround - Video | 0 | 10-10-2015 03:42 AM |
Matching Alternate Clips frustration | awe | Pro Tools 10 | 2 | 09-11-2012 11:07 AM |
Matching two clips that have different lenghts. | terluk | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 2 | 11-24-2004 11:51 AM |