Video AI 3.0.0.0.b

Hello Everyone,

The long wait for 3.0 is almost over. In the past few months we have taken the time to rewrite the Video Enhance AI app from scratch. This is just the first beta and not all features are in yet. If you are missing something please let us know.

Thank you everyone for all the testing.

Downloads
Windows | Mac
Headers, Libs, Dylibs, etc.

Changes from 2.6.4

  • Completely new app from the ground up
  • New Apollo model to handle motion blur better
  • Full frame stabilization
  • Models can be chained now
  • Support for various output formats
  • Command line support
  • Parallel execution support
  • Ability to keep previews
  • Color depth upto 16bit now supported
  • Video files are playable on crashing (recovery coming soon)
  • Colorspace and color inconsistency issues reduced significantly
  • Many many more things

Changes from Alpha 3.0.0.40a

  • GUI should be much more responsive
  • Apollo is faster on Mac
  • Apollo returns expected number of frames
  • Sliders now allow typing in the value
  • Source list can be expanded for making video selection easier
  • FPS default list should be accurate now
  • Preview playback issues should be fixed
  • Other misc bug fixes

Known Issues

  • Apollo does not work on CPU and on Mac OS Catalina
  • Apollo sometimes doesn’t work on AUTO AI Processor on windows
  • Sometimes video open with marker at last frame
  • Preview/export listing might show inconsistent information
  • Preview is not immediate
  • Multiple select for input videos is missing
  • Certain VOB files do not open correctly

Please upload videos that are not working to this DropBox folder.

14 Likes

Ah, I didn’t do enough digging when I was invited here to see about any earlier betas. Sorry I am late to the party, but I’ll give it a wack on Windows and Mac.

2 Likes

Thought I’d bring this up now since it’s still early times. I hope there are plans to implement logic for aspect ratio handling that lets you change the resolution of a non-widescreen source clip to a standard widescreen res. such as 4k (and vice versa) but maintain the AR and get the required black padding.

In VEAI 2.x if the source was not widescreen but your selected output resolution was, the application would correctly encode black bars on the sides to pad the video. The GUI would even show where the bars would be. Right now v3 doesn’t seem to have any logic for handling this. The useful ā€˜crop to fill frame’ option is also currently MIA.

Using a standard build of ffmpeg I can get the desired results using:

-vf scale=3840:2160:force_original_aspect_ratio=decrease,pad=3840:2160:(ow-iw)/2:(oh-ih)/2,setsar=1

Not sure if this is currently possible with the VEAI ffmpeg.

Thanks

3 Likes

Using Apollo with 100% (no slow mo) will still clear away motion blur? I want to remove motion blur without changing playback speed. This is for video where the motion in the video is too fast for the frame rate it was recorded at. I was a bit confused when I saw mentioned using 200%, 400% or 800% is better? Or Can I just use 100% but then change the output frame rate to be 2x, or 4x the original?

I guess what I am asking is if I have a 30fps video with motion blurring, where I want the same playback speed (so if it is 10 seconds long, it still takes 10 seconds to play), but I want to reduce the motion blurring as much as possible. The best setting will be to use Apollo 100% and set FPS to whatever my monitor is (60), or is leaving it at 30 or going to 120 beneficial at all for the model? Or will it be better to use Apollo 200% and then change the playback speed outside of VEAI or something to get it back to the original speed?

1 Like

When I try to log in to the beta I see this:

I’m on MacOS 12.4 on an M1.

I’ve been using the alphas – I just downloaded the .dmg and ran it from my applications directory.

I can also close that warning and then start using the app – only it simply fails silently and doesn’t actually run any previews or export anything. It just looks like it’s waiting forever.

Expected

  • not to receive the error (i.e. auto fix the models directory path) OR prompt me to fix it / navigate to it
  • not allow closing that error so I can’t proceed to the app OR have the app also say it can’t load models and prevent me from running a preview or export
4 Likes

First off, Love the new UI - amazing !

Macbook Pro M1 12.4 - 8GB ram - I have a 2060 coming today for the old Intel Macbook Pro so will test

  1. Timming clips will make End Users fustrated, should be in = in o=out, clicking on the curly brackets was a step curve (may be too early in the mornig)
  2. New export options - thank you
  3. Crop feature is good but the output format doesnt match up DAR example 768x576 letterbox - used crop to upscale to 1280x720, X:20 Y:90 H:720 W:400 getting 1280x728 and 10 lines blanking left and right uploaded to DB
  4. Command Line !!! amazing thank you

