EXPORTING IN PRORES RESULTS IN A MISSING FRAME

Video AI Bugs and Issues
1

This issue was not happening in version 4.XX is only happening in all versions 5.XX

Exporting a video after stabilization in all flavors of ProRes results in a missing frame at the end.

example, if a video duration is 12 seconds with 18 frames, the result video will be 12 seconds with 17 frames.

Also not happening when exporting in HEVC or h264. So it must be a PRORES thing.

1 Like
2

The team is looking into some issues with ProRes at this time.

3

We are finding the same issue is persisting as well. Here’s our process:

  1. Bring all clips into Topaz. Clips are PNG sequences.
  2. Click on each preview frame in Sources and allow the clip to load in the Preview window.
  3. Play the clip in the Preview window to ensure that it has loaded.
  4. Click the Clear In/Out button to ensure that the clip isn’t being truncated at the end (often times, it is truncated by 1 to 4 frames).
  5. Add our preset to all clips.
    – At this point, many exports come out with the same number of frames as input. However, there are enough instances where clips are still missing frames that we have to redo QC on each clip to check the resulting QT against the number of input frames.–
  • If the clip is still short of frames, we must then go back to those clips, run steps 1 to 5 again, and then add the next step:
  1. Scrub to the start of the clip and click “Mark in”, then scrub to the end of the clip and click “Mark out”
  • After that, we re-export and QC the clip once again. Generally it works, though I’ve had to do it twice on at least one clip before it output the correct number of frames.

Our setup:
Alienware running Windows 10 Home (Though this is also happening on other machines we’ve tried with different specs)
Ryzen 7 7700X, 4.5 GHz
32 GB RAM
4080
Topaz Video AI Version 5.1.4

Topaz settings:
Uprez from 720P to 1080P
Frame rate: 24FPS (unchanged from original)
Enhancement: Progressive, Gaia, Computer Generated
Add noise: 0
Focus fix: off
Frame Interpolation, Stabilization, Motion Deblur, Grain: All off
Export to Prores 422

Ideally, I’d like to be able to drag all the clips in and start them processing without having to go through steps 2-4 and step 6, or even select all of the clips and batch correct them by clicking the the “Clear In/Out” button without having to play each one individually.

Thanks in advance!

4

Are you able to upload the logs for review?

How To Obtain Your System Profile (Windows)

To gather logs, please select Help > Logging > Get Logs for Support and attach the zip file to this post or you can send them directly to the support team at help@topazlabs.com

5

Any news on this issue? its extremely frustrating since I exclusively use prores in my workflow.

Like I said before, this was not happening in previous versions…

what I notices is that for example if I put a video encoded at 23.98, the result video is encoded at 24.04 frames. so weird… and the missing frame at the end.

Please fix this.

1 Like
6

The QA and Engineering teams are still trying to fully replicate this issue to understand what is causing it in the app so that the devs can patch it.

7

Let me speed of the process please, grab a 23.98 fps ProRes video, put it in the software, apply stabilization full frame at 30%, only that, export it in any flavor of ProRes, compare the 2 videos in a video editing software, you will notice the exported one is one frame less an also encoded wrongly at 24.08 fps.

here I also attached the logs.

logsForSupport.zip (634.9 KB)

8

Having the same problem with missing single frame at tail of export. I am bringing in ProRes files to Video Ai Beta - usually the missing frame seems to exist at this stage already - An exported file from the edit will show 6:07, but the same file in VAI Beta will show 6:06.

Adding handles would be a fix, but when working with hundreds of shots in a sequence, this is an unrealistic and time consuming work around.

1 Like
9

Yes, and the worst thing is that this problem is new starting with versions 5.XX.

Was not present in any other previous versions.

1 Like
10

Still happening in V5.2.1. Needs a fix ASAP as it’s unusable. One frame missing from multiple exports every time I export. No support option via site, very bad look.

1 Like
11

Yeah, they are totally ignoring this problem.

How many months more to try to “replicate”?

It wasn’t even there in the previous versions…

1 Like
12

Are we getting gaslighted on this problem?

1 Like
13

Not at all. The dev team is working on this issue and trying to resolve the backend that has made it appear in the past few versions. They have been made aware of this thread.

14

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.