Well, I'm not sure you can get the quality you want. A 10 year old computer (2008) IMO can still play BizHawk, just slow. It can also do all this render, just slow. Here is a site that explains interlacing better than I can:
http://www.100fps.com/
I'm still doing some tests, so be patient. The way I did this requires you have certain settings in Bizhawk (you are using Bizhawk, right?) and also requires fixing the output and then deinterlacing before using PointResize and AreaResize. It is also slow to render. How fast is your computer?
AreaResize just does downscaling with weighted averaging so it might be sharper and less blurry for text.
Edit: I made a sample test with AreaResize, here is my result:
https://www.youtube.com/watch?v=IncF18TmI1Q&feature=youtu.be
Is this what you are aiming for?
That's a pretty slow CPU, honestly. It could be that.
Lagarith can be huge, but it depends what you think is huge. How much free space do you have and how long are you capturing? With your slower CPU, Lagarith is easier to decode but it depends on your hard drive speed.
Would you happen to have the exact model number? I want to find out what CPU. It not playing back in the editor is fine as long as your edits and final file plays fine in VLC, no?
If you're doing editing, I would recommend using lossless like Lagarith. This is assuming you have enough space, though GB/GBA games resolution is tiny so you must be really strapped for space to not have enough for a capture. Also, Xvid includes B-frames which will make AVIs funky sometimes. Really highly recommend you go lossless Lagarith.
So I'm still confused. Your first post says it plays smoothly in VLC, but now you're saying it doesn't play smoothly in VLC? Which is it? As long as MPC and VLC plays it back right, it's fine. Video editors may do extra processing making it too slow to playback smoothly. What are your PC specs?
I don't remember exactly, since it's been a while, but VBA may have some minimal capture settings. What codec did you capture to?
You need ffdshow installed. It is using an older version of ffmpeg which only supports FFV1 Level 1, which is why I mentioned it. What line did you use to convert? How accurate do you need the cut of the scene? If you don't need it to be too accurate, you can cut via key frames in MKVToolNix GUI itself using timestamps.
Edit: I do not recommend using codec packs due to the problems they may bring with installing extra codecs you would never use. I prefer installing codecs as needed bases.
What are you trying to do? Honestly if you are going to use AviSYnth script on it, I would convert it to lossless FFV1 Level 1 (AVI) with FFMPEG which can be opened by VDub and AviSynth
[18:01] <muggphone1> says AC3 5.1 chnls for all of them
[18:01] <Aktan> wait, third track?
[18:01] <Aktan> oops
[18:01] <Aktan> mkvextract.exe input.mkv tracks 3:output.ac3
[18:02] <Aktan> this is assuming only 1 video track at track 0
[18:02] <muggphone1> yes
[18:02] <Aktan> then track 1 is first ac3, track 2 is 2nd audio track.. etc
Great job! Only nitpick is why did you add the black bars to the left and right of the screen? I am on a 4:3 monitor and now I have black bars all around. YouTube is smart enough to auto add the black bars on a 16:9 screen.
Hmm good question. It may work fine in sequence but not so fine when out of sequence. I don't know, try both? I think random access is the ultimate test as I usually do see the problem after random access. Aka seek to some random frame, then going back to frame 0 yields a grey screen. I guess this is less of a problem since an encoder always encode in sequence, but on the other hand if you need to do any video editing, like cut out parts here and there, it be not in sequence anymore.
I should note that H.264 in AVI is usually a hacky workaround for B-Frames (since AVI doesn't support B-Frames). Lossless has no B-Frames so hopefully the problem isn't there but usually it means with the hack that frame 0 may be duplicated a few frames. Aka, maybe do a test to see the frame count in the x264 RGB vs LAGs vs FFV1?
Edit: Also do a test to see if a scene change starts at the same frame for all three?
You know, this goes for RGB H.264 too... I don't think RGB in H.264 is actually standard, just the most popular encoder, x264, added a way to do it. I could be wrong though. Even if I am wrong, I believe the profile needed to playback RGB H.264 would be one of the highest and not many players support that.
Sorry, I should have clarified that it's still bad that the encoded file doesn't have the correct flag (aka Bizhawk should be telling FFMPEG to write the flag). All I was saying is that it should be an easy fix without the need of capturing again. This is assuming it is a flag issue, which could be, but I don't know the full FFMPEG line Bizhawk uses. The fact that it is corrected there in VLC is really weird. Unless the flag is there, VLC should assume limited color range and look incorrect still. You can try something like method #4 listed here: http://avisynth.nl/index.php/Luminance_levels. Try the shader "0-255 to 16-235" or the opposite. For good measure, try the shader "BT.601 to BT.709".
I would make sure my assumption is correct first before finding the flag. While writing this post, I was second guessing myself if indeed this is a levels problem.
I'll do a test locally to speed things up, then I can actually figure the problem instead of guessing, but I really think it's not that FFMPEG is doing something wrong, it's more like just a missing flag, either range flag or color matrix flag.
Edit:
Okay, I did the test locally. Basically Bizhawk sends it to FFMPEG and FFMPEG guesses on a lot of the settings (aka uses default). Most people won't know how to set it correctly hence a simple line is used, but to get it correct, the line is a lot longer. It also doesn't help that Bizhawk came with an older version of FFMPEG. What you can do is get a newer version and place it in the dll folder of Bizhawk. Then in FFmpeg writer settings, choose [Custom] and use this as the command:
I should note the line I used is meant for SD games. HD games should have a different line. Also note, I choose limited color range since it is more widely used. Some may want to change the range to be full. As you can see, there is a lot of "complications" when choosing the options.
Okay thanks, your MediaInfo is weird with all the repeats. Anyway, the MKV is in RGB with color range info while the MP4 is in YV12 with no color range, so it was guessed as limited in MPC. I'm thinking if you set the flag to be full color range in the MP4, it will have the correct colors, assuming MPC is setup correctly.
Edit: I guess you fixed the info, lol.
No, you're misunderstanding. How are you getting that screenshot above? I think it be easier if you just post the info both those clips produce in MediaInfo, if you can.