Topaz Video AI v3.0.0

Trim and crop are two different terms. If you are taking a 16:9 image and cutting the ends of the image off to achieve a 4:3 aspect image is commonly known as cropping.

I definitely agree! On a Mac Studio what I could do in an hour is now showing 8 days 15 hours to complete which I think makes this upgrade useless.

I have also found that use of interlaced video is only available at double original frame rate. There is no way to output video at its original frame rate!

Very, very disappointed with this upgrade and strongly considering asking for upgrade fee back. . . . So sad. . . . .

dione robust does not double the framerate

What does that mean?
In order to find out more about how VEAI works I tried to use version 2.6.4 with one video in parallel to running already 3 videos in version 3.0.0.
I’m very surprised that it functions without any problem. Off course processing speed of each video in 3.0.0 went down from 0.46sps to 0.56spf, while 2.6.4 processed at 0.67spf
Looking into Task-Manager I see that 2.6.4 does not utilize ffmpeg

2 Likes

Checked that. Artemis LQ, 480p h.264 to 1080p ProRes HQ 0.10 sec (2.6.4) to 4.7 sec (3.0.0.)

Nope they are still there.
TVAI Still Keeping TVAI Files

which gear ? which source ? which aspect ratio ? which computer ? which card ? which system ?

here, windows 11 insider preview, 1050ti, 32Gb Ram :

  • Source : 720x480 and 640x480 with ProRest HQ on V3.0.0.0.
    Output : 4/3 ! as it’s 4/3, i’m doing an output of a 1440x1080 NOT 1920x1080 ! (issue reported earlier in this thread yesterday about this)…

result : respectively 0.42 s/f and 0.43s/f with a 1050ti

  • Source : 624x352 16/9 → 1920x1080 Artmis Low Prores HQ : 0.95 f/s the result is double slower, it’s normal, the 624x352 is not a resolution good for VEAI to, and having a bigger speed with bigger resolution as 720x480 or 640x480 is normal.

i don’t have this issue here. can you tell exactly what you do, your setting, kind of course and output, models etc… tell me as well what you setup in preference (model, temp folder etc), I can try to see if i can reprodure here your situation !

Apple M1 Pro unbinned, 16GB RAM, well the aspect-ratio-issues seems to be it. It’s a 4:3 file. Now it is almost the same. But I’ll stick to 2.6.4 until the major bugs are ironed out.

…but still: other file .mkv h.264 1080p to 1080p, just cleanup with artemis low quality: half the speed from 2.6.4. to 3.0.0., both prores output.

the issue on apple M1 pro you’re talking about (not the 4/3 thing) is known i think. too many reports.

if my memory is correct, VEAI is programmed on an Apple M1 Pro, so let’s see if the next update will fix some of the issues :wink: .

Mike,
If you have the latest Nvidia Driver loaded with the GeForce Experience gaming add-on, if you press ā€œAltā€ and ā€œRā€ keys on your keyboard simultaneously, a small panel will open which shows you CPU and GPU work percentages. While it is not the most comprehensive display I’ve ever seen, it will provide you with fast information about whether your apps are making much use of your GPU or not.

Also, I don’t think GeForce Experience will make much impact on the performance of your system.

Trial and error. Just another term for debugging.
They say that doing exactly the same thing over and over again, expecting a different result is the definition of insanity. It is also called debugging.

5 Likes

I can understand if you edit the preset that is currently the default that you may need to retell the program to use it as the default, however every time i add a new preset or do anything with presets at all, the default present reverts to ā€˜none’. Why is that?

Revert to ā€œnoneā€ occur only when you restart VEAI. As long as you keep it open it keeps the preset you have chosen at start.

I hope this gets fixed, of course. In the meantime, would image file output be an option for you?

Topaz Video AI v3.0.0.7 & 3.0.0.8 Early Beta Release were the only versions that finished processing my video without crashing windows. Final Release v3.0.0 crashes
logsForSupport.tar.zip (4.6 KB)

Because they are supporting variable frame rates…MP4 containers don’t support VFR, MKV does. Besides, since they are now using ffmpeg exclusively for processing, support for mkv containers is almost free.

One of the most requested features was the ability to just take and input file and produce an output file that the user could put on their HTPC or Plex or Emby servers. None of these users want to mess with post processing or remuxing.

  1. Moving this slider does nothing. It always shows the same frame.
  2. This button does not do anything. What is it supposed to do?
1 Like
  1. slower a bit the speed of 1.

it works but it’s subtle as 1. is already not playing at the ā€œnormal 1x speedā€.

they must fix 1. first, so you can really see the difference with 2.
but if you look closely to the picture, you’ll see that it’s a bit more slower.