-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-07-03 18:36, Iain Mott wrote:
On Tue, 2012-07-03 at 09:15 +0200, IOhannes m zmoelnig wrote:
Gem is 20fps you will play the file at a reduced speed. the simplest solution is to raise Gem's framerate.
as others have pointed out, the "blurring" will most likely come from inter-frame compression where you are trying to access non-keyframes and the used backend (most likely gmerlin, according to your settings) does a bad job at reconstructing the image.
Thanks IOhannes, I didn't know about the 20fps default. If gmerlin does a poor job, how can enlist the services of a better backend? Is this a matter of using a different codec or do I have to recompile with certain config options?
i'm not saying that gmerlin _is_ doing a bad job. afaik, it does the best job _in general_ (supports most formats, allows to access random-access, ...) whether it does a bad job in the specific case i cannot really tell, but it seems so.
anyhow, you can select a different backend using yet another parameter to the "open" message: [open foo.mov RGBA quicktime4linux( should open "foo.mov" in the RGBA-space using "quicktime4linux" (rather than gmerlin).
afair, the backend is merely a suggestion, and if the desired backend is not able to open the given file, it will fallback to the default behaviour.
fgamsdr IOhannes