On 1/9/06, <b class="gmail_sendername">Steve Adeff</b> <<a href="mailto:adeffs@gmail.com">adeffs@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sunday 08 January 2006 23:34, Adam Propeck wrote:<br>> On 1/8/06, Steve Adeff <<a href="mailto:adeffs@gmail.com">adeffs@gmail.com</a>> wrote:<br>> > On Sunday 08 January 2006 21:20, Adam Propeck wrote:<br>
> > > On 1/8/06, Steve Adeff <<a href="mailto:adeffs@gmail.com">adeffs@gmail.com</a>> wrote:<br>> > > > Gentlemen, I posted this to the dev list, but haven't gotten a<br>> ><br>> > response,
<br>> ><br>> > > > I feel it might have been "lost" in the thread to the uninterested.<br>> > > ><br>> > > > I'm hoping its a trivial thing to do, I'm just not equiped to do such
<br>> ><br>> > a<br>> ><br>> > > > change<br>> > > > and am hoping one of you might be able to whip something together in<br>> > > > a few minutes for me to test.<br>> > > >
<br>> > > > One of the issues I'm tracking as part of my firewire "project" is<br>> > > > why the DCT62xx series misses recordings sometimes. Now that I<br>> > > > finally got
<br>> ><br>> > my<br>> ><br>> > > > DCT62xx<br>> > > > capturing via firewire (added a second cablebox), I think I may have<br>> > > > found a<br>> > > > way around the problem. Most people said they had to unplug the cable
<br>> > > > from the box and plug it back in to "reset" it, which is something I<br>> > > > found as well. Jeremy suggested I use gscanbus to reset the bus<br>> ><br>> > instead,
<br>> ><br>> > > > wonderfuly,<br>> > > > his suggestion was spot on allowing me to not have to crawl behind my<br>> > > > home theatre equipment anymore. I've "tested" this method of fixing
<br>> ><br>> > quite<br>> ><br>> > > > a few times as I find the connection gets lost at least once a day,<br>> ><br>> > and<br>> ><br>> > > > usually everytime no signal is collected from the box for ~2hrs.
<br>> > > ><br>> > > > I was wondering if one of you could whip together a patch that<br>> > > > will force a reset on the Host(Port)/Node that the firewire<br>> > > > connection
<br>> ><br>> > is<br>> ><br>> > > > on<br>> > > > before every recording and every entry into LiveTV?<br>> > > ><br>> > > > This may also help channel changes, so perhaps placing the bus reset
<br>> > > > before<br>> > > > Myth changes the channel would be a good place for this step to go.<br>> > > ><br>> > > > Thanks for your time,<br>> > > > Steve<br>
> > ><br>> > > Who is the cable provider you're using? I haven't noticed this with<br>> ><br>> > Charter<br>> ><br>> > > really. Granted I just got mine setup recently.<br>> >
<br>> > Comcast, if its not an issue for all providors/boxes, it can be an option<br>> > in<br>> > mythtv-setup. I just would like to see if it does fix the problem.<br>> ><br>> > --<br>> > Steve
<br>> ><br>> ><br>> ><br>> huh. does this happen to the STB if it's not hooked up via firewire to your<br>> Myth box? I mean, does it lock up occasionally still? I'm new to this STB,<br>> so please bear with my questions.
<br>><br><br>nothing locks up, the computer just stops being able to receive the mpeg<br>stream over firewire until the bus is reset. this can occur by unplugging the<br>firewire cable and plugging it back in, or using gscanbus's reset bus option
<br>(which sadly is GUI only).<br><br>Why it does this, I don't realy know, but it does, and from my understanding<br>it happens to quite a few folks, so I figure I'd try and find a solution.<br><br>--<br>Steve<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br>Happens to me as well.<br>