Usually around as much as the Deldupped encode took (If not longer, for games with lots of duplicate frames). The problem is, is that I feel that it basically isn't worth it, from what I understand, people will just watch a given encode on YouTube anyway (Where, ironically, barring 60fps issues, the quality is higher than the SD encode when played at Original mode).
The rare exceptions will probably be when a game doesn't have room for dupe frames (Such as Metroid Prime Pinball).
Sorry to say, this is your personal opinion. Original mode, in my opinion, will never be higher quality than the original resolution downloadable encode. This is not only due to the missing frames, but the fact that the original mode encodes have been aspect ratio corrected by resize and are very blocky.
No offense, but I think I prefer the point-resizing method we are using. I don't really like the blur.
Yep, to each their own. I sure don't like the blockiness, as stated in my first post =p. I think this blur is cleaner and better than any upscale I've seen on fly, and all the color is there!
Since I don't like the blockiness of point resize to retain all the color information, I decided to try this method where I resize the luma with the best resizer I know of and resize the chroma with point resize. I used the following Avisynth script:
LoadPlugin("nnedi3.dll")
a = AVISource("RM2Video.avi")
chroma = a.PointResize(a.width * 2, a.height * 2).ConvertToYV24(chromaresample="point").ConvertToYV12(chromaresample="point")
luma = a.ConvertToRGB24().nnedi3_rpow2(rfactor=2, nsize=4, nns=4, qual=2, pscrn=false, cshift="LanczosResize", ep0=100).ConvertToYV24(chromaresample="point").ConvertToYV12(chromaresample="point")
last = luma.MergeChroma(chroma)
return last
I just saw this, and while I get graphical errors on playback also, I don't know if you have found a solution. One solution is to try to capture to something other than lossless H.264. H.264 support in AVI is hacked anyway. If you must use lossless H.264, try updating the codec you used, which I assume to be ffdshow.
Some Japanese TASer: Mickey11189 saved 1 frame in BitFS. Please hold off on the publication if it was to take place soon.
Okay, let me know when you have updated the input file.
Regardless at least some part needs to be re-encoded, due to the subtitles being wrong. So the files will all be replaced.
Actually, sure JXQ has not TASed in a while, there could have been a lot of better ways to express that instead of what mmbossman said. Basically, I think mmbossman was rude, and it's okay to feel insulted, but the way you lashed out made people think you are this other person. Now if you are a victim of being marked as someone else who supposedly left, I don't know what I can do to clear your name, but if you're not, I would be careful and be nice to the staff as this site has an history of people with different accounts and the staff sure does not like some of these people.
It is not okay for mmbossman to be rude even if he is a respected member. I, for one, has lost some respect towards him due to his rudeness. After all, technically code's original post was just a friendly comment. None of it was towards mmbossman at all.
What about games where damaged things flash at 30Hz?
This problem was already mentioned. Blurring is probably better but depending on the framerate YouTube switches to (yes it's VFR), dropping frames may still work.
I little bad is an understatement...
As for your problem. I really have no idea. I avoid internal Mupen capture like the plague. Using .kkapture does not have these problems.
Is Glide64 better than Direct64 for encoding?
I thought the order went like this:
Direct64
Glide64
Gln
Jabos1.6
etc...
Direct64 has problems, namely fog. Glide64 IMO is the best due to the fact that it's actually still being worked on even in 2010. Last I check the WIP version was out June of this year. All other plugins are dead.
I should also mention that I don't use Mupen internal capture, since it's buggy to hell. Instead I use a modified .kkapture, but it captures very slow and the things you need to do to get it to capture is somewhat a pain.
Are you capturing in full screen or in window?
Try enabling "Use frame buffer objects".
Also, does this only happen when capture, and not when playback?
