Quote:
Originally Posted by proudx 
Your right it's not worth my time anymore, I apologize if I bothered you with my reporting. I thought it woudl be of use to the community now or in the future that might encounter this problem. Quite Frankly I'm tired of playing quality control and beta tester for products, I simply want to buy something that works out of the box, and works well. Maybe the series 3 is the better option since the drivers are more mature.

Your right it's not worth my time anymore, I apologize if I bothered you with my reporting. I thought it woudl be of use to the community now or in the future that might encounter this problem. Quite Frankly I'm tired of playing quality control and beta tester for products, I simply want to buy something that works out of the box, and works well. Maybe the series 3 is the better option since the drivers are more mature.
Having brought up the point was definitely worth it. If you can get TiVo to recognize, and potentially diagnose and correct the problem, it will have been a worthy pursuit. However, TiVo's got a LOT of irons in the fire right now, and this particular problem likely doesn't rate very high on their To Do List (pun semi-intended).
I'd actually argue that the Series3 may not be more "mature" than the TiVo HD, and going to that platform may not be your best move. TiVo made some chipset changes between the S3 and THD, for various reasons (financial, engineering, or otherwise). However, the TivoHD is most definitely TiVo's preferred platform going forward. I'd say it's a fairly simple line of reasoning that the S3 has been end-of-lifed to a certain extent, and that the TiVoHD will receive the lion's share of the engineering develop/debug cycles that TiVo allocates.
Quote:
Originally Posted by proudx 
However, make no mistake about it. What I have pointed out is a real software bug/possible bad batch of recent tivohd hardware and I would be shocked if in the next 3 to 6 months you don't see new people coming on these forums complaining about this same issue. Theres simply no way its "my enviroment" since I have tested 7 of these on no less than 7 tvs in 3 different homes with different sources.

However, make no mistake about it. What I have pointed out is a real software bug/possible bad batch of recent tivohd hardware and I would be shocked if in the next 3 to 6 months you don't see new people coming on these forums complaining about this same issue. Theres simply no way its "my enviroment" since I have tested 7 of these on no less than 7 tvs in 3 different homes with different sources.
I don't doubt there is a problem. However, until TiVo decides to take action on this item, a seemingly endless stream of reporting on the issue tends to feel like tilting at windmills.















).





