<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 2:59 PM, Peter Bennett (cats22) <span dir="ltr"><<a href="mailto:cats22@comcast.net" target="_blank">cats22@comcast.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<br>
<br>
I actually created a patch for this in Mythtv 0.24, that solved the
problem. The patch failed in 0.25 and the problem had gone away for
me by then. The patch was a kludge work around - i.e. closed and
opened the firewire port if the error occurred. That action
recovered and recording could continue.<br>
There is a comment in the patch from andy that suggests that the
issue may be related to the VIA chipset.<br>
When I was having the issue I did look at verbose logs and could not
find any cause. It seemed that after recording for a few seconds it
would stop receiving data. One thing - the bus reset that is in the
code and gets called every few seconds when this error is happening
- does not fix the problem, but seems it may make it worse. I tried
with that option both on and off and that did not help.<br>
<br>
The general view from most mythtv developers seems to be that
firewire is dying out. I think the cable companies now have a waiver
that lets then give a DRM protected ethernet stream instead of
firewire.<br>
<br>
Let me know if you need some help testing firewire changes.<br>
<br>
Instead of putting more time into firewire, is anybody investigating
HDMI capture? There are HDMI capture cards available now and I have
seen a couple with Linux drivers. They seem to be expensive. I know
that would not work if the HDMI was encrypted, however Comcast has
the small "adaptors" with HDMI output and I wonder if they use
encrypted output. How does one check if the HDMI stream is
encrypted?<span class=""><font color="#888888"><br>
<br>
Peter<br>
<br>
</font></span></div>
<br></blockquote><div><br></div><div>As an aside, I have been using firewire for many years (I'm going to guess about 8 years or so). This is my current firewire card, and I really hope we don't lose support because it is my only capture method (my cable company is kind enough to put everything I subscribe to over firewire with no copy restrictions) and works relatively well, although I occasionally have to reboot the machine when it fails on recording, which has happened a bit more frequently lately.<br>
<br>Firewire info:<br>03:05.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) (prog-if 10 [OHCI])<br> Subsystem: Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller<br>
Flags: bus master, medium devsel, latency 64, IRQ 20<br> Memory at febff800 (32-bit, non-prefetchable) [size=2K]<br> Memory at febf8000 (32-bit, non-prefetchable) [size=16K]<br> Capabilities: [44] Power Management version 2<br>
Kernel driver in use: firewire_ohci<br> <br></div></div><br></div></div>