Topaz Video AI 5.3.3

Hello everyone,

Today we are publishing a new update to Video AI, version 5.3.3.


5.3.3


Changelog:

  • Updated batch processing
    • Updated flow
      • If you dont change settings with multiple sources selected, batch processing will use each videos unique settings.
      • If you do change settings with multiple sources selected, batch processing will propagate the changes you made to every input video.
    • Fixed multiple resolutions and model settings applying across wrong videos.
  • Fixed batch processing resetting AI model.
  • Fixed timeline playhead centering issue when quickly playing and pausing.
  • Fixed bug where timeline is missing major tick.
  • Fixed timeline padding issue.
  • Fixed several issues with the hovertip of input items:
  • FPS in hovertip now will update with the change in input settings for image sequences.
  • Fixed precision for FPS field.
  • Added feature to recommend models based on input video height.
  • Enabled selection of recommended models automatically on turning on Enhancement filter.
  • Fixed - Last major tick now only visible if minor ticks follow.
  • Fixed issue where playhead will disappear when going out of bound of timeline view: now reappears at the beginning of the timeline or at the smallest timestamp it can reach without causing the timeline to go out of bounds.
  • Fixed AV1 appearing for some unsupported GPUs.
  • Fixed incorrect end trim marker when placed on the frame before last.
  • Removed autozoom of timeline on rendering a preview.
  • Modified ā€œReset timeline zoomā€ button functionality to match with the older versions.
  • Fixed bug where image sequence start frame number text field not working.
  • Updated End User License Agreement
10 Likes

Nice bug fix release Tony.

I’d still like to see the preferences menu item moved to Edit → Preferences instead of File → Preferences, to be consistent with every other Topaz app.

6 Likes

Thank you! Great product!

Very nice bug fix list ! I really enjoy the current flow, fixes, fixes and fixes
Great !

Sadly, I am sure that most of us are on alpha and beta for Hyperion and RXL experiences :sweat_smile:
Going ton install it, but not sure to play with it ^^

CONS : The first roll-zoom step in timeline remains completely insane, way to strong !
00:00:00 → 01:30:00 is zoomed into 00:00:00 → 00:16:00 :triumph:
x6 :rofl: step 1
x2 step 2
1.5 step 3
1.4 step 4
aso
You see the problem ???

Is there anyone happy with zoom-in zoom-out with roll on ?

I also would be very pleased to get benefit on my "Pro ā€œlicenseā€, because currently and since moving from 5.0.4 to 5.3.x, it is COMPLETELY impossible to do so. It crashes all the ways, whatever the model I use, whatever the resolution an so on …

  • The GPU load does not follow any logic. One GPU is constantly sleeping
  • The multi export kill after 10s the batch. If I run each 1mn after the other, i’v got some improvements.
  • The load is globally pure crap, CPUs is idling, GPUs are idling
  • Error is a dice roll: ā€œAI errorā€, ā€œErrorā€, ā€œResolution errorā€ … this is 576p dude …

NOTE : EVERYTHING was very fine with 5.0.4, so I start to be a bit fed up, but i’d like to get the benefit of the license and try models that are not outdated …

image

6 Likes

Anyone have a link to the new EULA?

1 Like

Hi Topazlabs team, is there any new models or new versions are upcoming?

4 Likes

Updating models have been so far off there radar for a year now it is beyond ridiculous

IMO top 3 things that need to be focused on for the next 18 to 24 months

1 Model updates should #1 by a good amount

  1. Optimizations

  2. Bug fixes

UI should ever get updated UI for like the last 2 or 4 versions of 4 and the first 2 version of 5 should be the UI they roll with for the next 2 1/2 years

Topaz Video AI looks like they want it to be more of a video editor with only 1/3 of the program for Upscaling

10 Likes

Hello.

I’m sure that many users (and potential future users) agrees with your 1 - 3 impressions.

But, from my observation, since late '23, Topaz has deployed a couple model refreshes (mediocre, IMO, but they still count for Topaz to state ā€œwe’ve released new updates/models in 2024ā€ :smirk: - Proteus4 ~1/24, ect.)

I think these floods of GUI revisions from Topaz recently speaks other volumes, though (and its future media player places a cherry on top of my plight) which is, IMO, Topaz could be aiming at a sort of media center / hub (and not so much leaning on just another video editor).

Also, IMO, it seems like Topaz has reached its final product layout for TVAi for full streamline and with just the bare minimum here and there minor perks (features) to justify their annual sub. models with the so-called promising of ā€œexciting new featuresā€ awaits down the pipeline :smirk:.

2 Likes

I use an older version. Is it now possible to set multiple edit points in the timeline? Or is only one in- and out-point possible?

Every bug fix is welcome.
So, thanks!!!..

Hopefully the bug which forces me to use MKVtoolnix and fix the PAR will be squashed soon as well.

1 Like

ProPres import into Adobe products still doesn’t work. I’m frankly shocked this isn’t a higher priority bug as ProRes is a common intermediate format amongst professionals.

Does anyone have a problem, after converting several videos at 120fps, when I merge them in say, QT or IMovie, they render in slow motion only?

Please note… If you download this, and currently have 5.3.1 or earlier, you are subjecting your self to an EULA (contract) that you may not wish to enter. Read it carefully, and check with your lawyer if you have one.

It seems to give Topaz the right to change the rules anytime, and to use your name or logo in their publicity, and the only way you can get out is by deleting and no longer using the software. I’ll be sticking with 5.3.1, unless this is fixed.

5 Likes

What version of the adobe products are you using and what ProRes settings for your export?

Trying to replicate now but so far my tests have all imported without issue in to Premiere Pro v24.6.1

I’m on a Mac Studio (M2 Ultra) macOS 14.6.1. I tried all permutations of ProRes settings into Premiere, After Effects, and Media Encoder. The error is: ā€˜The source compression type’ is not supported.

Thanks for looking into this.

1 Like

Tried to upscale interlaced vob, i’ve cropped it get error

upd: fixed

That’s because, as far as I can see from Apple’s ProRes license buyer pages, Topaz does not have an official license for ProRes. Apple requires - and monitors very strictly - that a license holder who implements a ProRes ENCODER delivers a 100% compatible version. Decoding is free…

Topaz cheapskates with a homemade FFMPEG encoder version so don’t blame Adobe…

Hello.

To be fair here, Apple has this super iron-grip on many 3rd-party applications (which is costing Apple big time in forced turnarounds in courts today), though.

Many believe (on purpose) Apple STILL prefer its iDevice owners to use its software for ALL their workloads, even inference workloads that Apple is still poorly performing at the moment. :smirk:

Sorry, but that has nothing to do with this. As a filmmaker, I am particularly happy with Apple’s strict requirements. With a ProRes video file from a licensed camera manufacturer or software developer, I know exactly what specifications it has and that that video file can be decoded and used without any problems with almost ANY software.

An H264, 265 HEIF etc file can be anything, 8 or 10 bit, 0.5 or 400 MB/sec, interlaced, GOP, intraframed, hardware encoded on the fly or with expert knowledge very precisely with expensive software. Camera-specific software from Canon, Blackmagic, Nikon, Arri, Topaz generated ProRes: one software package has no problems, while another doesn’t understand it at all.

So please let Apple keep that iron, indispensable grip on ProRes and that not all kinds of software developers put their own neat tricks, accelerators, ā€˜better’ specifications and other ā€˜improvements’ into ProRes…

2 Likes

As a filmmaker

That does not warrant you being correct, sadly. As the courts are proven it as we converse. :smirk: