ProRes MOV Files From Topaz Video 1.0.2 Not Importing Into Adobe Apps

Topaz Video General
1

Since updating to Topaz Video v1, The ProRes mov files it creates are unrecognized by Adobe Premiere, After Effects and Media Encoder. If have Topaz create an MP4 wrapped in a MOV wrapper, it works fine. If I use Shutter Encoder to convert the Topaz output to another ProRes format - that works too,

Seems like in v7 I could make ProRes files and import them into Adobe without issue. Thoughts?

2

Thoughts? Donā€™t use Studio itā€™s bugy

3

Sure. Thatā€™s an option.

4

Can you send the team the logs for review on the export settings you are using and the file specs?

help@topazlabs.com

To gather logs, please select Help > Logging > Get Logs for Support and attach the zip file to your reply.

We have seen issues before with exports not playing well with Adobe Premiere usually due to the audio format but have not been able to replicate it reliably on the devs end.

5

Prores exports have been broken since version 6. They come out with no timecode. If you run a FFMPEG repair on the file it will rebuild the timecode and work fine after that. I have mentioned it MANY times but they do not seem to care.

2 Likes
6

ProRes 422 HQ output only works fine in 4.2.2 but nothing newer for me.

Still persists with the latest Topaz Video and Topaz Video AI releases :frowning:

  • Wasted a few hours with the latest releases last night and still got what I thought was a corrupt file.

  • Will try it tomorrow to see if it fixes it but that might add hours to my workflow. :frowning:

7

Just minutes ago I exported three ProRes 422 HQ files. One from Topaz Video v1.1.0, one from Shutter Encoder v19.7, and one from Davinci Resolve Studio v2.3.1.

All of them imported into Premiere Rush and playback was ok. They also imported into Topaz Video ok. This is on Windows 10.

1 Like
8

I just tried it for a short clip in video AI and video and both gave me files that were not readable by VLC (and my other tools)

Topaz Video AI 4.2.2 does not have this issue.

I will file a bug and I hope this is fixed. I am a paying a customer (before and after subs) and have not been able to use anything after 4.2.2 for a primary workload as I need the output to be in intermediate of ProRes.

Info:

  • Windows Explorer shows 0 duration / some players fail / FFmpeg warns about missing codec parameters (pixel format), and MOV muxer warns codec frame size is not set.

  • Remuxing with FFmpeg makes the file usable, but for large files the remux step is extremely slow on NAS/SMB due to MOV finalization/faststart. My files are 1TB+ in size and this is a non-starter.

what ffmpeg sees when I try to repair the file:

command:

ffmpeg -err_detect ignore_err -i ā€œinput.movā€ -map 0:v:0 -map 0:a? -c copy -movflags +faststart ā€œoutput_fixed.movā€

std:

  • Could not find codec parameters for stream 0 (Video: prores (HQ) ā€¦): unspecified pixel format
  • Consider increasing the value for the ā€˜analyzedurationā€™ (0) and ā€˜probesizeā€™ (5000000) options

Move muxer error:

  • [mov @ ā€¦] track 1: codec frame size is not set

Metadata

  • videoai : Framerate changed to 60 using chr-2 replacing duplicate framesā€¦
    encoder : Lavf62.0.102
9

Perhaps it would be a good idea to post a link to short problematic output sample (a few seconds) on Dropbox or similar.

I did notice that a ProRes output file from interpolation with scene detection on, doesnā€™t display a media length in Windows Explorer. Even so, with scene detection on or off, the files still play fine in VLC and MPC-HC.