[mythtv-users] auto-transcode and keyframe indexing

Nicolas Will nico at youplala.net
Mon Dec 1 22:36:07 UTC 2008

Hello all,

I am a DVB-T user.

I am using the lossless MPEG-2 transcode to go from transport streams to
program streams and save the average 20% disk space.

I have set the commercial detection to run after the transcode.

So things should be running in that order:
     1. record
     2. transcode
     3. generate keyframes index (as part of transcode)
     4. commercial detection

I have noticed that since I've set the auto-transcode that none of my
recordings have a proper keyframe index.

Manually re-indexing using mythcommflag makes ffwd and rwd fine again.

I have looked at the logs, and yes, the transcode script forces a
keyframes indexing.

However, the transcode script appears to first generate an <original
file name>.tmp file. The re-indexing also appears to be run against
this .tmp file. Then there should a swap to the original file name, as
the .tmp file is never mentioned again and the file is not on disk

I have left a backend log starting at recording end and ending after the
commercial detection here:


I'm running Mythbuntu 8.10, using the packaged MythTV:

nico at favia:~$ less /var/log/mythtv/mythbackend.log
nico at favia:~$ mythbackend --version
Please include all output in bug reports.
MythTV Version   : 18722
MythTV Branch    : branches/release-0-21-fixes
Library API      : 0.21.20080304-1
Network Protocol : 40
Options compiled in:
 linux profile using_oss using_alsa using_arts using_jack using_backend
using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun
using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc
using_opengl_vsync using_opengl_video using_v4l using_x11 using_xrandr
using_xv using_xvmc using_xvmcw using_xvmc_vld using_glx_proc_addr_arb
using_bindings_perl using_bindings_python using_opengl
using_ffmpeg_threads using_libavc_5_3 using_live

Any help, pointers would be appreciated.



More information about the mythtv-users mailing list