[mythtv-users] Recording of 0.00 GB in size

Jerry Rubinow jerrymr at gmail.com
Tue Sep 21 15:18:06 UTC 2010


On Tue, Sep 21, 2010 at 11:10 AM, Adam Jimerson <vendion at gmail.com> wrote:

> On Sun, Sep 19, 2010 at 11:12 PM, Adam Jimerson <vendion at gmail.com> wrote:
>
>> On Sun, Sep 19, 2010 at 11:07 PM, Jerry Rubinow <jerrymr at gmail.com>wrote:
>>
>>> On Sun, Sep 19, 2010 at 10:53 PM, Adam Jimerson <vendion at gmail.com>wrote:
>>>
>>>> On Fri, Sep 17, 2010 at 12:12 AM, Jerry Rubinow <jerrymr at gmail.com>wrote:
>>>>
>>>>> On Fri, Sep 17, 2010 at 12:05 AM, Adam Jimerson <vendion at gmail.com>wrote:
>>>>>
>>>>>> Ok so I'm resending my last post because the mailing list ate it,
>>>>>> saying it was to large.  Anyways I checked the mythbackend.log and found it
>>>>>> littered with entries that looked like the following:
>>>>>>
>>>>>> 2010-09-16 08:00:34.157 AudioInALSA(hw:2,0) Error: weird return from
>>>>>> snd_pcm_readi: Input/output error
>>>>>> 2010-09-16 08:00:34.157 NVR(/dev/video0) Error: Short read, 40 of 3072
>>>>>> bytes from ALSA:hw:2,0
>>>>>> strange error flushing buffer ...
>>>>>> select timeout
>>>>>>
>>>>>> I can only find them while the system has failed to correctly record a
>>>>>> show so I'm sure this has something to do with it but don't know what to
>>>>>> make of it or how to fix it.  I had tried to post more of the log during the
>>>>>> recording of one of the shows in case I over looked something, but that is
>>>>>> what set me over the mailing list limit, if anyone wants to look through it
>>>>>> let me know and I'll find some kind of file host/server to upload it to (to
>>>>>> large for pastebin every try fails and causes the browser to lock up).
>>>>>>
>>>>>
>>>>> The interesting part should be when the backend first wakes up to tune
>>>>> the station and begin the record, up through the first of the messages like
>>>>> the excerpt you posted.  All I can tell from the above is that it looks like
>>>>> it is having problems getting data from your tuner (/dev/video0).  Can you
>>>>> post that section of the log file?  It doesn't have to be large.  Also, what
>>>>> type of tuner card do you have?
>>>>>
>>>>> -Jerry
>>>>>
>>>>
>>>> Sorry for the long delay, work has been keeping me from messing with
>>>> Myth.  As for the request from the log here is from where, as far as I can
>>>> tell, the backend wakes up for the recording all the way to where it starts
>>>> spitting out the "select timeout"s
>>>>
>>>> 2010-09-16 07:59:00.594 scheduler: Scheduled items: Scheduled 214 items
>>>> in 0.1 = 0.00 match + 0.13 place
>>>> 2010-09-16 07:59:29.898 TVRec(1): ASK_RECORDING 1 29 0 0
>>>> 2010-09-16 08:00:02.660 TVRec(1): Changing from None to RecordingOnly
>>>> 2010-09-16 08:00:02.661 TVRec(1): HW Tuner: 1->1
>>>> 2010-09-16 08:00:02.711 ProgramInfo(): Updated pathname '':'' ->
>>>> '1063_20100916080000.nuv'
>>>> 2010-09-16 08:00:04.021 SampleRate: Attempted to add a rate 32000 Hz,
>>>> which is not in the list of allowed rates.
>>>> 2010-09-16 08:00:04.024 TVRec(1): rec->GetFileName():
>>>> '/mnt/storage/MythTv/Default/1063_20100916080000.nuv'
>>>> 2010-09-16 08:00:04.136 NVR(/dev/video0) Error: Can't open vbi device:
>>>> ''
>>>> 2010-09-16 08:00:04.208 AutoExpire: CalcParams(): Max required Free
>>>> Space: 2.0 GB w/freq: 15 min
>>>> 2010-09-16 08:00:04.218 Started recording: V: channel 1063 on cardid 1,
>>>> sourceid 1
>>>> 2010-09-16 08:00:04.226 scheduler: Started recording: V: channel 1063 on
>>>> cardid 1, sourceid 1
>>>> select timeout
>>>> 2010-09-16 08:00:14.157 AudioInALSA(hw:2,0) Error: weird return from
>>>> snd_pcm_readi: Input/output error
>>>> select timeout
>>>> select timeout
>>>>
>>>>
>>>> As for my TV Tuner it is a Hauppauge WinTV HVR-950Q USB device.
>>>>
>>>
>>> For the recording on the same channel that works, does the log look any
>>> different (besides the ALSA errors)?  Not sure if the SampleRate message is
>>> significant, or the vbi error, but I'd try looking in the archive for other
>>> people reporting those errors, if they are absent on the recording which is
>>> successful.  That's about the limit of what I can think of to try.
>>>
>>> -Jerry
>>>
>>>
>> The vbi errors should still be in the recordings that work correctly, I
>> don't have anything set for the vbi option because I thought that it was for
>> closed captions.  I'll check into the logs to compare the  good and bad
>> recordings to see what is different.
>>
>
> Ok so I was wrong both errors do not exist in a good recording  here is the
> myth log from a good recording:
>
> 2010-09-21 02:00:04.617 scheduler: Started recording: Star Trek: Voyager
> "Coda": channel 1064 on cardid 1, sourceid 1
> 2010-09-21 02:00:09.906 ProgramInfo(): Updated pathname '':'' ->
> '1064_20100921020000.nuv'
> 2010-09-21 02:00:09.919 JobQueue: Commercial Flagging Starting for Star
> Trek: Voyager "Coda" recorded from channel 1064 at Tue
>

[snip]

This output start after the channel is tuned.  The output with the errors
starts before this point, and the errors therein occur before the
 "scheduler: Started recording" line.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100921/2b5aa0ee/attachment.htm>


More information about the mythtv-users mailing list