[sfhub]

EDIT:

This appears to have been fixed. Now have guide data through 4/21

---

Usually I have 12 days of guide data.

Usually this gets fixed before I run out of guide data.

Usually this gets fixed faster if Lyndon sees it and forwards on.

My 5040 has successful net connect and no error messages.


PS I think as a result of this problem I'm also net getting the

"next day" last minute changes. For example yesterday ABC

changed out Miracles at 10pm and replaced with repeat of

The Practice. Usually my unit would pick this change up the

night before. So as a word of caution if the networks make

any last minute changes, you'll probably need to account for

them manually.

 

[asinshesq]

ok, who will be the first to claim this is the beginning of the end. (No, I'm not suggesting it -- I remain confident that the replay service will have a long life -- but I am equally confidence that the paranoid among us will jump on this little tidbit.)

 

[BaysideBas]

They already did last month when the Replay servers hiccuped

 

[tluxon]

Just pulled my Replay out of the river - anybody know how to get it working again?

 

[sfhub]

The same thing happened a month or two ago, so my first inclination

is this is a repeat of the same problem.

 

[Jeff D]

A pvr is a perfect platform for the "push" technology. I'd love to have the replay wait for the information to come to it rather than having the replay initiate the connection.


Live recording changes via the web, channel lineup changes as they are announced, etc. That would be cool.

 

[Jerry1726]

Quote:

PS I think as a result of this problem I'm also net getting the "next day" last minute changes. For example yesterday ABC changed out Miracles at 10pm and replaced with repeat of The Practice. Usually my unit would pick this change up the night before.

Yeah, I stated the same example in the thread of "Once Again"-this sems to happen every month as I said there. The only solution I have found is to wait it out.

 

[sfhub]

Quote:

Originally posted by tluxon Just "pulled" my Replay out of the river

Quote:

Originally posted by Jeff D A pvr is a perfect platform for the "push" technology.

Were you suggesting tluxon "push" his Replay back in the river?

 

[majortom]

Quote:

Originally posted by Jeff D A pvr is a perfect platform for the "push" technology. I'd love to have the replay wait for the information to come to it rather than having the replay initiate the connection. Live recording changes via the web, channel lineup changes as they are announced, etc. That would be cool.

It would be very difficult for RePlayTv to contact boxes in the field, instead of having those boxes contact it. You would have problems with firewalls, dynamic IP addresses and other issues.


/carmi

 

[Foxtrot-Yankee]

Quote:

Originally posted by majortom It would be very difficult for RePlayTv to contact boxes in the field, instead of having those boxes contact it. You would have problems with firewalls, dynamic IP addresses and other issues. /carmi

Wrong. If a Replay can be contacted to receive a show via Internet Show Sharing, they can drive right through the same channel to trigger a download of channel info.


--Fox

 

[morrisdl]

push could be done (example Internet Show Sharing), but it would be much more problemmatic. I would dare say that Internet Show Sharing is probably the most difficult aspect of ReplayTV to get working (from what I hear on this board). I would bet most users dont or havnt used it. Making updates dependant on this would not be good.


Maybe a combination of push and pull would be best? It would be cool if your replay would subscribe to updates for the channels that you have records setup. Then get complete guide data nightly. This would provide additional functionality to those that have it setup correctly (or a friendly firewall).

 

[honus87]

Yes, but lots of people have ReplayTVs that can't be contacted to receive a show via ISS because they haven't gone to the effort to set it up, and many people have problems getting it set up correctly if the posts here are any indication.

 

[reedg01]

Quote:

Wrong. If a Replay can be contacted to receive a show via Internet Show Sharing, they can drive right through the same channel to trigger a download of channel info.

I disagree.


For ISS, you use your IP address from your ISP, and then open up a port in the firewall to a particular IP address in your internal network. If you have multiple Replays, you have to do this for each one, using different ports for each Replay.


For this to work for push updates, SB's successor would have to maintain a database of all Replays, with their IP address and unique port number. You would have to notify them of any change in either attribute. My ISP does not guarantee me the same IP address all the time, but my service always works, because no network traffic is being triggered from outside.

 

[moyekj]

Quote:

Originally posted by honus87 Yes, but lots of people have ReplayTVs that can't be contacted to receive a show via ISS because they haven't gone to the effort to set it up, and many people have problems getting it set up correctly if the posts here are any indication.

Also, some people (like me) use their work place as their ISP and are therefore sitting behind corporate firewall such that ISS will never be possible.

 

[toots]

Well, I came home tonight, checked the living room ReplayTV, and sure enough, the guide stopped on 4/17.


So, I figure, this is it; it's the end of the world. Do a 411-Zones, and sure enough, it hasn't done a successful update in over 24 hours.


Yep. My ass is totally gonna fall off now.


So, I do a 243-zones and force an update. Now, I have guide data to 4/21.


Guess I gotta screw my ass back on now.

 

[Markito]

Yeah, but now it has a crack in it.

 

[Belial6]

The simplest way for replay to do a push of show data is to use email. Email is basically free. Everyone with an ISP has email. All replay would need to do is have an email address of file, and when a change is made, send an email to the corrisponding address that has the data necessary to set up a show. The email could look like:


Subject: Replay show request [xxx-xxx-xx-xxx]

Body: A new recording has been requested.


Channel: 244

Date: 04/09/2003

Start Time: 8:00 pm

Length: 60 Minutes

Quality: High


2442003040920:0060High


...and so on for any and all variables. The ReplayTV unit would then just need a small pop3 client. The user could enter a servername/username/password as well as a connection interval into a configuration screen on the replay. The replay would connect to your ISP's email server as often as you want. Replay wouldn't have to worry about thousands of connection a minute, and users with dynamic IP addresses could still use the push technology of email. If you didn't want to see the emails from replay in your inbox, there are hundreds of free email providers. You could just sign up for one and use it exclusively for your ReplayTV. If security is necessary, they could generate a random password every night that is set on the ReplayTV unit during the nightly connect, then the unit would know that the email wasn't spoofed.


I would rather just set a password on the unit, and change it manually when I needed though. By not making the password updated by the server, it would open up the ability for people to write their own ReplayTV remote programmers.

 

[sfhub]

Umm, how is this push? Your replay unit still needs to pull the email

from the server where the mail was sent. I understand you've proposed

a method for greater pull frequency which if set to high enough granularity

will appear to be push from the end-user perspective but it is not push

from network perspective.

 

[asinshesq]

Quote:

Originally posted by toots ...Now, I have guide data to 4/21...

Oh no. The service is going to end 4/21. Six days after the auction. EXACTLY SIX DAYS -- that can't possibly be a coincidence. I knew it all along. I kept telling lizard_boy this was the end. Doorstop city. What will we do? WHAT WILL WE DO?