Topaz Video AI 3.0.0.10.b

Your problem is here:

MSI (c) (BC:EC) [14:18:11:445]: Note: 1: 1719
Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
MSI (c) (BC:EC) [14:18:14:171]: Product: Topaz Video AI BETA – Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

At an elevated command prompt run the following:

SFC /scannow
Whether this finds and fixes anything or not, then run the next command

DISM /Online /Cleanup-Image /RestoreHealth
This one might take some time if it finds anything to fix.

When both are done, restart. Test your install again.

The timestamp is after the installer has been terminated via task manager. I’m happy to try the commands though.

Why is task manager stopping the installer?

The installer hangs, doesn’t progress and can only be terminated via task manager. I have run the commands, no change as expected. Thank you for the suggestion.

Maybe this is more of a 3.1 feature request? But would be very cool if we could mark time stamps for when to begin and end each filter. For example in a 1 minute video, do Apollo for the seconds 20-40 (lets say there is high motion then), but go ahead and just use frame doubling outside of that, until seconds 50-60 do it again. And use proteus during the whole things, and stabalize the camera only during seconds 0-5 and 40-50.

Currently we would have to cut up the video manually and do each combination as needed.

Also not sure if this is possible, but if all our settings could be placed into the metadata of the output video (toggle check box) file, in a way that can be human readable later or extracted to be reused that way, that would be cool!

@gregory.maddra @suraj Just my personal feedback, I prefer the old icon for Topaz Video AI better than this new icon. The last icon felt high quality, like I have nice piece of software, this new icon doesn’t come across this way. It looks horrible in my opinion. Here is a screenshot below to compare them side by side, the last one looked like a piece of artwork this one looks like it’s a placeholder for an actual design to take its place. You can even see it’s choppy too with its jagged edges compared to the old icon. It’s a major eye sore compared to what it was.
image

6 Likes

They’ve been changing to the arrows for all the Topaz products. I agree, they look very generic and don’t “say” anything about the product.

2 Likes

I mean with everything running so smoothly…why not kill time redesigning icons right.

But in their defense i’ve seen that shield used on many other products, must come in a build your own icon starter pack or something. That black diamond looking one used on Photo a few builds back was probably the best so far.

2 Likes

Installation without any problem, processing with preset “Progressive Enhance 4x Upscale” works fine (5.74 fps). I’ve nothing to complain up to now.

Converting from 25fps to 50fps a 4K H264 video takes 5x longer with V3.0.0.10b than V2.6.4
On a M1 Mac Mac Studio with 32GB RAM and 32 GPU cores.
(RAM usage is set to 100%, Chronos Fast for V3, Chronos V3 for V2))

Edi:, Chronos and Apollo on TVAI 3 are 3 times faster than Chronos Fast, so only 1.5x slower than Chronos Fast TVAI V2.

So it looks like Chronos Fast is the one with issues on TVAI 3 at the moment.
Really looking forward for the speed “optimisations”!

I am using a translator.

I want to choose what to do after all the processing is done.

Do nothing."
End of program.
Sleep.
Shut down the computer, etc.

  1. Lost option to de-interlace and enhance the video now it needs two steps, like 2.64, big loss for myself.
  2. Still no way to move in and out markers with keyboard, when in trim mode, have to use mouse.
  3. Lost option to use ALL GPU, I now get an error. Early version of beta would hit 9FPS while using dual GPU.

-vsync is deprecated. Use -fps_mode
Passing a number to -vsync is deprecated, use a string argument as described in the manual.
Switching to NI mode, due to poor interleaving
Invalid value 5 for device, device should be in the following list:
Failed to configure output pad on Parsed_veai_up_1
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument

Error while processing the decoded data for stream #0:0

Qavg: 178.271

2 frames left in the queue on closing
This is a few steps backwards.

  1. In the future we will allow having multiple enhance filter chained together, so that will allow deinterlace to be chained with other filters. Currently we want to keep the resource utilization in check mostly for lower end machines.
  2. You should be able to trim with the edit menu without entering trim editor, Shift+[(start trim position), Shift+](end trim position) and Shift+/(reset trim)
  3. Can you post the logs for the ALL GPU issue.
    Also logs for the below error.
2 Likes

Can I get the logs, I work on a M1 Max machine myself and haven’t seen any performance differences.

May be in the future once the core functionality is working as expected.

1 Like

The export now happens in 2 passes. The first pass writes to the preview directory with the required flags to show the output in app and also keep the processed results if there is a crash. The second pass just strips the extra flags and copies the processed file to the output location so the results can be opened in external editors and players without issue. After the second pass the intermediate file is deleted.

Doing this frees up the second encoder on GPUs allowing users to process multiple videos without processing failures while using GPU encoding.

2 Likes

Thank you for highlighting this. Only the corrected slash entries are used. Will verify and clean it up if not already.
The uninstaller currently doesn’t clean up the registry and so entries might remain in early users machine.

4 Likes

There will be a new logo when we release.
The only reason to use a place holder fast forward logo was to allow users to distinguish between VEAI 2.6.4 logo and 3.0 EA.

3 Likes

@gregory.maddra can you work @robin.koehler to figure out and resolve the installer issues.

1 Like

Why would it not clean up the registry, and will that be fixed?