[mythtv-users] firewire with 3250

[Jim Westfall]

Eric Smith <erictsmith at gmail.com> wrote [11.21.06]:
> I did a little bit of testing with this last night and had moderate,
> but not complete success.  As far as i can tell, at the moment I have
> no choice but to try to implement something like this on channel
> change.  Why are you hesitant of doing this Jim?  I have not
> experimented much with broadcast, but what i did seemed to be
> consistent failures... and even if it worked that would not impact the
> issue below would it?

If there are folks with DCT6200s that need to do that per channel 
change priming, they likely need to be using broadcast instead of p2p.

For the SA3250 (p2p) usually the only priming you need to do is before 
starting mythbackend.  The priming puts the stb in a state where its 
always sending data and when mythbackend goes to record it basicly 
just listens in on the stream.

Your case is a little special because you are changing to a 5C channel 
which would break stuff.

jim

> 
> I am running a single SA3250HD and using both the firewire out for the
> available HD channels and the s-video out for some non-HD digital
> channels.  Quite often when switching from one of the channels being
> fed from s-video back to firewire the firewire stream is lost.  The
> channel is changed correctly almost everytime, but the STB will not
> enable streaming (as if the new channel is 5C)  In the past it seemed
> the only way to resume the connection was to unplug and replug the
> firewire cable from the cable box.  What i noticed last night was that
> some but not all of my available HD channels would work as the first
> HD channel when using the sure_change script.  For example....
> 
> 301 - HBO non HD fed over s-video
> 1421 - ABC HD over firewire
> 1460 - TNT HD over firewire
> 
> Start on 301 -> Change to 1421 (Stream is lost)
> Start on 301 -> Change to 1460 (Works)
> Start on 301 -> Change to 1460 (Works) -> Change to 1421 (Works)
> 
> I have no idea what would be causing this behavior.  Any thoughts?  Or
> things I can try?  My only other thought was to add into the channel
> change script to change to 1460 automatically if the stream is not
> successful, retest, and then if 1460 is working change back to the
> intended channel.  Obviously this is not an ideal situation, but i
> figure i can at least give it a try to determine if the behavior i was
> seeing last night is actually consistent.
> 
> 
> 
> On 11/20/06, Yeechang Lee <ylee at pobox.com> wrote:
> > Jim Westfall <jwestfall at surrealistic.net> says:
> > > I will say I have always been suspect of people using these scripts on
> > > channel change, especially on 6200 devices.
> >
> > Me too. I outline in
> > <URL:http://www.gossamer-threads.com/lists/mythtv/users/233570#233570>
> > how to simply and easily prime FireWire using firewire_tester at
> > bootup with no further pre channel-changing priming needed for 100%
> > reliable recordings. (I should have also said, though, in that
> > message, that one needs to switch to Broadcast in mythtv-setup.)
> >
> > This has nothing to do with the accuracy of channel changes, however;
> > I still face the issue of how every 20-30 recordings a FireWire-based
> > channel change will not go through right
> > (<URL:http://www.gossamer-threads.com/lists/mythtv/users/236728#236728>),
> > typically keeping the box set to the previous channel. FireWire always
> > records fine, but not necessarily the right channel.
> >
> > --
> > Yeechang Lee <ylee at pobox.com> | +1 650 776 7763 | San Francisco CA US
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users