thank you for getting this app updated

2 Likes

Giving full disk access to VEAI worked for me

2 Likes

THANK YOU SO MUCH FOR THIS AMAZING UPDATE OVERALL AND SPECIFICALLY FOR SUPPORT FOR PRO RES 4444XQ.

I feel like I’m finally getting my moneys worth from the product, like it’s finally, truly living up to the promise of what Video Enhance AI is and what it’s capable of. UI is infinitely better, render times appear to have drastically decreased on my 16’ M1 Max with 64gb RAM and it just runs overall so much smoother than before.

After it’s out of beta and has some additional polish + being able to better max out CPU/GPU and RAM capabilities (currently only using 20% or so and 8 gigs RAM for 8k upscale, even with Max memory usage set to 1.00, battery saving turned off, max processes set to 3, app in the foreground and energy mode set to High Power). Anyways, after those finishing touches, I’m completely fine with the annual license renewal fee and you guys charging much more for the initial license purchase.

You guys have truly built something amazing and worth being proud of. Congratulation to everyone involved, ya’ll took your time to do things right and achieved results nothing short of spectacular. It was more than worth the wait.

3 Likes

it does seem like with Apollo, changing the ā€œslow playback speedā€ setting effects the processing since the file size changes… but I would like to remove motion blur while keeping the same final playback speed…

1 Like

seems like using slow playback causes the video to play slow and the audio to play at normal speed in the final product.

1 Like

Previews are still pretty awkward compared to the old UI.
When rendering out a movie it says ā€œwaiting for previewā€ and I can’t find out how to make it show the preview.
It wants me to wait until the video is 100% done, and that’s not good when rendering out an entire movie.
ā€œPlease wait for the status to reach 100%ā€
EDIT - Saw that this is an issue reported in the main description of the beta. sorry

2 Likes

I would suggest that you make it more obvious that lanczos is used for resizing if enhance is not enabled.

5 Likes

I have reported problems with color space handling in the past, but they have not been fixed yet.
I hope this will be fixed as soon as possible, as it is simply a matter of changing the options set in ffmpeg to the appropriate ones.
Even if you have other priorities, it is not a good idea to leave a color space problem that degrades image quality in an application that is intended to improve image quality.
https://community.topazlabs.com/t/video-ai-3-0-0-34a/32848/151

2 Likes

Please make it so that the ffmpeg command line+arguments for the currently selected filter settings can be viewed/copied without having to start the export process.

Thanks

1 Like

@suraj Got a ā€œProcessing failedā€ when trying to play with a video.
From the error window, it looks to be… a silly folder/filename issue.

Here is the error:

No such filter: ā€˜ls grs ds_VF fe_48 (61) - Égie du vt’

Error reinitializing filters!

Failed to inject frame into filter network: Invalid argument

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

The original path is: ~/Desktop/Oy, ls grs ds/VF fe/48 (61) - Ɖgie du vt, Ć©gie de l’u.mp4

It looks like the comas are the ones that make the process fail.

Further investigation shows that this issue only occurs when the Stabilization feature is enabled. It also occurred in alpha 0.40.

@suraj Other issue : when I drag the video position cursor to move in the video to find a particular moment, I click on the cursor, move the mouse slowly to the right until I find that moment, then release the mouse button. But the cursor is sill moving forward like if I was sill pushing the mouse button while scrolling to the right!
Said differently, the UI didn’t catch that I released the mouse button and stopped moving the mouse.

Tested with Alpha 0.40: I could not reproduce the issue with the latest Alpha version, but the UI was much lest responsive than the first beta.

PS: @suraj, did you get my PM?

1 Like

Pretty useless update when it takes almost 30 minutes to render a preview! Running at 0.3fps…

1 Like

Not a good update honestly. Processing is slower than ever (Dione TV was 7fps in the last update, now it’s 3fps). Sliding with your mouse through the video has a huuuuggeee delay, and it’s really annoying. My cursor is at the end of the video, and the video preview screen is just fast-forwarding to get to it. The ā€œadd grainā€ option isn’t there as well. Preview is worthless.

3 Likes

Hi, i’m agree with you, the encoding is very slow, not fast, it’s a very bad update. Why the grain option isn’t there? Where’s the hdr option too? Nothing good update sorry. Always error for audio with copy option… Never again new models, always same models… Or never models updates… I’m very sad

2 Likes