Unfortunately, it’s broken. Tried to trim just the width of a 720x480 SD to 2824x2160 4K, but it squishes the height to 1882, leaving thick black bars on the top and bottom.
i tried what you told, what is your source ? a 4:3 file ? i don’t have the 1882 issue you tell.
here is a 4:3 DVD rip → MakeMkv → De-interlaced with GTQMC → VEAI 3.0 → Cropped to remove some unfortunate Pal lines → Widht + Height set to 2824x2160 4K + Proteus Auto =
Interesting. I guess I need to experiment with the settings a little more.
i learned often that sometimes, Veai or any other software handle bad some files. bad conversion, source, format etc.
you can easily replace bad by “not accurate” ; “not compatible with”, “not yet able to handle the format” etc … instead of forcing it to accept any files, i think there is a better approach.
VEAI is a kind of Gui for an open source software called ffmpeg, and where the model Ai are used as kind of “plugins”. 3 different things working together.
example with Vegas Pro of such issue : during many years, i was working with vegas pro with all kind of file, CBR, VBR, different Framerate etc and didn’t care of the source format.
it was crashing ALL the time, 10, 15 crash per hour. A Nightmare.
the software is known for that. it could almost be called Vegas Crash Pro ! With time, the dev team reduced the number of crash but… they were still a lot of them.
with time, I noticed that the software can handle different bitrate only at a certain point.
that working with intel iGpu than Nvidia card was more stable. the rendering is slower, but slower is better than crashing all the time!!
The preview is still Awfully slow, never been fixed.
I can assure you that the devs behind VEAI are much more listening to their users that the one behind other company.
how to reduce vegas pro crash ? stopping mix of different framerate… that’s how VEAI help me to work in vegas pro and make it crashing less.
sure, someone else could tell “DaVinci handle all this without a single issue”, but i don’t care about how other software work. I like to work with some software than others for different reasons, crash included 
2 Likes
Trim is cutting something off. It is also known as cropping. You are talking about resizing or rescaling the image…
I love the new interface, and the performance is nothing short of amazing. I do have one question. I set it up to do a project last night, figuring it would take most of the night. I was pleasantly surprised by how fast it was. But now I see a second process going on even though I didn’t have two processes set. The first one seems to be complete showing a .mov, the second, which is still going, showed a .tvai format, and now it is showing .tvai.mov and still going. I did an enhancement, and the output box shows a green check mark. So what is this second process going on?
Handbrake.
So when I am applying Proteus manually, and testing by preview and I decide I need further tweaking of the settings, it opens a new output, and I need to close the video on the previous output. Is that the way it is supposed to work, or am I doing something wrong?
What do you mean?
I think you’re supposed to be able to just click on the completed previews in the list and view them. That way you can compare them somewhat quickly.
You keep spelling it Handbreak. It’s Handbrake.
3 Likes
Look at everything else!
What Screen Shot you look at?
I see no difference…
so of course, we can see that the image is compressed with artemis low! we can see that the edges are smooth, and there is a loss of detail anyway…
I use vegas pro too, and I confirm, the preview is slow when it starts to have effects, the technique consists in selecting a small area of a few seconds and doing “shift+b”, it will make a pre-render to read the segment without lag 
1 Like
It is hard to look at any details, when images uploaded to this forum are showing compression artifacts.
I’m curious what is up with the odd input frame rate of 28.444?
What is causing that?
Your screenshots are terrible. We don’t need to see your entire desktop. Can you not maximize Video AI and then capture the entire screen?
And most of the time nobody here has any clue what you are trying to point out about the images.
6 Likes
In the end I think that I found a good compromise for my settings in Proteus:
Set “Parameters” to “Manual” and sampled “Estimate” at about 10 to 15 different frames across the whole Video. This confirmed me that Parameters vary a lot thru the whole video (off course that’s a nobrainer), and in consequence one single set would not perform best for all frames. Therefore I concluded to set “Parameters” to “Relative to Auto” and adjusted the individual setting carefully a little bit (according the results found by “Estimate”) . For the moment that’s the best compromise for upscaling my TV-Mediathek videos.
This is called Variable framerate. Very few videos does a real Constant frame rate. VEAI certainly display the real framerate. so you can see a 30.371 to 28.88 instead of 29.97 etc…
ii’s displayed in mediainfo. video are variable or constant birate. information is written in it on the full details page.
For example every video with a constant bitrate remised in Avidemux is converted to variable bitrate. the bitrate does not usually go above or below 1 fps of variable.
