TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.



Pages:1



Remote Scheduling

(Click here to view the original thread with full colors/images)



Posted by: Popasmurf

I know that this feature will be enabled VIA HMO. My question, is how hard would it be for TiVo to enable this same feature via Dialup in the HMO so you could do it either way? One of the people I work with has a Replay unit, and I noticed that they have the remote scheduling, and it is done VIA Dialup.



Posted by: PrimeRisk

It shouldn't be any technical issue at all. It is a service issue though. Most TiVos call in once every 27 hours or so to get program data. To support remote scheduling with a two hour response time would require your TiVo to phone home every 2 hours. TiVo pays for the connects from its customer base and increasing the dial-ins by a factor of 13 or so would cost them money. Of course, if you were willing to wait for the next regularly scheduled dial-in, this would be just fine, but most people would probably want better response time than that.



Posted by: mabittin

as an ex-Replay user.....even with Replays hooked up via ethernet connection, the remote scheduling is only updated once per day (at the nightly connect - and the web interface is PAINFULLY slow)



Posted by: mikedaly

quote:
Originally posted by mabittin
as an ex-Replay user.....even with Replays hooked up via ethernet connection, the remote scheduling is only updated once per day (at the nightly connect - and the web interface is PAINFULLY slow)

Yah... from what I've heard/read from current/past Replay users, they are not the model TiVo should use for how a "remote scheduling" system should work. Yet another example of "looks good on a feature list, but once you use it..."

You're right, there probably isn't a technical reason for limiting remote scheduling to broadband users only. But since the calls DO cost them money, this is one way to nudge people towards broadband (which presumably is cheaper for them to support, since there are no payments to UUNet). Likely more of a marketing than technical decision. jmho.



Posted by: aindik

quote:
Originally posted by mikedaly
Yah... from what I've heard/read from current/past Replay users, they are not the model TiVo should use for how a "remote scheduling" system should work. Yet another example of "looks good on a feature list, but once you use it..."

You're right, there probably isn't a technical reason for limiting remote scheduling to broadband users only. But since the calls DO cost them money, this is one way to nudge people towards broadband (which presumably is cheaper for them to support, since there are no payments to UUNet). Likely more of a marketing than technical decision. jmho.



It doesn't require broadband, per se. It requires that the TiVo be connected to a home network that has always-on internet access. TiVo doesn't care if that internet access is broadband or narrowband, as long as it's always on.

You will be able to use remote scheduling as long as you don't use the TiVo modem.



Posted by: MighTiVo

I don't understand why remote scheduling won't be available with a 24-48 hour lag time for Series 1 users.



Posted by: dcorsi

Because for how long can Tivo be expected to add and add features to an old unit which never claimed to ever support it? I am sure Tivo *could* do this but I have been so pleased by the changes from 1.3 to 2.0 to 2.5 to 3.0 and stunned to have gotten them for free. The chain has to break at some point because Tivo has Series 2 units to sell. The other choice is Tivo to go out of buisness and then we all suffer.

Series 2 remote scheduling as I understand checks every 15 minutes which is fantastic and that along with MP3 and photo streaming is why I upgraded with the recent offer.





vBulletin Copyright ©2000 - 2009, Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2009 - Created by Stefan "Xenon" Kaeser Modified by Adam J. de Jaray