What are you sending to YouTube? Might be a codec or a parameter to that codec that it doesn't like.
Edit: fsvgm777 pointed out to me that you included MediaInfo in the description. I'll take a look and edit this comment.
Are you sure you're not mixing DAR with PAR? Your link here says that the NES/SNES has a PAR of 8:7, which should be a DAR of 4:3 on a standard CRT TV.
Whoa, that's a lot of testing. Nice to see you're super curious in what's the best. Here are some select comments:
I thought the current script would be point resize to the target resolution or bigger in multiples of 2, then downscale to the target resolution if needed. For example:
Language: avisynth
AVISource("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
There is a slight color bleed which is intentional to make the pixel sizes consistent.
Yes, Lagarith YV12 is probably using Rec601 color matrix, but since you already know how to use Avisynth, why not capture in RGB and convert it yourself as a last step, then send to Handbrake?
What he did was upscale it above the target resolution, then downscaled to the target resolution with AreaResize. AreaResize uses weighted averages to figure out the end result.
This is why I personally use Lanczos with 2 taps instead of 3. Less ringing but more blurry.
Welcome to the forums SuperLumberjack! I'm happy to see more people in search of the best image quality. Regarding your last post, the reason why we use YV12 is because we rather control how we get to YV12 instead of letting YouTube do it. Basically, the conversion to YV12 is the last step and we would like to control how the color information is thrown out. I hope this makes sense.
Now, as to the matter on how to display retro games on a modern display, as you already stated, that is highly subjective. Without going way too off subject, I'm a fan this type of up-scaling for older games:
https://www.youtube.com/watch?v=axDY3OBjxzA
Here is another example on NES:
https://www.youtube.com/watch?v=KkP7EscUrl4
This uses the very processor intensive method of nnedi3 up-scaling.
Going back to the technical aspect of the perfect AR correction, I must admit I'm not sure how good our method is. I've not had the chance to read through the links, but they do sound interesting.
In general hardware encoding is inferior quality than x264, as you have seen. Though, I must admit I have not been keeping up so there might be an hardware encoder who does better.
ffdshow is the decoder for VfW I use that supports FFV1 version 1. Hmm, I knew about this a while back, I guess I didn't mention it anywhere here, sorry.
Don't get me wrong, what retrotink2x does is very impressive for on fly and having near zero lag, but it has it's limitation. I'm not saying to "pretty" it up afterwards, I'm saying the "jank" wasn't there in the first place. I'm saying it's an after effect of using scalers and on fly deinterlacing, etc which can be fixed if a better deinterlacer (though slow) is used on the original content. But for the speed purpose, I can see your setup be good enough. This is why I asked if you want the best quality or just good enough.
Edit: Going back to your original question before this tangent, I think 480p60 was a limited time thing on YT (my guess) and it is unlikely to get it. Just a guess, that or it needs to be exactly 60 FPS (a wild guess).
Edit 2:
No wonder why doing PS1 on BizHawk I had to choose only certain fields.
That's the thing, I've done smash videos in the past and I didn't have those problems. Really is too bad I don't have a GC + Smash somewhere to show what I mean. Watching Smash on Twitch.tv, I wonder how they deinterlace on fly. Your FF8 example does look very good, however. But I think I can do the same in software, I do have my PS1 here but FF8 is somewhere else, I could capture FF9 instead.
I really doubt retrotink does a better job from the YouTube video you linked us as there is a lot of problems with that video. It's too bad I don't have a GC to make a sample, but would a sample from a PS2 work for you?
If your goal is to have the best quality on YouTube, I still think capturing the original interlace signal and then using software deinterlacer like QTGMC would be better quality.
If you don't mind some reboots, can you try this?
1. Reboot
2. Install version 2.1 of prereq
3. Reboot
4. Extract to a new folder of BizHawk version 2.3
5. Try it out!
What version of the prereq file did you install? The error message you posted doesn't make much sense since you have a decently new computer running Windows higher than 7 with a dedicated GPU that can do 3D quite well. I'm pretty sure DX9 games work on Win8 so the fact it fails to create a Dx9 device is troubling. The other thing I can think of is updating your GPU drivers and/or Intel if it does both. Other thing I can think of is forcing BizHawk to use NVidia.
x264vfw is largely outdated. I'm not even sure if there is a 10-bit x264vfw. With H.264 support hacked into AVI anyway, I would really avoid x264vfw if you can. It is most likely 8-bit. x264 8-bit/10-bit EXE is the most up-to-date version of x264. Use those. 10-bit has better compression, but it is more complex, meaning encode and decode slower. If you are sending to YouTube, YouTube is 8-bit (I think?) and you should be sending 8-bit H.264.