And that is seriously a deal breaker for me, and I am sure many others. What were the developers thinking?
The above is the definition of the phrase âdeal breakerâ 
2 Likes
Issues and Feedback
ffmpeg command line generation still has some issues.
- Itâs quoting things that donât need to be quoted.
- âvsync 0 is depreciated (I also am pretty sure it doesnât do anything)
Add grain is much weaker than in 2.x.
Maybe allow settings higher than 20?
I find this to be useful when upscaling, after removing noise since it allows me to put the film grain the denoise process removed back in. But in 3.x itâs too weak.
Model Download Messaging
Currently there is no messaging when running command line if ffmpeg is downloading a model. There should at least be a â flag that enables this (maybe --showmodeldownload 0|1 or just have it tied with --nostat). Otherwise it looks like ffmpeg has frozen up.
GUI: Model Management
Please bring back the model management/download/removal.
Profile Names
Please allow punctuation again, I usually use version numbers with profiles as I check after an âexportâ is finished. Right now Iâm workaround it this by just doing v10, v11, v20 but it looks stupid.
Profiles Are Incomplete
Profiles arenât saving some things like cropping.
Metadata
The metadata being added to encoded video is useful but a few things.
- The naming of models and options in the metadata does not match what the GUI uses. It should be consistent.
- For resolution changes, right now it just shows the target resolution. It should be something like Resolution changed from XxY to X2xY2 or Resolution changed X1xY1->X2xY2.
- It might also be useful to have additional metadata fields, like have one thatâs VAI_MODEL (showing the friendly name of the model used and itâs version).
5 Likes
[quote=âthompsonl, post:50, topic:36338â]
Model Download Messaging
Currently there is no messaging when running command line if ffmpeg is downloading a model. There should at least be a â flag that enables this (maybe --showmodeldownload 0|1 or just have it tied with --nostat). Otherwise it looks like ffmpeg has frozen up.
[/quote] @gregory.maddra @ida.topazlabs @yazi.saradest
Lee,
I think this is an issue that needs more discussion. The GUI must have some capability to monitor the behavior of the FFmpeg processes it launches. (And often loses track of, causing GUI hangs.)
I must explain that I do not have a lot of experience with FFmpeg monitoring, probably due to the fact that I rarely try to run the jobs manually. (IMO, thatâs what the GUI is for.)
Perhaps there should be an explicitly separate process that lives between the GUI and FFmpeg that manages and monitors FFmpeg sessions and feeds back their status. - That functionality would be extremely useful (and informative) from both the command line and GUI perspectives.
For lack of a better name, I will call this the FFmpeg Queue Manager, or FFQ. (Something like this may already implicitly exist in the VEAI environment, but if so, I donât know its name.)
In any case having this functionality as a discrete program that could be used to initiate and maintain communication (and status) with all running FFmpeg sessions could be very useful. - And it would not only resolve your messaging from command line sessions, but may also add some stability to the GUI, too.
Bottom line: Does an FFQ sound like a good idea? Or does something like it already exist?
Would anyone care to clarify or discuss this? OR should this become a side discussion?
3 Likes
Only the second time I have tried the stabilization with the same result I got previously with a beta release.
Input is from a Canon 5D3. 1280x720 50fps.
I have not asked TVAI to do anything other than Stabilization with default settings. The output sure is stable but a grid of pinkish boxes was not the stable output I was hoping for.
I just tried another preview, this time selecting âAuto cropâ. TVAI started working on it, then TVAI was gone, crashed, vanished. No error messages, just gone.
2022-11-03 02-32-10 Thread: 25428 Debug passProcDone 1 3 3 0 0
2022-11-03 02-32-10 Thread: 25428 Info Open videoPath âC:/Users/john/AppData/Local/Temp/337593105/previews/073A1675_46712365_stab.movâ 0x6354
2022-11-03 02-32-10 Thread: 25428 Info Removing video âC:/Users/john/AppData/Local/Temp/337593105/temp/_tvai_45367559/%06d.tiffâ 2
2022-11-03 02-32-10 Thread: 4952 Debug Open Called âC:/Users/john/AppData/Local/Temp/337593105/previews/073A1675_46712365_stab.movâ 0x1358
2022-11-03 02-32-10 Thread: 4952 Debug Open Called for file âC:/Users/john/AppData/Local/Temp/337593105/previews/073A1675_46712365_stab.movâ -1
2022-11-03 02-32-10 Thread: 25428 Info Close and delete path âC:/Users/john/AppData/Local/Temp/337593105/temp/_tvai_45367559/%06d.tiffâ
2022-11-03 02-32-10 Thread: 25428 Debug 8
2022-11-03 02-32-10 Thread: 25428 Debug 9
2022-11-03 02-32-10 Thread: 4952 Critical Unable to find video stream information in file âC:/Users/john/AppData/Local/Temp/337593105/previews/073A1675_46712365_stab.movâ
2022-11-03 02-32-10 Thread: 25428 Debug Updating video info {âsarâ:1,âframerateâ:50,âstartNumberâ:1,âframesâ:500,âprogressâ:100,âstatusâ:5,âframeâ:0,âprocStatusâ:{âstatusâ:5,âetaâ:48.468,âfpsâ:0,âmessageâ:ââ,âpassâ:2,âerrorâ:ââ,âprogressâ:100,âframeâ:0,âpriorityâ:3,ârequestPosâ:1,âprocessorIndexâ:-1}}
2022-11-03 02-32-10 Thread: 4952 Critical Unable to open file at âC:/Users/john/AppData/Local/Temp/337593105/previews/073A1675_46712365_stab.movâ
2022-11-03 02-32-10 Thread: 25428 Info Removing video âC:/Users/john/AppData/Local/Temp/337593105/temp/_tvai_45367559/%06d.tiffâ 3
2022-11-03 02-32-10 Thread: 4952 Debug Open Called for file âC:/Users/john/AppData/Local/Temp/337593105/previews/073A1675_46712365_stab.movâ -1
2022-11-03 02-32-10 Thread: 25428 Info Close and delete path âC:/Users/john/AppData/Local/Temp/337593105/temp/_tvai_45367559/%06d.tiffâ
2022-11-03 02-32-10 Thread: 25428 Info EXITED: 3 0 0
2022-11-03 02-32-10 Thread: 25428 Info ~TProcess(): destroyed
2022-11-03 02-32-10 Thread: 25428 Warning input video opened FAILED: ââ
Intel(R) Coreâą i7-10700K CPU @ 3.80GHz 3.79 GHz
Installed RAM 64.0 GB
System type 64-bit operating system, x64-based processor
Edition Windows 10 Pro Version 21H1
OS build 19043.2130
IntelÂź UHD Graphics 630 Driver Version 31.0.101.2114
3 Likes
Thank you so much for the response. This is the type of information we the user need to make the best decision for our use cases.
Did you see a quality increase with the encoder also or just speed. I prefer software encoding over the speed of the NVenc encoder because of the quality difference. And donât get started on how bad AMD RX 6600 is for encoding. My NVidia Turing and even my Pascal card seems better then 6600.
Ok this actually works! Thank you for making me aware of it, I had no idea there are these options hidden in the menu
1 Like
Trim is broken since latest bugfix it marks trim at the start point and then thatâs it. Canât see any of the video after start point, so pointless as you canât set an end point. Have to reinstall 2.64 it was much better and had more control, I genuinely hate the new setup I find it so dumbed down itâs much worse than 2.64. Wish I did not choose to update to 3.0.
Completely agree with everything you said and will do the same.
Stabilization does not work normally! Squares, as before. Drivers of the latest version, at first they are not there, then after 2-3 minutes they appear, and then constantly.
Win 10, 32 Gig DDR4, RTX 3060Ti, R9 5900X, Latest Nvidia Game drivers
1 Like
When reading: FAQ for TVAI 3.0 Frequently Asked Questions for Topaz Video AI v3.0 - Topaz Labs
chapter âWhat is the difference between Video Enhance AI (VEAI) & Topaz Video AI (TVAI)?â
"⊠Most of the issues stemmed from the fact video was being treated as a series of constant-rate images. All the current models operate on this assumption and as a result, had issues processing videos with variable frame rates, repeated frames, scene changes, etc. This was hampering the development of new models and processes that require multiple passes, like stabilization, scene detection, etc. To address these concerns and allow the addition of new features, we decided to rewrite the code base.
This approach allows us to focus on our core expertise to create and improve our models to perform better on all user videos. âŠ"
That explains essentially why the âoldâ 2.6 AI models need to be âretrainedâ. I still hope that this will be done timely.
1 Like
This is like some of the blurry screens I got when I tried Stabilization. I am also doing stabilization by itself. It worked great on a small 2 minute file, but not on the larger ~23 minute file I tried. I think it might also be important to list your system environments in case that might be related.
Win 10/64 Pro, 32 Gig DDR4, RTX 3080Ti, I7 12,700k, Latest Nvidia Game drivers
1 Like
@ida.topazlabs
Please excuse my rudeness as I do not speak English and this is my first time posting here. I have been using your software since the previous version, and I would like to write a few things that I would like you to fix.
I basically output videos with the following settings, but I have the following problems.
[Imgur: The magic of the Internet]
ă»When I output trimmed videos, the chapter information is not deleted, which causes problems during playback.
ă»When I playback enhanced videos on my PC, they do not play at maximum size even if I set them to full screen.
ă»Sound is out of sync (sound is about 0.3 seconds early).
The above two issues did not occur in the previous 2.x version.
Thank you in advance.
Is there any chance we can get Constant Rate Factor back as a GUI option?
2 Likes
I can confirm that the sound layer sometimes begins between 0,3 and 0,6 seconds to early. not only this. when trimming the video sometimes the first 0,3 - 0,6 sec of the trim start is a repeating of the end of the video layer before the trim so if you move the sound layer back later it overlaps with the sound layer of the region before the trim start. this leads me to the question if at the end of the video or trim are 0,3 - 0,6 sec of the sound layer is missing. 
2022 is the most unsuccessful year for topaz
6 Likes
This might have something to do with the fact that ffmpeg only wants to cut at key frames. I donât know what that means professionally, but in my usage of ffmpeg as my only tool for cutting videos into parts, if I tell it to cut at 00:03:00.000, the sound will often have a length of like 00:03:00.300, but the frames cut right when I told it to.
If I join the two clips back, I need the extra blank frames or the sound becomes off by those .3 seconds.
Appending clips with MKVToolNix delays the playback of the second clip until the sound finishes playing, so the sound stays in sync. If I take all the frames from clip two and renumber them to become a continuation of clip one then convert them into a movie, the sound becomes off at the point where clip one ends.
Maybe this is something not accounted for in TVAI.
yes, I also noticed that sometimes the gui itself is not able to cut exactly often changing my input time to something slightly different.
I definitely agree. I used to use it a lot. previously. And I believe that they will reintroduce it eventually.
In the meantime, I suggest the nearest thing to lossless video currently on the menu. That is ProRes 422 HQ.
It is also a good idea to use if you plan to run the same video though process more than one time.
2 Likes
@gregory.maddra I can not find Main10 and 10bit encoding in H265 Main10 VEAI files.Using MediaInfo to Read.
