Originally Posted by waterhead
It is my experience that the commercial flagging is not perfect. Before you actually cut the commercials, you should review the file and adjust the sections to be removed.
This is my experience as well. Some programs are flagged with extremely high accuracy; others... well, the flagger struggles. Especially with very dark shows (like Battlestar Galactica, or Stargate Universe). I find that the flagger can struggle with basketball games, especially near the end of the game where frequent commercial breaks can mean there is more commercial than game.
My actual practice is to run the flagger on non-sports shows, and watch non-transcoded programs. I run my frontends with auto-skip, but notify me of how much time was skipped. If I notice an over-skip, I can back up and watch the part of the show that was erroneously flagged as a commercial. If it under-skips, it's easy to hit the 30 second skip button. I've got just over a TB of space (which used to be a lot, back when the big drives were 250GB!), and I'm only using about half of that, so I'm not worried about transcoding to save space. IMO, it just uses processing resources that are better allocated to commercial flagging ASAP. If the job scheduler was more sophisticated than a simple FIFO queue, I might consider automatically transcoding my old saved recordings (like, if it's been watched but not deleted, let's transcode to a smaller "archival" size), but right now it's not worth it.
Looking at the XBMC wiki, I see that MythTV is supported natively ( http://wiki.xbmc.org/index.php?title=MythTV
), which is good since by default the filenames are not human-friendly. The frontend displays the metadata pulled from the database, not the file names from the filesystem. You'll have to use mythweb (the web interface) to schedule shows, which is my preferred method anyway, since a mouse and keyboard is faster and more flexible than a remote control.