I'm using ivtv 0.3.6z, along with the new ivtvdev_drv.o that came with it, on myth 0.18.1-fixes, a fairly recent version.
Last night I was beginning to record Battlestar Galactica on MythTV and had an interesting (a bit frustrating) episode. Myth had just gone into recording mode and was playing the recording as it was recording. I started to turn the volume up in Myth (I'm using oss for sound) and suddenly the audio encoding in ivtv quit, but the video kept going. In the recording, everything after that point was silent. I know it wasn't oss because if I skipped back to before the point where audio encoding quit, the audio played just fine. It stops again when it gets to the fubar point. I could still adjust the volume in myth for other things, play music, etc. It kinda sucked because not only did I have to reboot (this is a combined backend/frontend), the previous day my wireless network went out due to a 1s power off at my home. Since I use ntpd to keep my clock synchronized, it took a few minutes for the machine to reboot. What's worse even, I had to reboot again because after the first reboot, x11 on the 350 failed. In the end, it was 10:15 before I could even start watching the show I had scheduled to record at 10:00. :( Anyway, I was able to re-record BG when it came on again at 1am. The attached file shows the /var/log/messages entries during the period in question. I also included some lines from mythfrontend.log at the bottom. There's some strange error message about ac-tex being damaged there. So, the question is: is there somethign wrong with my setup, is there a bug in ivtv or myth, or something else? I'd like to prevent this in the future if possible. Thanks.
var.log.messages
Description: 1528755239-var.log.messages
