Very strange fame behaviour...
Hi, I've been going back and forth with fame trying to make it work nicely with the em8300 (dxr3/h+). I've almost made it work perfectly but I have now stumbled upon a wall... After about 7 minutes of playback (happens with every video at the exact same time of playback (not matter if you seek or pause etc, it happens after 7 minutes of active playback) the pixels get blown up. It looks like the screen is set to a lower resolution, but the seek-bar and time counter is still displayed properly (well, almost). The pixels look like when tv networks scramble a face etc and this makes video totally unwatchable with fame. This definately does not happen with libavcodec and I haven't got a clue to why it happens, and after 7 minutes. It never goes back to the normal state either, once it's transformed you have to kill mplayer and restart. Have anyone got any clues to why this happens, or do I have to subscribe to some fame mailinglist? BTW, these are the settings I'm using: fame_params.width = s_width; fame_params.height = s_height; fame_params.coding = "IPPPPPPP"; fame_params.quality = 90; fame_params.bitrate = 6e6; fame_params.slices_per_frame = 1; fame_params.frames_per_sequence = 8; fame_params.shape_quality = 100; fame_params.search_range = 1; fame_params.verbose = 0; fame_params.profile = NULL; Ah, and yes, if I change the coding to I-frames only it works perfectly... //David Holm
Hi,
with libavcodec and I haven't got a clue to why it happens, and after 7 minutes.
I've got similar thing. It freezee after playing ~ 1000 frames. Then I had to quit and restart mplayer, seek to taht position and I could watch next 1000 frames. FInally I've found it's the fame_params.frames_per_sequence, it was set to 0x7fffffff by default. Setting it to 25 solved this problem. No such problem what you described.
Ah, and yes, if I change the coding to I-frames only it works perfectly...
Ah. I've never tried IPPPP for longer time. But I've experienced some bugs (bad pixels, like overflows) with IPPPP encoding of fame, with frames containing high detail crominance planes. A'rpi / Astral & ESP-team -- Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu
On Tue, Mar 19, 2002 at 08:55:53PM +0100, David Holm wrote:
Hi, I've been going back and forth with fame trying to make it work nicely with the em8300 (dxr3/h+). I've almost made it work perfectly but I have now stumbled upon a wall... After about 7 minutes of playback (happens with every video at the exact same time of playback (not matter if you seek or pause etc, it happens after 7 minutes of active playback) the pixels get blown up. It looks like the screen is set to a lower resolution, but the seek-bar and time counter is still displayed properly (well, almost). The pixels look like when tv networks scramble a face etc and this makes video totally unwatchable with fame. This definately does not happen with libavcodec and I haven't got a clue to why it happens, and after 7 minutes. It never goes back to the normal state either, once it's transformed you have to kill mplayer and restart.
Have anyone got any clues to why this happens, or do I have to subscribe to some fame mailinglist?
BTW, these are the settings I'm using: fame_params.width = s_width; fame_params.height = s_height; fame_params.coding = "IPPPPPPP"; fame_params.quality = 90; fame_params.bitrate = 6e6; fame_params.slices_per_frame = 1; fame_params.frames_per_sequence = 8; fame_params.shape_quality = 100; fame_params.search_range = 1; fame_params.verbose = 0; fame_params.profile = NULL;
Ah, and yes, if I change the coding to I-frames only it works perfectly...
Why would you want to use IPPPPPPP rather than I-only??? It's just a lot slower... Rich
On Tue, 19 Mar 2002, David Holm wrote:
Hi,
Hi,
It never goes back to the normal state either, once it's transformed you have to kill mplayer and restart.
Have anyone got any clues to why this happens, or do I have to subscribe to some fame mailinglist?
I don't have any precise idea, but maybe this is due to a bug in the pmvfast algorithm in version 0.8.9 (fixed on current CVS) or maybe new rate control algorithms.
BTW, these are the settings I'm using: fame_params.width = s_width; fame_params.height = s_height; fame_params.coding = "IPPPPPPP"; fame_params.quality = 90; fame_params.bitrate = 6e6;
Can you try setting fame_params.bitrate = 0?
fame_params.slices_per_frame = 1; fame_params.frames_per_sequence = 8;
Why do you set it to 8? Can you try leaving it to the default value? (0xffffffff)
fame_params.shape_quality = 100; fame_params.search_range = 1;
1 is very small. You should try larger search_range anyway..
fame_params.verbose = 0; fame_params.profile = NULL;
Ah, and yes, if I change the coding to I-frames only it works perfectly...
Ok, can you also try using different motion estimation algorithms? Add this code between the call to fame_open and the call to fame_init: { fame_object_t *object; object = fame_get_object(fc, "motion/none"); fame_register(fc, "motion", object); } You can also try with the "motion/fourstep" estimation algorithm. regards, Vivien Chappelier.
participants (4)
-
Arpi -
D Richard Felker III -
David Holm -
Vivien Chappelier