1/ did you tried the others export video option in the preference ?
2/ if 1/ doesn’t fix the issue, do you have this issue with all videos or only this one ? if only this one, then try to convert it to H264/H265 again with an another encoder and try to redo it again in VAi. maybe ffmpeg has some problem with the original codec used from your video for reason X or Y.
When I’m using Proteus to clean up an video (100% not upscaling yet), everything seems to work except for reds. Anything “red” in the image breaks into vertical lines. Because of this, the picture “out” is worse than the picture “in”. I’m sure this is new as I don’t remember seeing it before.
Hey,
1, Yes, I did try. mov/v9 doesn’t produce these issues.
2. All videos. I tried to convert to h264 and them Upscale as well, avail, no change.
Not sure what the issue might be, but I guess it’s related to the new 300% “boost” they introduced in the latest version.
that’s the input source I got. But previous versions didn’t produce this issue.
Write to the support. Software work great here, with H264 / Mp4 / Auto, with Temp directory Export video mode. on a A4500 RTX and a 1050ti.
they need to take a look at your logs and see why you have these issues. It’s not normal. Maybe it’s not the software related. Ffmpeg has is pro and cons too.
Version: 3.1.1
Feature request: Add name of output file to the output film label.
Why?: So a user is able to match the output file, in this case an export failure, to the input file so able to try again.
Whyl output failure?
I have 17 360º 5760x2880 prores files. I am applying manual proteus denoise and anti-aliase to them all, batch job. A few of the exports reported ‘out of memory’ (WHY??). This job is running on a Mac with 96Gb of memory. Jobs set to run across 4 GPU cards. All outputs set to 5760x2880 prores422 HQ.
I wish to repeat the files that have failed again, but is tedious if not possible to match output review image with the input image. It would be better to match input and output by file name. Or better still, put a link of the input which produced this output in the output’s details pane. Do not wish to just rerun the output again as the same settings may cause the failure again.
In the panel on the right (where you chose your AI models) there are some options at the bottom that lets you pick your container, bit rate, and video codec.
It is kind of limited (No audio codec options, bit rate options are “constant bit rate”), but it’s there.
If you wanted too, you can use the command line tools to do your processing. It uses a modified version of ffmpeg, so if you know how to use ffmpeg, you can use that knowledge to tune the video output to get the exact settings you want.
Although, quite a few video codecs are missing (I believe this is a licensing conflict?). You can build your own version of ffmpeg with TVAI tools.
Github repo: GitHub - TopazLabs/FFmpeg at topaz/develop
Useful instructions: FFmpeg/INSTALL-Topaz.md at topaz/develop · TopazLabs/FFmpeg · GitHub
If you don’t want to compile your own version of ffmpeg to get access to a specific encoder, then you can use ffmpeg piping to pipe the output from TVAI ffmpeg into a different ffmpeg with the encoders you want and encode your video/audio with that one. However that does come with increase memory and CPU cost.
1 Like
Hi
Not sure what you are talking about here but I also encountered an issue loading video into Vegas. Turns out that some options in VEAI cause the output video to be variable frame rate. I’m re-processing old HDV 25i video and randomly some file result in variable frame rate rather constant. Posted a question but had no response and still not found the definitive cause.
Developper explains it here :
https://community.topazlabs.com/t/temp-files-and-output-files/38853
Red colors are generally very critical when encoding. Test if the problem disappears with a different export format like ProRes or higher bitrates.
Hi there - thank you for the reply. This is not after encoding (although I use Pro-Res), this vertical pattern is introduced at the preview stage.
I have the same problem, after updating to 3.1.x the calculations became much slower 4-7x.
i7-11700K / 32GB / NVIDIA GeForce GTX 1660 / VRAM 6GB
Input 1920x1080 / Output 3840x2160 / 50fps / Artmenis
Before the update 9min, afterwards 43min
Not sure if it helps but here is proteus in 2.6.4 and 3.1.1
(Not the same frame but I think it shows the difference with the same input.
Which Driver and GPU?
Hi there - sorry…
3.8 GHz 8-Core Intel Core i7
AMD Radeon Pro 5500 XT 8 GB
Does that help?
which date has the driver?
Did you use stabilisation too?
H265 encoding appears to have problems, since upgrading to 3.1.1 anything encoded using H265 Main (NVidia) cannot be opened in Vegas Pro & I cannot edit tags in the file using TagScanner. Both these programs were able to use files created using the H265 encoder previously.
If I encode using H265 Main 10 (NVidia) everything is fine but obviously it is 10bit.
Looking at the files created by Topaz Video AI in MediaInfo the profile has changed from Main@L4@Main to Main@L3.1@Main but I am not sure if that is the problem as the Main 10 profile has also changed from L4 to L3.1 & still works fine.
No stabilisation - just really basic Proteus on automatic (although I tried tweaking a few settings in manual to see if I could fix/diminish the problem). Not sure of my driver date (I’m on a Mac OS Catalina 10.15.7)
Hi! Have had some restarts within 1 hour when running Topaz as the only app. Is it linked to that the screen is turned of? Power saving mode was 5h.
@gregory.maddra
@yazi.saradest
see linked posts above
