[mythtv] firewire branch status?

Steven Adeff adeffs.mythtv at gmail.com
Thu Apr 12 18:19:46 UTC 2007

On 4/12/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> On Thu, 2007-04-12 at 11:26 -0400, Steven Adeff wrote:
> > Hi guys, been running this a while and its been great. One thing I
> > noticed, the box got reset  and it changed ports. Myth found it fine
> > with the GUID system but recordings didn't work. I had to run the
> > firewire_tester -B command a couple times on the box at the new port
> > to get it working again. Is the method firewire_tester uses included
> > in part of how Myth internally handles firewire recordings?
> Change the "#if 0" in linuxfirewiredevice.cpp's ResetBus()
> to "#if 1" and it will do this for you automatically.
> This will glitch any other firewire recordings which are
> ongoing, but if you are only using one firewire recorder
> this is not an issue.

will it do this every time it looks to record or only when it doesn't
get a signal? I'd prefer to only have to worry about it when the box
gets reset (which seems to be rarely).

Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -

More information about the mythtv-dev mailing list