> <------------>
> It seems that Myth on my machine can record live TV, or record a show when
> manually requested to do so while watching live (the "R" key), but will
> not record when directed to do so via the program guide or via MythWeb. I
> have scheduled several recordings over the past few days, both with the
> analog and digital tuners (pcHDTV 5500 card) - none have been able to
> record - it goes through the motions, but there are zero-byte files
> present in the recordings directory and error messages in the logs. There
> are entries in the list of recorded shows with the program info, but
> without a preview image and no file size listed. Here's a recent log dump
> (I get similar entries for every failed recording).
>>> 2007-01-03 16:10:06.606 Preview Error: Previewer file
> '/mythtv/recordings/1790_20070103155900.mpg' is not valid.
> 2007-01-03 16:10:06.608 MainServer: Failed to make preview image.
> 2007-01-03 16:10:06.609 MainServer::HandleAnnounce FileTransfer
> 2007-01-03 16:10:06.610 adding: vader.malibyte.net as a remote file transfer
> 2007-01-03 16:10:13.112
> RingBuf(/mythtv/recordings/1790_20070103155900.mpg.png): Could not open
> /mythtv/recordings/1790_20070103155900.mpg.png.
> 2007-01-03 16:10:13.114 Preview Error: Previewer file
> '/mythtv/recordings/1057_20070103020300.mpg' is not valid.
> 2007-01-03 16:10:13.116 MythSocket(2aaaabede780:-1): writeStringList:
> Error, socket went unconnected.
> 2007-01-03 16:10:13.116 MainServer: Failed to make preview image.
> 2007-01-03 16:10:13.140 MainServer::HandleAnnounce FileTransfer
> 2007-01-03 16:10:13.144 adding: vader.malibyte.net as a remote file transfer
> 2007-01-03 16:10:19.648
> RingBuf(/mythtv/recordings/1057_20070103020300.mpg.png): Could not open
> /mythtv/recordings/1057_20070103020300.mpg.png.
> 2007-01-03 16:10:19.664 MythSocket(2aaaabc0c340:-1): writeStringList:
> Error, socket went unconnected.
>>Hi Bob,
Does your log file contain anything like this?
[mpeg2video @ 0x4b37e264]ac-tex damaged at 6 21
[mpeg2video @ 0x4b37e264]invalid mb type in P Frame at 38 22
[mpeg2video @ 0x4b37e264]ac-tex damaged at 11 23
[mpeg2video @ 0x4b37e264]ac-tex damaged at 1 24
[mpeg2video @ 0x4b37e264]00 motion_type at 2 25
[mpeg2video @ 0x4b37e264]ac-tex damaged at 18 26
[mpeg2video @ 0x4b37e264]00 motion_type at 21 27
If so it could be that your signal is not strong enough so myth is
crashing or just not receiving anything it can make sense of (the
crashing seems to have reduced in recent releases with my system, but
the 0B recordings haven't on certain channels, especially Five here in
the UK which is notoriously bad for signal level!)
HTH
Phil
>--
Phil Foxton <phil at thefoxtons.org.uk>