OS X Premiere 25.0 Quicktime v210 exports corrupt

[Av0101]

PAL Quicktime YUV 10bit Uncompressed exports have corrupt video

Source video: PAL 720x576 4x3 Uncompressed YUV 10 bit Quicktime, uncompressed PCM Audio
Export format: Match Source (Uncompressed YUV 10 bit, Quicktime)
Adobe Premiere/ME 25.0
OS Sonoma 14.6.1
M2 Mac mini Pro 12 Core 32GB RAM
AJA IO X3 Thunderbolt 3 for monitoring (v17.1)

Steps:
1. Import a PAL Uncompressed YUV 10 bit Quicktime into Premiere 25.0 (or any other media)
2. Set in/out points
3. Right click on source clip and Export Media
4. Choose Format: Quicktime, Choose Video Codec: Uncompressed YUV 10 bit 4:2:2, Match Source
5. Export

Result: Exported files open with green scrambled video when imported back into  Premiere 25.0

This issue first surfaced in OS X Premiere 24 and remains a bug for that version.

This fault does not occur in OS X Premiere 23.

[Kevin-Monahan]

Hi there @Av0101,

I'm really sorry to hear you're experiencing this issue with your exports. It sounds incredibly frustrating, especially when you're trying to maintain high-quality video standards. Here are a few suggestions that might help you work around this problem:

Potential Workarounds

1. Try a Different Codec:

   Instead of using Uncompressed YUV 10 bit, you might want to try exporting using a different high-quality codec like Apple ProRes 422 HQ or DNxHD 444 HQ 10 bit. These codecs are known for maintaining high quality and might avoid the corruption issue.

2. Update Your Software:

   Ensure that both your Adobe Premiere Pro and macOS are fully updated. Sometimes, updates can fix bugs that cause these kinds of issues.

3. Check Your Hardware:

   Make sure your AJA IO X3 Thunderbolt 3 and its drivers are up to date. Hardware compatibility issues can sometimes cause problems with video exports.

4. Use an Older Version:

   Since you mentioned that this issue does not occur in Premiere Pro 23, you might consider using that version for your exports until this bug is resolved in the newer versions.

5. Contact Adobe Support:

   If none of the above solutions work, it might be best to contact Adobe Support directly. They can provide more specific troubleshooting steps and might have a patch or workaround for this issue. Look for the chat pod to the lower right and ask for the "video queue." They will help you as they are trained to assist digital media creators like you.

Steps to Export Using ProRes or DNxHD

You probably are aware of how to do this, but in case you don't:

1. Open Export Settings:

   Go to File > Export > Media.

2. Choose Format:

   Select QuickTime as the format.

3. Select Codec:

   Under Video Codec, choose Apple ProRes 422 HQ or DNxHD 444 HQ 10 bit.

4. Match Source:

   Ensure that the settings match your source video as closely as possible.

5. Export:

   Click Export to save your file.

I hope one of these suggestions helps you overcome this issue. Dealing with software bugs can be frustrating, but hopefully, these steps can help you maintain your workflow. If you need any more assistance or have further questions, feel free to reach out. We're here to support you!

Best of luck with your projects!
Kevin

[Av0101]

Thank you for your reply Kevin.

We have tried all your suggestions.

Although exporting to Prores results in a file without corruption, we HAVE to export to Uncompressed YUV v210 .mov as that is the required archival delivery format.

I will  again contact Adobe Support directly via chat support.

Previously the support person could not resolve.

Is it possible for you to forward this bug directly to engineering and ask them to confirm it is on the list for fixing?

Best regards,

Adam

[Av0101]

Shivani from Adobe support found a workaround that avoids the export corruption in Uncompressed YUV 10bit 422 .movs.  Export via Media Encoder 25 and select "Use Maximum Render Quality" and "Use Previews" tick boxes. This doesn't work if you attempt to export directly from Premiere, you have to use Media Encoder.

So, still a bug but at least there is a workaround. He said he'd report this to engineering to fix.