P: Keine Metadaten bei AAF-Export in 24.2.1 / No metadata on AAF export

[Haggit]

Als ich mit der aktuellen Premiere-Version 24.2.1, die ich am 23.02.2024 installiert habe, von meinem Filmprojekt nach Picture Lock einen AAF-Export gemacht habe, konnte der Sounddesigner die Timeline zwar in Pro Tools öffnen, aber die ISO-Tracks nicht zurückholen. Das lag daran, dass alle Metadaten nach dem Export weg waren. Start-TC war angeblich immer 00:00:00:00. In Premiere selbst waren die Metadaten der Audiofiles aber vorhanden und bei früheren Tests, wo wir AAFs exportiert hatten, ging auch alles. Das war aber vor dem Update von Premiere.

Ich habe also die vorherige Premiere-Version 24.1.0 installiert und der AAF-Export hatte wieder seine Metadaten, einschließlich korrektem Start-TC.

Windows 10 Pro 22H2, 64 Bit. AMD Ryzen 5 2600 Six-Core-Processor, 3.40 GHz. 32 GB RAM. NVIDIA GeForce 1660 Ti.

[Todd_Reeder]

Wir bräuchten ihr Projekt und einen Screenshot ihrer Exporteinstellungen, um es sicher zu wissen ... ich weiß nicht, wie ich das auf Deutsch anfragen soll

[Bruce Bullis]

[requested necessary files]

[Haggit]

I can write in English, no problem. Thank you for your assistance.

Here are some screenshots of my AAF export. I tested it with and without "use tape sources when present", but it made no difference. Then I took the exported Wave files into Wave Agent I saw that the exported files from Premiere Pro 24.2.1 have always the Start TC 00:00:00:00. When I exported it with the previous Premiere Pro 24.1.0, the Start TC is correct and the sound designer can work with it in Pro Tools.

You can download my project file here. https://we.tl/t-Z6t1rPMAgF  If you need further files please let me know.

[Kanye Yuski]

In Ver 24.2 & 24.3 Premiere Pro
If you export a sequence in AAF with the above version, the original time code of the Wav file will be disappeared.

This case can be confirmed below.
Pr ---> aaf ---> Da vinci
Pr ---> aaf ---> Pro tools

The problem did not occur with Ver23.6.

Please release an improved version ASAP!

[Bruce Bullis]

Odd. 

Could you provide us with a project containing the sequence you're exporting, and one such .wav file containing timecode, that PPro is now ignoring? 

[Tech29280971fn3r]

Currently when exporting out an audio aaf from premiere, it will give every clip a timecode of 00:00:00:00. When bringing this into pro tools we can see all the clips timecodes have been stripped and replaced with 00:00:00:00.

Can something be done to fix this? To be able to export out a audio AAF which keeps the source timecode metadata. Other NLE systems have been able to do this for years.

[Bruce Bullis]

Hello Tech,

Could you let us know the AAF Export settings you're using? [A screenshot would be fine]

[Exquisite_build5C92]

I have exactly the same problem.

[ono-d]

Hello.
I am experiencing the exact same problem.

When I export AAF with v24.4.1, all Start TCs are rewritten to 00:00:00:00.

In v23.6.5, the Start TC of the original material is retained during export, thus avoiding this problem.

This bug is critical for audio workflows using Protools and should be fixed as soon as possible.

Image attached.

[Todd_Reeder]

Thank you for the additional information.  Could you please try and export the AAF in 16 bit instead of 24? do you get timecode then?  Could you also try a different export where you are still in 24 bit, but exporting to AIFF instead of WAV?

[ono-d]

Sorry for the late reply.

The result was the same when exporting in 16-bit wav.
Also, when exporting in wav from a sequence, the TC seems to be rewritten to 00:00:00:00.

In the case of AIFF, the original TC was retained and exported.

Versions after 24.x seem to have problems with wav output.

[Gemstone Chris]

