[mythtv-users] 0.25.3: 0-Byte recordings, how to fix?

Tim Draper veehexx at gmail.com
Sun Nov 4 11:50:09 UTC 2012


On 4 November 2012 08:43, Martin Moores <moores.martin at gmail.com> wrote:

> On 4 November 2012 08:18, <cvb at kruemel.org> wrote:
>
>> Hi - I recently upgraded my machine from Ubuntu 10.04 to 12.04, and hence
>> now have mythtv 0.25. With this, I am seeing a significant increase of
>> 0-Byte-recordings.
>>
>> It appears that mythtv thinks it is recording the shows, but nothing
>> happens. However, mythtv keeps thinking it is recording the show even after
>> it has stopped - until I quit and restart mythtv. Also, restarting helps to
>> enable recordings with more than 0 Bytes again.
>>
>> Not sure this is a helpful error description. I also have added a log
>> below showing when the recording should have started and ended. mythtv
>> actually did only stop "recording" when I pkilled it this morning:
>>
>> Nov  3 20:04:30 alpha mythbackend[10195]: I Scheduler mythdbcon.cpp:395
>> (PurgeIdleConnections) New DB connection, total: 11
>> Nov  3 20:04:30 alpha mythbackend[10195]: I TVRecEvent tv_rec.cpp:1544
>> (HandlePendingRecordings) TVRec(2): ASK_RECORDING 2 28 0 0
>> Nov  3 20:04:30 alpha mythbackend[10195]: I TVRecEvent tv_rec.cpp:1544
>> (HandlePendingRecordings) TVRec(1): ASK_RECORDING 1 28 0 0
>> Nov  3 20:05:00 alpha mythbackend[10195]: I TVRecEvent tv_rec.cpp:1030
>> (HandleStateChange) TVRec(1): Changing from None to RecordingOnly
>> Nov  3 20:05:00 alpha mythbackend[10195]: I TVRecEvent mythdbcon.cpp:395
>> (PurgeIdleConnections) New DB connection, total: 11
>> Nov  3 20:05:00 alpha mythbackend[10195]: I TVRecEvent tv_rec.cpp:3503
>> (TuningCheckForHWChange) TVRec(1): HW Tuner: 1->1
>> Nov  3 20:05:00 alpha mythbackend[10195]: I CoreContext mythdbcon.cpp:395
>> (PurgeIdleConnections) New DB connection, total: 11
>> Nov  3 20:05:00 alpha mythbackend[10195]: E TVRecEvent
>> dvbchannel.cpp:1103 (GetUncorrectedBlockCount) DVBChan(1:/dev/dvb/adapter0/
>> **frontend0): Getting Frontend uncorrected block count
>> failed.#012#011#011#011eno: Operation not supported (95)
>> Nov  3 20:05:00 alpha mythbackend[10195]: W TVRecEvent
>> dvbsignalmonitor.cpp:91 (DVBSignalMonitor) DVBSM(/dev/dvb/adapter0/**frontend0):
>> Cannot count Uncorrected Blocks#012#011#011#011eno: Operation not supported
>> (95)
>> Nov  3 20:05:00 alpha mythbackend[10195]: N Scheduler autoexpire.cpp:263
>> (CalcParams) AutoExpire: CalcParams(): Max required Free Space: 3.0 GB
>> w/freq: 14 min
>> Nov  3 20:05:00 alpha mythbackend[10195]: I Scheduler scheduler.cpp:2513
>> (HandleRecordingStatusChange) Tuning recording: "Blitz - Cop-Killer vs.
>> Killer-Cop":Thriller: channel 1131 on cardid 1, sourceid 1
>> Nov  3 20:05:01 alpha mythbackend[10195]: N DVBRead
>> dtvsignalmonitor.cpp:354 (HandlePMT) DTVSM(/dev/dvb/adapter0/**frontend0):
>> PMT says program 131 is encrypted
>> Nov  3 20:05:03 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x504 status:
>> Encrypted
>> Nov  3 20:05:03 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x503 status:
>> Encrypted
>> Nov  3 20:05:04 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x4ff status:
>> Encrypted
>> Nov  3 20:07:02 alpha mythbackend[10195]: N DVBRead
>> dtvsignalmonitor.cpp:354 (HandlePMT) DTVSM(/dev/dvb/adapter0/**frontend0):
>> PMT says program 131 is encrypted
>> Nov  3 20:07:03 alpha mythbackend[10195]: N DVBRead
>> dtvsignalmonitor.cpp:354 (HandlePMT) DTVSM(/dev/dvb/adapter0/**frontend0):
>> PMT says program 131 is encrypted
>> Nov  3 20:07:04 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x503 status:
>> Encrypted
>> Nov  3 20:07:07 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x4ff status:
>> Encrypted
>> Nov  3 20:15:08 alpha mythbackend[10195]: N DVBRead
>> dtvsignalmonitor.cpp:354 (HandlePMT) DTVSM(/dev/dvb/adapter0/**frontend0):
>> PMT says program 131 is encrypted
>> Nov  3 20:15:11  mythbackend[10195]: last message repeated 2 times
>> Nov  3 20:15:11 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x503 status:
>> Encrypted
>> Nov  3 20:15:11 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x4ff status:
>> Encrypted
>> Nov  3 20:15:15 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x504 status:
>> Unknown
>> Nov  3 20:15:17 alpha mythbackend[10195]: I DVBRead
>> mpeg/mpegstreamdata.cpp:1980 (ProcessEncryptedPacket) PID 0x504 status:
>> Encrypted
>> Nov  3 22:03:00 alpha mythbackend[10195]: I TVRecEvent tv_rec.cpp:1030
>> (HandleStateChange) TVRec(1): Changing from RecordingOnly to None
>>
>> I have a TT-3200 with a CAM in my system, since some years. 70% of the
>> recordings are working (encrypted or not), 30% are failing with 0 Bytes
>> recordings (encrypted or not). Restarting mythbackend helps to recover the
>> situation - after a recording has failed.
>>
>> Happy to provide additional information required to fix the problem.
>>
>> Thanks, Chris
>>
>
> Chris
>
> Don't know if this is relevant, or just for my tuner card.  I used to get
> this a lot on my dual tuner, when EIT was enabled on both tuners, used to
> lock it up.
>
> Not familiar with your setup, so please ignore if this doesn't apply!
>
> Martin
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
>
i get issues with one of my USB tuners (replaced it - weak v4l driver
support). It used to lockup and only removing it from the USB bus did it
work again - reboots didn't fix.
ime, 0B recordings are down to the follow - no satellite lock, no antenna
connected, or tuner config/hardware related issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20121104/90a6ed50/attachment.html>


More information about the mythtv-users mailing list