Sunday, February 26, 2006

MythTV 0.19

Upgraded to 0.19 today via the most recent atrpm packages. I held off for a couple weeks to see how others faired and to give a chance for some fixes to get folded back in. LiveTV in 0.18.x hasn't worked properly for me in ages and I was waiting for 0.19 to avoid having to spend a lot of time tracking down the problem. However, several people reported a bunch of issues with the reworked LiveTV code in 0.19 and I wanted to wait for them to be fixed. According to the MythTV Users and Dev lists, it looks like they're now gone.

Here's the upgrade procedure I used:
  1. Shutdown all frontends
  2. Shutdown mythbackend on slave
  3. Shutdown mythbackend on master
  4. Backup mythconverg database (v0.18.1)
  5. yum update on master
  6. Run mythtvsetup on master (to update database schema)
  7. Backup mythconverg database (v0.19)
  8. yum update on slave
  9. Start mythbackend on master
  10. Start mythbackend on slave
  11. Start mythfrontend
Unfortunately, (6) didn't go as smoothly as I'd hoped. At some point in the past, I'd run a CVS frontend on my OSX laptop and this hosed a database schema update. I remember having to fixup a few things afterward to regain stability. Anyway, the 0.18.1 -> 0.19 schema update failed and I had to repeatedly undo failed updates (remove table columns etc.) and re-run mythtvsetup until the schema finally updated cleanly to version 1123. A few other people on the lists had similar issues and I think they're all related to previous failed schema updates.

Here's a few things I've noticed today that may be bugs in 0.19 or bugs in my config or just random application or OS errors:
  • My remote occassionally loses focus in the setup screens of mythfrontend or at least the up/down/right/left buttons stop working. Restarting mythfrontend fixes the problem.
  • When LiveTV was interrupted with a scheduled recording and I later quit back to the menu, no bookmark was saved and the watch recording screen didn't indicate that the recording was continuing, even though it continued and completed just fine.
  • mythcommflag didn't auto-run for the above LiveTV-interrupted, scheduled recording
  • A few IOBOUND errors appeared in my slave log
  • Autoexpire deletions are working but the slave complains about not finding appropriate db entries
  • Slave could not produce a preview image because the mpg was 'not valid' even though it was watchable and a preview finally appeared after > 1hr.
  • Preview unavailable on an otherwise ok recording. What should generate this? The Slave backend, master backend or the frontend? Some previews are being generated as mythtv.mythtv (frontend perms) rather than root as under 0.18.x... The preview only appeared after trying to watch the recording.
  • Couldn't get MythTV's internal DVD player to send digital audio out of the SPDIF on my Shuttle.


Post a Comment

<< Home