That's true, feos' script win ! :-P But the only strange thing I noticed is that the colors changed. We see this in the reds and greens. I don't knwo if it was itentional or not.
There is a slight color bleed which is intentional to make the pixel sizes consistent.Language: avisynthAVISource("movie.avi") PointResize(3408, 2928).LanczosResize(2880, 2160, taps=2) ConvertToYV24(matrix="Rec709", chromaresample="point") ConvertToYV12(matrix="Rec709", chromaresample="lanczos") # Notice the change in chromaresample
I use this codec because I had a problem of wrong color matrix when I used the Lagarith codec (because there is no tag for the color matrix) and then encode the video with Handbrake. I'm not a professional for encoding, it's why I use Handbrake. I think the result is really good ! :-)
For the Nnedi3, yes, I already tested it ! ;-) It gives excellent results, but gives sometimes some artefacts too :-/ But I like it too. What did you use to upscale to the final resolution ? Lanczos3 ?
I forgot to say that personnally, I prefer the "Spline36" algorithm rather than "Lanczos3" (I did lots of comparisons to be sure). The result is quite similar, but there is a bit less ringing ! ;-)
It could be the Svideo, I may try to capture it over just Composit and the flicker might not be there. Also many capture cards including mine, like the GCHD can do deinterlace on the fly which would probably make that go away. I should do some tests. So I could possibly do a passthrough mode, and just select "convert standard definition to 640x480" button. But my idea is to not pretty up the image aftwards with these captures, I sort of want to capture it as it, jank and all. Also I did capture some footage with the game mode "deflicker" option on, the test 4 one, and it was mitigated. I think of the retrotink2x as more of a "what is sent out is mostly what you get back" sort of deal. If the image was flickering since all it does is line double, you will get the flicker doubled as its coming through as well, since its so quick at what it does.
That's why games for consoles in interlaced mode usually render a full progressive image, and then present it for two fields, getting both the bottom and top. If you end up behind, you just show an old field again. There will be slight studder and slowdown as there always is with lag, but with none of the jumps or jerks from the above situation. So, the best way to deinterlace those is to simply recover the original progressive stream by looking at adjacent fields and seeing which ones line up.
Well like i said, melee is a VERY BAD EXAMPLE https://www.youtube.com/watch?v=Gl7Is-VgB8I here is a recent one i did of ff8 on the psone. No matter HOW you capture smash, unless your do it in progressive mode it will have flicker and that weird interlacing. It doesnt do this on anything else, the retrotink was merely outputting what it was getting in. Smash bros melee just sends out a janky signal, probably doing a sort of screen tearing/interlace interrupt to make it as fast as possible. Worst case scenerio really, I should capture other GC games to show that none of that is present on anything else it does. Trust me, its not a deinterlacing going wrong, its more of a what you see is what you get with this thing and what melee sounds out look just that weird even on a CRT over composit. Thats why it had a deflicker option in the menu of the game that helps with it. Its an engine thing.
Asol, is the aspect ratio different for Genesis consoles or is it just the same?
I've tested v1.1, v2.0 and v2.1 (and different bizhawk version)
Sorry, i was wrong. I have AMD graphic (with updated drivers and Catalyst). Anyway i've installed the correct prereqs, but after i saw it didn't work, i installed other prereqs too but nothing changed...
Obviously. And after i got error about runtime 2012 missing, i've installed runtime All in One and now i get the error i posted.
Ah, well, i still dont know what it mean lol But if deinterlacing is so useful, is possible to do with avisynth, and how? Anyway, if i can run hawk or can't, i installed everything necessary but keep giving me errors lol (sorry for OP). Somethings about sounds or what.
Is x264 8bit/10 bit the same as the regular x264vfw? OR is it different? What are the differences between the two?