Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

Long encoding and Frame substitution recursion

New Here ,
Jan 09, 2024 Jan 09, 2024

I am having a frustrating time trying to export my project. I am trying to export Apple Pro Res for the colorist but am experiencing long encoding (14 hours) for a 9 minute long film, and having the frame substitution error pop up. Something went wrong somewhere and I need to figure it out. Attached is the file properties, I am exporting to the Quicktime format, 4096x2160. I am using a windows pc Processor Intel(R) Core(TM) i7-6950X CPU @ 3.00GHz, 64 GB Ram. 

 

file path of footage.jpgexpand image

TOPICS
Editing , Error or problem , Export , Hardware or GPU
152
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 10, 2024 Jan 10, 2024

Hello @swagglepoo,

Thanks for the query. You say you are having trouble with export performance, right? May we have more details about your computer (CPU/RAM we know, but which GPU? What hard drives) and your source footage? Looks like Panasonic UHD V-log footage,or am I incorrect? Anyhow, more info would help greatly!

 

From the screenshot: since your source footage is H.264/HEVC-based, your computer should be in the "recommended" hardware category. Is it? It appears you may be coming up a bit short on system requirements given the task at hand. 

 

Forgive me if I am incorrect, but your Intel CPU might not have Quick Sync, which is rather crucial for handling H.264/HEVC files, particularly if they are 4K at 10-bit. If you do not have that, then there is no hardware acceleration of decoding/encoding the format taking place. Furthermore, you are transcoding to a wholly other codec, and a high-quality one, at that. Is there an input LUT in play? Are you scaling from UHD to full 4K? If so, there is also scaling and GPU accelerated effects in play. Given these tasks, asking your computer to do all this in a reasonable amount of time may be a bridge too far...

It may be time to treat yourself to a new computer, and one with a CPU containing the Quick Sync function so you can do what you really want; edit smoothly. Otherwise, you may have to live with these long processing times. Sorry about that. Let me know if you need more suggestions. We're here to help.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 11, 2024 Jan 11, 2024

Hey Kevin! Thanks for the quick reply, here's some more info about my pc stats.

Gpu: NVIDIA GeForce GTX 1080 Driver version: 31.0.15.4617 Driver date: 11/9/2023 DirectX version: 12 (FL 12.1)

Disk 1 (C:)NVMe Samsung SSD 960 SCSI Disk Device Capacity: 477 GB Type: SSD

Disk 2 (D:) Samsung SSD 870 EVO 4TB Capacity: 3.6 TB Type: SSD

Source footage info is correct, Panasonic UHD V-Log MP4/MOV H.264 10 bit 4:2:2, image resolution is 4098x2160 and there is no input LUT.

I have another PC I can attempt to export on as a back up just incase, and it has exported Apple Prores files from this Premiere project before successfully. I am just curious whether I am doing something wrong export or codec wise here or maybe this computer is not capable of handling this type of export like you said.

 

Thanks again!

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 12, 2024 Jan 12, 2024
LATEST

Hi @swagglepoo,

No, I think you've done the best you can with the system you have. 

 

You could try a smart rendering workflow with a system like this, where you "render as you go" to ProRes. Then export directly to ProRes. Then, you're not encoding, it's more of a copying process. Even better would be to shoot ProRes natively with your camera if it offers that feature. If it doesn't check out the Atomos devices, they're very slick. 

 

You have options, but you have to get change your workflow. Otherwise, you're due of an updated computer. Let me know if the advice helps.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines