[mythtv-users] Failed Firewire recording
Harry Devine
lifter89 at comcast.net
Sat Jun 20 13:43:59 UTC 2009
William wrote:
> On 06/20/2009 09:11 AM, Harry Devine wrote:
>> Harry Devine wrote:
>>> OK, so I had given up on using firewire for some recordings since I
>>> never got it to work consistently. I'm running Mythbuntu 8.10.
>>> After reading this thread
>>> (http://www.gossamer-threads.com/lists/mythtv/users/385324?search_string=DCH-6416;#385324)
>>> I figured I'd give it another try.
>>>
>>> I downloaded the firewire_primer.pl script and set it up as a cron
>>> job to run @ 5 &35 minutes after every hour. I setup a test
>>> recording over night last night, and when I got up this AM, I
>>> noticed that is was only about 10 seconds long. So I looked at the
>>> Myth logs and found the following, but I'm not sure what the exact
>>> problem(s) is/are:
>>>
>>> mythbackend.log:
>>>
>>> 2009-06-18 01:29:02.406 TVRec(6): Changing from None to RecordingOnly
>>> 2009-06-18 01:29:02.412 TVRec(6): HW Tuner: 6->6
>>> 2009-06-18 01:29:03.920 SetLastChannel(222): cleared: no
>>> 2009-06-18 01:29:03.930 AutoExpire: CalcParams(): Max required Free
>>> Space: 3.0 GB w/freq: 15 min
>>> 2009-06-18 01:29:03.937 LFireDev(00159AFFFE163F4A): Buffered packets
>>> 2000 (8000 KB)
>>> 2009-06-18 01:29:03.946 Started recording: In Plain Sight "A Frond
>>> in Need": channel 6222 on cardid 6, sourceid 6
>>> 2009-06-18 01:29:03.958 scheduler: Started recording: In Plain Sight
>>> "A Frond in Need": channel 6222 on cardid 6, sourceid 6
>>> 2009-06-18 01:29:04.016 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 50 msec...
>>> 2009-06-18 01:29:04.080 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 100 msec...
>>> 2009-06-18 01:29:04.132 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 150 msec...
>>> 2009-06-18 01:29:04.184 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 200 msec...
>>> 2009-06-18 01:29:04.236 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 250 msec...
>>> 2009-06-18 01:29:04.288 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 300 msec...
>>> 2009-06-18 01:29:04.340 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 350 msec...
>>> 2009-06-18 01:29:04.392 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 400 msec...
>>> 2009-06-18 01:29:04.444 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 450 msec...
>>> 2009-06-18 01:29:04.496 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 500 msec...
>>> 2009-06-18 01:29:04.548 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 550 msec...
>>> 2009-06-18 01:29:04.600 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 600 msec...
>>> 2009-06-18 01:29:04.652 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 650 msec...
>>> 2009-06-18 01:29:04.704 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 700 msec...
>>> 2009-06-18 01:29:04.756 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 750 msec...
>>> 2009-06-18 01:29:04.808 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 800 msec...
>>> 2009-06-18 01:29:04.860 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 850 msec...
>>> 2009-06-18 01:29:04.912 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 900 msec...
>>> 2009-06-18 01:29:04.964 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 950 msec...
>>> 2009-06-18 01:29:05.016 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 1000 msec...
>>> 2009-06-18 01:29:05.068 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 1050 msec...
>>> 2009-06-18 01:29:05.068 LFireDev(00159AFFFE163F4A): ResetBus() -- begin
>>> 2009-06-18 01:29:05.071 LFireDev(00159AFFFE163F4A): ResetBus() -- end
>>> 2009-06-18 01:29:05.078 LFireDev(00159AFFFE163F4A): SignalReset(1->2)
>>> 2009-06-18 01:29:05.079 LFireDev(00159AFFFE163F4A):
>>> SignalReset(1->2): Updating device list -- begin
>>> 2009-06-18 01:29:05.388 LFireDev(00159AFFFE163F4A):
>>> SignalReset(1->2): Updating device list -- end
>>> 2009-06-18 01:29:05.444 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 50 msec...
>>> 2009-06-18 01:29:05.496 LFireDev(00159AFFFE163F4A), Warning: No
>>> Input in 100 msec...
>>> libiec61883 warning: iec61883_cmp_create_bcast_output: Failed to set
>>> the oPCR[0] plug for node 63.
>>> 2009-06-18 01:29:05.497 LFireDev(00159AFFFE163F4A), Error: Bus Reset
>>> : Failed to reconnect
>>>
>>> mythfrontend.log (when I tried to watch the recording):
>>>
>>> 2009-06-18 08:35:37.394 AFD: Opened codec 0x191f2e0, id(MPEG2VIDEO)
>>> type(Video)
>>> 2009-06-18 08:35:37.394 AFD: codec AC3 has 6 channels
>>> 2009-06-18 08:35:37.394 AFD: Opened codec 0x18a8e40, id(AC3)
>>> type(Audio)
>>> 2009-06-18 08:35:37.627 [mpeg2video @ 0x7f70851d2e90]00 motion_type
>>> at 105 50
>>> 2009-06-18 08:35:37.634 [mpeg2video @ 0x7f70851d2e90]Warning MVs not
>>> available
>>> 2009-06-18 08:35:37.674 [mpeg2video @ 0x7f70851d2e90]00 motion_type
>>> at 47 6
>>> 2009-06-18 08:35:37.677 [mpeg2video @ 0x7f70851d2e90]Warning MVs not
>>> available
>>> 2009-06-18 08:35:37.784 [mpeg2video @ 0x7f70851d2e90]ac-tex damaged
>>> at 44 45
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]skipped MB in I
>>> frame at 1 19
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]ac-tex damaged
>>> at 0 44
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]ac-tex damaged
>>> at 0 45
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]invalid mb type
>>> in I Frame at 0 46
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]ac-tex damaged
>>> at 0 47
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]invalid mb type
>>> in I Frame at 0 48
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]invalid mb type
>>> in I Frame at 1 49
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]invalid mb type
>>> in I Frame at 0 50
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]invalid mb type
>>> in I Frame at 0 51
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]ac-tex damaged
>>> at 0 52
>>> 2009-06-18 08:35:37.785 [mpeg2video @ 0x7f70851d2e90]ac-tex damaged
>>> at 0 53
>>>
>>> My Myth version is 18722 (0.21.20080304-1), and my kernel is
>>> 2.6.27.9 x86_64. Any ideas on what these mean? What else should I
>>> be looking for to help diagnose this problem?
>>>
>>> Thanks,
>>> Harry
>>>
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>
>> Here's an update on what I'm seeing: I successfully recorded a show
>> on one channel the other night, so last night I setup another
>> Firewire recording on another channel. That one failed with the same
>> errors above. So, why would 1 channel work and the other one not?
>> Could it be the 5C encryption? I was under the impression that once
>> the signal came into the box, the signal/stream is unencrypted and
>> the output is sent out to the box outputs (HDMI, Component Video,
>> Firewire, etc.).
>>
>> Any thoughts/ideas/things to try?
>> Harry
>>
>
> Your backend failed to connect to the stream and a reset of the
> firewire bus did not fix the problem. Sounds like you have the capture
> device misconfigured in mythtv-setup. I would go into the firewire
> device settings and change it from point-to-point to broadcast and set
> the rate to 100 mhz to be safe.
>
> You might also try turning off the 'reset firewire bus' option since
> you are priming the connection with the script you run.
>
> Sometimes, as in my case, a new firewire port on a card is required
> but since you can see your stb thats not the issue.
>
> W.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
Currently, my device settings are already set to Broadcast and 100mbps.
I also have "Disable Firewire Reset" checked under General Settings.
Should I try changing something in these?
Thanks,
Harry
More information about the mythtv-users
mailing list