I adjusted my settings to include your suggestions, but it increased the file size to 0.6 MB. I can't really tell if it means anything; the 200 frames segment is relatively low-motion. Thank you!
Aktan, do you remember? In good old days we were using mkvmerge option for youtube HD aspect ratio correction. Back then we were also using somewhat low resolutions for HD. Then we switched to avisynth resizing for aspect ratio correction. It was reported to yield sharper picture, but I don't exactly remember. Then we switched to x8 encode and ARC with a youtube tag. After the latter method died, we reverted to the avisynth ARC method, which required reducing our ambitions with the file sizes again. But what if we switch to mkv way again? It would let us send x8, with less file size, giving the benefits of the 2 methods. Will it look worse than x8 + yt tag ARC? Will it look as good as it does right now? I could do some tests (feos versus youtube v2), but kinda busy.
Or we could try working with the author in order to help us do our job with encodes. Jeez, if only I had MORE TIME. We're a constant source of new tests after all, and he seems somewhat active.
Aktan, what do you think of new kkapture versions? https://github.com/rygorous/kkapture/commits/master
Thank you. I messaged Fog and he helped me import the file (I believe it was an oversight on my behalf). The correct way to do so is to use FFVideoSource, for anyone else coming across this message.
Language: avisynthVersion()
Hi, I try to encode a movie, but when I launch my script with VirtualDub, he tells me : "variable 'LoadPlugin' not found" Does anyone knows how to fix this ?
So the larger the original footage, the more color bleeding there will be. Well, that's fair I guess. (I normally do 720p instead of 1080p, but GBx footage doesn't 2x scale to 720p)
So assuming you have a video in RGB to begin with, you resize with a factor of 2 using point size or nearest neighbor. The point of this is to double (or quadrouple, etc) each pixel both horizontally and vertically, making each 2x2 block contain four identical pixels. This means that when the chroma is compressed down to represent the 2x2 block, no data is discarded and then no blurring/blending occurs.
@Pokota Does it need to be only to the power of 2 or can I simply use any even number? I'm asking this because I work with 6x and 10x sometimes too.
Try doubling the resolution:Afaik only YV24 and RGB have pixel-perfect colors at native resolution.Language: AvisynthAVISource("video.avi") PointResize(Width * 2, Height * 2)
To add onto this, unless the later AviSynth version fixed this, the param "chromaresample" would be ignored if the source isn't already in YUV, so the real way is doing like this:Language: AvisynthConvertToYV12(chromaresample="point")
Last minor point is there are color conversion matrix for different resolutions. For native console resolutions, it is mostly BT.601.Language: AvisynthConvertToYV24(chromaresample="point") ConvertToYV12(chromaresample="point")
I was still having the same issue with Lagarith without null frames enabled.
I see. Switching to x264 solves that issue, but now I am getting sound desyncs. Pretty sure I still have everything set to default in my configurations. Is there anything I should change there that might fix it?
