Encountered an issue with both the non-interlace and interlace versions of the Proteus model. Output file stutters when played back both in Topaz UI, in external player and also when output file is brought into DaVinci Resolve for final output processing. And by stutter I mean it plays correctly for a few seconds and then it will jump back and replay a few frames, then play normal, then mess up again. This only seems to occur w/ the Proteus model and only after the latest update. Happens w/ all sources tried.
System is a custom desktop w/ Nvidia 4070:
Device name
COLOSSUS
Processor
12th Gen Intel(R) Core™ i9-12900K 3.20 GHz
Installed RAM
64.0 GB (63.7 GB usable)
Device ID
BAA53E08-6302-4508-9708-4304B2687930
Product ID
00330-71481-17919-AAOEM
System type
64-bit operating system, x64-based processor
Pen and touch
No pen or touch input is available for this display
The team is working on a patch for this issue as we have seen it appear as variable frame rates and issues where the clip frames are out of order and skip.
Search “VFR” at the top, and you’ll find a lot about ut.
I believe both Artemis and Port have the same issue. They drop frames for no apparent reason, causing variable frame rate, which in turn causes the stuttering you’re experiencing.
Unless you are using the AI models SDR to HDR and Rea XL, download v5.3.6. It’s the most recent version where variable frame rate isn’t an issue. You will have all the latest AI models, just like in current version except for the ones mentioned above.
That’s what I did and con confirm that it doesn’t have that issue. Version 5.3.6 works.
iMac Hardware Overview:
Model Name: iMac
Model Identifier: Mac15,5
Model Number: Z19E000ZFLL/A
Chip: Apple M3
Total Number of Cores: 8 (4 performance and 4 efficiency)
Total Number of Cores GPU: 10
Total Number of Cores Neural Engine: 16
Memory: 24 GB
System Firmware Version: 11881.61.3
OS Loader Version: 11881.61.3
Mac OS: 15.2 (24C101)
so when i am exporting and uprezing footage from either 1080i 29.97fps / 1080p 30 fps / 2160p 30 fps to 4k 60fps ive noticed when i apply the stabilization effect the output file goes down to 59.97 fps when i have selected 60fps as my output preset . is there any reason why this happens and is there a way to fix this within the video topaz ai app as i dont want to do further processing on the file. please advise
I frequently experience 30.00 fps footage being 29.99 fps footage after exporting, but so far I haven’t seen a clear pattern as to why it sometimes happens and others not.
I’m using Iris on both progressive and interlaced model.
My source is a quicktime DV but I experienced the issue on mp4, ProresHQ, Prores
I’m doing a lot of test.
When I’m rendering I clip to upscale and deinterlace it (720x576 x 2) The framerate is very wierd : The move is to forward then backward for 1 frame, then forward, then backward…
I’m workoing on Windows 10 - HP 7840
Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz 3.50 GHz (2 processeurs)
Here is my log files (Help > Logging > Get Logs for Support) logsForSupport.zip (1.3 MB)
Please help me fast because I need your software for professional needs
If it is for every frame, it sounds like your workflow is incorrectly interpreting bottom field first as top field first during the deinterlace step. DV is most likely to be BFF, but that cannot be assumed. Try changing the “parity” of the deinterlacer.
If it is for only some frames (say two out of every five), you may have telecined rather than interlaced content.
Most likely not a TVAI issue. Have a read on interlacing parity and telecine.
Can you reach out to help@topazlabs.com and include this forum link and upload the original input clip and the exported file to my dropbox?
You can securely submit your file(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something and include the file name. Submit File to Dropbox
Thank you for your help!
Your comment makes sens. I was hoping this could fix the problem but I correctly interpret the dominance of the field and tried all the options with the same result…
I am having the same problem. Upscaling is dropping frames. Frame Interpolation is off. I have a constant 30 fps file and after upscaling it is 28.621 variable fps. It doesn’t matter if the source is x264 or ProRes, my target is h265. This is a big problem. I step through the source and target files and I can see missing frames.
I just updated to 6.1 and I noticed a Force CFR option. This should solve my problem, testing now. I really dislike the new interface, I hope they fix it or give us a way to choose the legacy style.
I’ve recently discovered an issue with TVAI (or possibly just ffmpeg) that I’ve not seen before. My usual workflow involves using TVAI to clean up noise in 2160p footage without an actual upscale.
I use the command line exclusively for actual exports because I want to export to AV1 using SVT-AV1 for the encoding, so I have to do a pipe from TVAI’s ffmpeg to my own ffmpeg:
This is handy for me because I don’t need an intermediate file on disk and allows me to better use system resources so I can compress while I upscale. When video is a 2160p source, things work well. When it is a 1080p source, I get flooded with errors like the following:
It seems to be non-deterministic. Each run gives different DTS issues at different timestamps
It seems to be system-load dependent. Almost as if frames are being dropped somewhere or pushed to the pipe out of order. I can reproduce more of the problems by running more concurrent ffmpeg instances.
My system is a Radeon 6900XT GPU with a 7950X CPU and 64GB of memory and the latest version of TVAI. Logs are not useful in this case since it is just the command line.
This looks like it is relating to the known VFR bug that the team has been working on a patch for. As a workaround, quick fix in the GUI the team added a Force CFR option to the export codec settings.
A new patch is coming out soon that should resolve this though.
In Windows when I deinterlacex2 a video the final frame rate of the exported file is ~44-45 instead of 50fps. When I deinterlacex2 the same file on a mac with the same settings it’s done right - 50fps. It didn’t do that before. Only the last times. The problems where very hard with v6.0.1 and a little bit better with 5.5 but it’s wrong again.
