[mythtv-commits] Ticket #5278: Firewire Uses Bad Port Number and Fails
MythTV
mythtv at cvs.mythtv.org
Sun Apr 18 00:35:27 UTC 2010
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi@… | Owner: jarod
Type: defect | Status: closed
Priority: minor | Milestone: 0.24
Component: MythTV - Recording | Version: 0.21
Severity: medium | Resolution: fixed
Mlocked: 0 |
---------------------------------+------------------------------------------
Comment(by eric@…):
Replying to [comment:45 robertm]:
> This message is consistent with 5C status changing in the program, which
can and does happen.
I know, but I don't think that's it in this case.
I had a bunch of channels I couldn't capture and I assumed it was a 5C
issue, even though the diagnostic screen for the STB said the channels
weren't enabled for 5C. However, after switching from a TI firewire
controller to a VIA one I can get those channels now.
I still think it's something to do with the way the box changes port
numbers.
> Have you captured in any other program to determine that your firewire
connection is otherwise functional and rock solid?
I've been recording over firewire from this STB for quite some time.
Probably close to two years. (My first comment on this ticket says
"Changed 19 months ago by eric at ...") It's always been "functional" but
never "rock solid".
Since upgrading to .23, I haven't yet caught a failure like this while it
was happening. It used to be that restarting mythbackend would get things
working again. (Which, again, suggests it's not a 5C problem.) I'm going
to need to keep an eye on it and see if I can reproduce that.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:46>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list