Opened 15 years ago

Closed 14 years ago

#7179 closed defect (duplicate)

Length of recordings shown wrong during playback

Reported by: anonymous Owned by: Janne Grunau
Priority: minor Milestone: unknown
Component: MythTV - Video Playback Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

The indicated length of my TV recordings and the current position in OSD is wrong during playback. The indicated length is usually a few minutes shorter than the actual length so the video continues to play after the OSD indicates the length has been reached, and commercial skipping/ff/rw jumps to the wrong position.

This happens on all my recordings coming from my PVR-150. It happens with "old" recordings from 0.21 which used to work well as well as 0.22 recordings.

For example.. mplayer correctly tells me a recording is 59m55s while mythtv says 57m43s for a one hour recording.

MythTV Version : 22009 MythTV Branch : trunk Network Protocol : 48 Library API : 0.22.20090919-1 QT Version : 4.5.0 Options compiled in:

linux debug using_oss using_alsa using_pulse using_jack using_backend using_dvb using_firewire using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

Attachments (1)

frontend_playback.log (19.8 KB) - added by anonymous 15 years ago.
mythfrontend log with playback debugging. Start frontend, play recording, end playback and end frontend.

Download all attachments as: .zip

Change History (7)

Changed 15 years ago by anonymous

Attachment: frontend_playback.log added

mythfrontend log with playback debugging. Start frontend, play recording, end playback and end frontend.

comment:1 Changed 15 years ago by anonymous

Example recording available here: http://83.252.170.215/12_20090925234500.mpg

Reported length of video: mplayer: 14m54s (correct) mythtv: 13m03s

comment:2 Changed 15 years ago by anonymous

Oh.. I just noticed the recording length is retrieved from the database and may not be based on the recorded file. So I guess the example recording isn't of much use. What is?

comment:3 Changed 14 years ago by sphery

This sounds like a broken seektable. Please see http://www.mythtv.org/wiki/Repairing_the_Seektable and report back whether that fixes the issue. If so, it's likely a dup of #7978

comment:4 Changed 14 years ago by sphery

Status: newinfoneeded_new

comment:5 Changed 14 years ago by anonymous

My problem looks much like Chris Rouch's problem in #7978.

I optimized my database and used mythtranscode to rebuild the seek table for all my MPEG-2 recordings. This fixed the recording lengths of previously recorded programs, but new recordings keep getting a shorter length than expected. Mythcommflag does not fix recording lengths for me.

I'm currently using Ubuntu 9.10 from which I'm now running this mythtv version:

MythTV Version : 23193 MythTV Branch : branches/release-0-22-fixes Network Protocol : 50 Library API : 0.22.20091023-1 QT Version : 4.5.0 Options compiled in:

linux profile using_oss using_alsa using_pulse using_jack using_backend using_dvb using_firewire using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

comment:6 Changed 14 years ago by sphery

Resolution: duplicate
Status: infoneeded_newclosed

Thanks for the update. I'm closing this as a dup of #7978 (and/or #7849 ).

Note: See TracTickets for help on using tickets.