I used to be able to export a clip's audio to a WAV file with timecode for external processing. It was extremely useful because I could easily replace the old audio in a sequence with the new, or easily create merged clips.

Now that's no longer the case. Every WAV comes back in with timecode at zero.

I have included two WAV files exported from the same video clip: an older one from June of 2023, and one I just now exported (files are silent to protect client privacy). When brought back into Premiere, the older one retains the timecode of the original video clip, and the newer one does not. The only difference is the older one was exported from Premiere 2023, and the newer from Premiere 2024.

I don't think I'm doing anything different on export (the metadata tab is activated), so has Adobe removed this functionality?

Thanks,

Chris

[Kevin-Monahan]

Hello @Gemstone Chris,

I'm Kevin from Support, one of the moderators here.

I read your bug report. Can you give the team more information to reproduce the bug? How do I write a bug report?

I hope they can help you ASAP.

Much appreciated!
Kevin

[Gemstone Chris]

Hi, Kevin. Thank you for your help. I'll try to provide as much information as I can.

I'm running Premiere Pro v24.3.0 on a Mac Studio M1 Ultra running Sonoma 14.4.1. The problem I am having occurs regardless of the kind of source media I am using, but the sound files I previously attached came from an MXF file, Sony XAVC-I, with timecode. I load that clip into the Source window and export WAV files using the following settings:

When I used to do this on Premiere Pro 2023 last year (I don't remember the exact version number, sorry). the files contained timecode that remained there when imported back into Premiere. Now under v24.3.0, they do not. The files I attached should be identical, but the one from 2023 (that preserved timecode) is 16 bytes larger, and a hex editor reveals quite a few differences between them. Premiere is writing these WAV files differently than it used to.

Thanks,

Chris

[Nicholas28310091sn7q]

Just a note that this is still happening -- I cannot get an AAF with timecode to my sound editor out of Premier, more of less killing our pipeline.

[Bruce Bullis]

We're investigating.

[Kevin-Monahan]

Status update: The team is investigating the issue more closely.

[Kevin-Monahan]

Hi @Tech29280971fn3r,

Thanks for the message. It’s been a while since you filed this bug. Are you still having this issue? If so, can you provide the info the product team member requested?
 
I'll move your post to the Discussions board while we await your information.
 
Thanks,

Kevin

[Mr. The Guy]

Were you previously on an Intel Mac? I am currently having this issue with 24.1 on an M3 Max, but am NOT having it on an Intel Mac with the same version of Premiere. 

[Gemstone Chris]

No, it wasn't Intel. It was working fine on my M1 Mac Studio, and now it doesn't.

[Pro38841370pxzt]

This issue is still occuring and is a huge workflow issue. This is really a horrible bug. From my tests, Premiere is not sending original audio timecode when an AAF is created even though that info is in the project sequence. PLEASE FIX ASAP. 

[Zbyszko Rylec]

I can confirm. In Premiere 23.6 extracted audio clips contains source clip timecode (the one that was used to extract audio from). In 24.5 version all extracted audio clips starts from 00:00:00:00. There is a similar bug with alternating TC of clips. Sometimes it works, sometimes not. It started about a year ago and still isn't fixed! 

[Kevin-Monahan]

Hello @Zbyszko Rylec,

I'm Kevin from support, and I'm a moderator here. I apologize for the ongoing problem with audio timecode. This sounds very frustrating.

I hope the product team will provide an update on this bug soon.

Thanks,
Kevin

[Edouard Jeanjean]

Hi @Kevin-Monahan,

We have exactly the same problem with Adobe Premiere 2024 on Windows: when exporting WAV (wav or AAF/wav export), the timecode is set to 00:00:00:00.

We use audio shooting rushes as well as picture-in-picture proxies. And when exporting audio (even if we put the native audio in the timeline), Adobe Premiere exports wavs without timecode (delays).

Best Regards

[Kevin-Monahan]

Sorry about that. Let me try and get a response for you. @mstegner, have you seen this issue yet?

Thanks,
Kevin