|
Originally Posted by gabextremev200
|
Oh, I guess there were some posts I missed! (should have refreshed!) Well, hm... that's a good idea. Re-encoding... thanks, I'll try it out on these clips, lol.
I guess you have a point there, but when you decode with Raw Framebuffer, the video looks just like the original, even without dithering.
If only "Intel 2700G" looked as good as Raw Framebuffer.
When I use TCPMP's "Raw Framebuffer," the clips look so similar to the originals on the PC that I really can't tell the difference if you were to give me screenshots! Especially with dithering. But when the decoder has anything to do with "2700G," the colors are thrown out of whack and there is blocking, etc. If Raw Framebuffer and i2700G look the same to you, I think its a problem with my particular decoder.
The problems with just sticking to Raw Framebuffer are:
1. At least 3 times slower than "Intel 2700G"
2. Screen tearing problems
3. "Reduce LCD Tearing" option slows it down even more
|
i have to agree with you that it does look better with Raw Framebuffer than with "2700G decoder", but no difference with "2700G". In other words, "2700g docoder" is much worse than "2700g" option. However, all of these options will show you blocks that you will not see on your PC monitor.