Last Time when i checked with 5.3.3 the Problem was still there.
Video AI 2.6.4 is slower yes ! But it has not the Problem, and it has much less problems with MPG1,2 and Vob Files.
They integrated Color Space selection and it works mostly.
But !
After 2.6.4 they changed how the Models them selves behave with the Color Red in General ! Red Tones are the hardest for Codecs, they know that.
Blocking, Ringing, Mosquito Noise, occurs much faster when Red Tones are in the Game ! Especialy with Codecs before h264 !
So i compared 2.6.4 (same Models, same Settings !) with 5.3.3
Input: Rec 601 File, i set 5.3.3 to Rec 601 Input.
The 5.3.3 Output looked (at the first glance) more like 709
and i was thinking “ah looks like Color Shift because of Rec 601 to 709”.
Then i opened the 5.3.3 Output, 2.6.4 Output and the Original Input Side by Side.
It was very confusing at first.
The Colors from 2.6.4 & 5.3.3 looked the same. but anything that was Red, was much different in 5.3.3 !
So 5.3.3 kept Rec 601, but it’s so agressive against Red Spots, that it looks just total different.
5.3.3 cleans up ““better”” with the same Model and Settings, but that’s because it’s way easier and faster, to just smear out Red !
Did anyone notice that in any Version of Video AI. Proteus will kill more Red Tones & Color Differences in General, if the “Revert Compression” is over around 45 ?
Yeah it looks then cleaner, but something is missing ! it looks bland, because the variation of Color degrades.
Did anyone notice, that Video AI is slower, if less filtering in Proteus is used and the Source has many Grain/Details/Noise ? That’s because more Data to process is left !
So, they were thinking. Ok most Problems like Blocking are at Red Spots, let’s kill the Red (preprocess Red Spots in a fast way, take out the Red) and smooth what is left on that Spot. It’s fast, looks cleaner, and use less Bandwith, which makes the process much faster !
So we can say, Video AI over 2.6.4 has greatly improved in Speed ! Yeah no Wonder, if Red is trashed, and way less Bandwith is required !
Video AI over 2.6.4 is absolute unusable for me because of the fact that it behaves like that.
I stick with the “slow” but “precious” (for the most part) 2.6.4 Version.
My PC:
Amd Ryzen 2 2700 8 Core, 16 Threads, 32 GB Ram DDR4 @ 3200mhz.
GeForce 3060 with 12GB Ram, PCI-E 3.0 (more as enough for Video AI), X370 Chipset, 2 x 1 TB SSD TLC. Monitor: Eizo with 10Bit Lut.
So my Hardware is not a Bottleneck, Video AI which is much faster if less Data is left, is the Problem.
They do that with the Red Tones since 3.x it’s possibly allready baked in the Models,
and not inside the Code from Video AI itself !
That would explain why Video Ai newer as 2.6.4 dont accept Model Files from 2.6.4 even if it’s the same Model Version ! (like Artemis Medium V12. It’s just the same by Name, but the newer ones got that agressive behavior against Red, backed in)
So because it’s allready backed in since at least 2 years, they cant go back, that easy.
That’s why they say “Oh it’s a FFMpeg Problem” " wrong Color Space is detected" then provide Color Space Setup for the Input (funny Fact, in 2.6.4 there is not such function, but for some reason, the Input Color Space was always detected right ! when i feed 2.6.4 with a yuv420 8 Bit Input) and nothing realy changes.
That’s why they say nothing anymore is this Thread, if people got still that Problem, and ask like you, if the Color Shift still happens.
That Less Data to process/see = more Speed happens in h264 & h265 Codecs too !
Use a CRF of 30 in x264, then use a CRF of 10.
CRF 30 is much faster, even if all other Settings are the same.
I see less = i can work faster !
by the way.
ProRes eats up Grain & Noise like crazy with the HQ 422 Profile ! So much Bandwith and it cant hold the Grain & Noise. So much to the claim that it is “Basically lossless” (yeah if the Input has no Grain ! and is under 1080p)
The 1080p Output is way less detailed, and much smoother (what was a little bit Blocky in the Preview Window, is totaly flat in the Output File) compared to what i see saw in the Preview !
H264 with CRF 0 has the same Speed, a acceptable amount of more Filesize, and the Output looks realy like in the Preview.
I dont know if this is a Problem is only in 2.6.4 (did not try 5.3.3, dont want use it because of the Red Tone Problem) but because of that Problem (that was never so extreme visible with SD & SD to 2x Content) i got to redo all my Projects again !
Which will take ages, because if i restore a Scene from a Adult Movies, one Scene got up to 300 Cut Parts (one Setting for one Scene never works ! Wasted Quality !) and 900 Files !
So Apple and People that claim ProRes is basically lossless, thanks for nothing !
F Apple ! H264 FTW !
