My guess is they'd love to do this, and that it's more likely management (who probably don't read here) who would need to be convinced.
Suggestion for D* Reps out there...
I know that there are people from D* who read these posts. I'm told you don't want to make yourself known because of the flame war that would start. I get that.
Still, I'd like to suggest that D* make an effort to reach out to the people here, especially disgruntled R15 and HR20 owners. Don't make us complain to you, come to us. Don't make one person responsible for disseminating everything (although he does a great job, no disrespect intended).
Here are a couple of ideas to help mend the fence, increase customer satisfaction and improve the product:
1) Weekly tech chat. Real developers talking about real problems. We promise that it won't turn into "angry peasants with torches" time and they promise, no BS. This would be a line to the coders who are working so hard to make this thing right. See what the issues are. Get to understand each other.
2) Occasional chat with the marketing people. Let us know what features are tops on their lists for release, tell them what's tops on ours. Why not tell them person-to-person if (for example) you don't want any more shopping channels? Let them hear it.
3) Let more people in on the process. Earl does a great job but there are others here who have proven (to me at least) to be the sort of people who want to improve things not just bash.
4) A couple of changes to the software. These would be developer-level things and purely opt-in. They've been mentioned before, I won't take credit: logging via ethernet/phone line and opt-out to the latest firmware updates. Add to that the ability to opt-in to more experimental builds.
I've said before that there's a real opportunity here for D* to reach out to the community, to help change opinions out there and build some goodwill among the trendsetters.
Whad'ya say?
Still, I'd like to suggest that D* make an effort to reach out to the people here, especially disgruntled R15 and HR20 owners. Don't make us complain to you, come to us. Don't make one person responsible for disseminating everything (although he does a great job, no disrespect intended).
Here are a couple of ideas to help mend the fence, increase customer satisfaction and improve the product:
1) Weekly tech chat. Real developers talking about real problems. We promise that it won't turn into "angry peasants with torches" time and they promise, no BS. This would be a line to the coders who are working so hard to make this thing right. See what the issues are. Get to understand each other.
2) Occasional chat with the marketing people. Let us know what features are tops on their lists for release, tell them what's tops on ours. Why not tell them person-to-person if (for example) you don't want any more shopping channels? Let them hear it.
3) Let more people in on the process. Earl does a great job but there are others here who have proven (to me at least) to be the sort of people who want to improve things not just bash.
4) A couple of changes to the software. These would be developer-level things and purely opt-in. They've been mentioned before, I won't take credit: logging via ethernet/phone line and opt-out to the latest firmware updates. Add to that the ability to opt-in to more experimental builds.
I've said before that there's a real opportunity here for D* to reach out to the community, to help change opinions out there and build some goodwill among the trendsetters.
Whad'ya say?
- Status
- Not open for further replies.
1 - 12 of 12 Posts
So the next question is how do we get management to see things our way? I'm hoping all the bad press, with the links back to this site, should help us. Maybe it's lame but I'm hoping that today's the day that someone at a high level gets word of some of the bad press that's starting to mount and says, "What is this dbstalk.com? Is that one of those 'blogs' that my kids are talking about? Is it like myspace or something?" and someone in his office turns on his otherwise inert computer, types the letters D,B,S,T, etc. for him, and opens his eyes.walters said:My guess is they'd love to do this, and that it's more likely management (who probably don't read here) who would need to be convinced.
Sorry for the cynicism, I've dealt with a few upper management types in my day. I sincerely hope that D*'s management is not that clueless.
All four of these can lead to huge IP (Intellectual Property) issues and for most smart companies the risk just isn't worth it. Internet forum users are fickle at best.. all the goodwill you build goes to pot if a mistake is made. Also remember that the users here probably represent one tenth of one percent of D*'s customer base...
To be honest, I'm not sure how on earth E* has been able to do tech chats and the like for as long as they have, they've been burned on more than one occasion by sharing too much information.
To be honest, I'm not sure how on earth E* has been able to do tech chats and the like for as long as they have, they've been burned on more than one occasion by sharing too much information.
Sounds like the voice of experience there, Neil.
Not disagreeing with you, per se, only suggesting that perhaps this sort of thing can be managed in such a way that the risk is minimized. Perhaps what we're getting is the most we should expect given the legal issues, but maybe not.
I mean, I certainly am glad for the info I get here, but if problems with HR20 turn into a PR nightmare, there will be a lot more than IP issues. I have read some pretty angry posts, and any of these could potentially shape opinions and affect sales.
Bottom line (IMO) is that right now the balance between information and risk management isn't right, and it's already affecting customer satisfaction. I'm just trying to think of ways to set it right.
Not disagreeing with you, per se, only suggesting that perhaps this sort of thing can be managed in such a way that the risk is minimized. Perhaps what we're getting is the most we should expect given the legal issues, but maybe not.
I mean, I certainly am glad for the info I get here, but if problems with HR20 turn into a PR nightmare, there will be a lot more than IP issues. I have read some pretty angry posts, and any of these could potentially shape opinions and affect sales.
Bottom line (IMO) is that right now the balance between information and risk management isn't right, and it's already affecting customer satisfaction. I'm just trying to think of ways to set it right.
Because 1) They don't really give any information out, and 2) They don't care if the information they do give out is correct or not. Many of the Tech Chats are mostly pitches for new functions that may or may not come out in the future. The Charlie Chats are spins on new services that may or may not come out. You might as well be at CES for all the good this info is.Neil Derryberry said:...
To be honest, I'm not sure how on earth E* has been able to do tech chats and the like for as long as they have, they've been burned on more than one occasion by sharing too much information.
Well for me the article is half correct. I am frustrated, but I am also a software designer, so I understand. I love the Hr20, but I miss my auto overcorrection during fastforward from the Tivo. I think if DTV were able to give me equivalent functionality in that one item, I would be totally happy.
I have to assume they will eventually get the kinks worked out. What I don't see, is a way to make the experience the same as the Tivo, since Tivo's patent around the overshoot correction is pretty rock solid. That's where I think DTV should just go ahead and pay Tivo their license fee and give it back to us!
I have to assume they will eventually get the kinks worked out. What I don't see, is a way to make the experience the same as the Tivo, since Tivo's patent around the overshoot correction is pretty rock solid. That's where I think DTV should just go ahead and pay Tivo their license fee and give it back to us!
1) TiVo has to be willing to license that "feature"
2) Have you tried using the jump back option to exit FF, instead of play
2) Have you tried using the jump back option to exit FF, instead of play
I still end up having to hit jump back around 6 times when using FF 3x because the HR20 is so slow to respond to the remote.Earl Bonovich said:1) TiVo has to be willing to license that "feature"
2) Have you tried using the jump back option to exit FF, instead of play
Ditto to what ShapeGSX said. To expand on it, you never know how many jump back presses it takes because every press seems to yield a different amount of "jump back."Earl Bonovich said:2) Have you tried using the jump back option to exit FF, instead of play
Exactly! I have not been able to gauge the "jump back". I think the manual states that the jump back is 6 seconds but it is definately different everytime I press it. :whatdididHerdfan said:Ditto to what ShapeGSX said. To expand on it, you never know how many jump back presses it takes because every press seems to yield a different amount of "jump back."
Jeez, I thought I was going nuts!Mike770 said:Exactly! I have not been able to gauge the "jump back". I think the manual states that the jump back is 6 seconds but it is definately different everytime I press it. :whatdidid
Glad I'm not the only one!1 - 12 of 12 Posts
- Status
- Not open for further replies.
DBSTalk Forum
A forum community dedicated to digital bit streaming enthusiasts. Come join the discussion about programming, content, and reception, home theaters, displays, models, styles, satellites, reviews, accessories, classifieds, and more!
Full Forum Listing
Recommended Communities
