Opened 18 years ago

Last modified 13 years ago

#468 closed defect (fixed)

h264 sync issues

Reported by: magnade@… Owned by: reimar
Priority: normal Component: core
Version: HEAD Severity: normal
Keywords: Cc: compn, zetakoo@…
Blocked By: Blocking:
Reproduced by developer: no Analyzed by developer: no

Description

with the latest mplayer from cvs i am seeing sync issues
with some h264 files at first i thought my computer
just didnt have enuf power/speed to be able to play them
correctly/smoothly but after some playing i noticed cpu usage
isnt even maxed out with some tinkering with options
i found that -nosound -benchmark -vo xv would play smoothly
but very fast and of course cpu usage at 100%

turning off framedroping i found that video would start lagging
behind audio rather quickly doing -ao null didnt help any and -ao sdl
produced pops in the sound also only using 40% cpu time

turning on framedrop and cpu usage sits around 40% or so until it
figures out that its too far behind and has to catch up then spikes
to 100% cpu for a few seconds
also when this is enabled the console fills up with
'Error while decoding frame!'

a couple interesting items i found is setting -fps doesnt seem to have
any affect on how fast or slow video lags behind
and using mplayer instead of gmplayer affects how badly it plays
gmplayer being slightly worse off

my computer is a athlon64 2800+ with radeon 9600se video card
any other info needed just ask

the video i can reproduce the above issues can be found on bittorrent
here: http://kaizoku-fansubs.com/ look for tv special 3
skipping to 34:00 into the file finds the issue very quickly

Change History (6)

comment:1 by magnade@…, 18 years ago

with a recently released movie 5 from same url i mentioned before
i noticed this issue seems to get worse as its deeper into the file
also cpu usage is bad later in the file its using 50% vs. 25% or so
at the begining

xine plays the file fine and smooth for me and only uses a near constant 22%

and mplayer has been updated and is still current cvs

comment:2 by magnade@…, 18 years ago

i recently played some h264 on my laptop just playing around
and noticed this issue again but laptop never was able to catch up
i now wonder if ffmpeg just decodes h264 to a mpeg2 like format
uploads to video card and allows it to do the work which is a good idea
cept on really slow video cards that have a hard time with mpeg2 orignaly

reason i think is cause cpu loading on the laptop was very close to
what i see on my desktop athlon64 with the r300 card
the laptop however has a 320m card which i think is based off of a
rv100 chipset and uses shared memory to add to the strain

comment:3 by zetakoo@…, 17 years ago

Cc: zetakoo@… added

i have experienced this with every widescreen (WS) episode from http://kaizoku-fansubs.com/, episodes from 207 to current (209) they are all in ws, before that there was no errors, and 207 and 208 fullscreen versions (which aren't publicly available anymore) didn't have these issues even though they were released at the same time,

i can verify that 209 starts having problems at 5:30 ish and it will report errors while decoding frames at least once per second or so

this happens in windows when trying to play the videos and in linux when using mencoder to re-encode them to xvid (it will encode but the audio will be out of sync, and with choppyness)

in linux i used MPlayer dev-SVN-r21629-4.1.2 which is about 2 weeks old or so if i remember right
and in windows MPlayer-mingw32-1.0pre8, it would also seem that after about 5 minutes or so mplayer reports the current position 00:00:00 and will start incrementing that, and also the total lenght seem to be reported incorrently

i hope at least some of this was actually helpful

comment:4 by zetakoo@…, 17 years ago

I tried 209 in VLC just now and it seems to play fine, but the 5:00 and 5:30 times i reported earlier might be off, VLC seems to suggest something like 6:00 instead of 5:30

and computer specs are Athlon 64 3000+, 512MB and geforce 6600 gt

comment:5 by compn, 13 years ago

Owner: changed from alex@… to reimar

comment:6 by compn, 13 years ago

Resolution: fixed
Status: newclosed, patriotact@gmail.com

should all have been fixed a while ago, please try with svn and reopen if need be.

Note: See TracTickets for help on using tickets.