|
|
|
RobertT:Perhaps offering survey respondents 1 month free T-box subscription would assist in getting some responses.
Here is a crazy notion, lets give peace a chance.
Here is a crazy notion, lets give peace a chance.
KiwiNZ: ... I have checked the unit for heat and it's quite cool ...
RobertT: ... Perhaps if you were to post a message on the T-box directing people to a URL for a customer survery where you also posted the information in your post above would help get to the heart of the number of people experiencing issues...
OldFart: Look at the sequence of events:
OldFart: Telstra hierarchy (think General Melchett) sit clueless 35 miles behind the lines.
OldFart: Oh yes, my favourite quote from a service call last month. In answer to the question of how often I have to reboot the machine, I responded that it was at least weekly. "Oh, well Telstra regard that as normal operation," was the reply. "You'd need to be rebooting several times a week for them to consider there was a problem." Sheesh!!
ChristineNZL: I also doubt only 2% of customers are havinbg problems - more likely only 2% bother to complain. I would like to know what is considered a "heavy user"? We probably record on average 3 or 4 programmes per day and we have had lots of problems. So is 3 or 4 programmes a day "heavy"?
DonGould:ChristineNZL: I also doubt only 2% of customers are havinbg problems - more likely only 2% bother to complain. I would like to know what is considered a "heavy user"? We probably record on average 3 or 4 programmes per day and we have had lots of problems. So is 3 or 4 programmes a day "heavy"?
Based on what Gary said, I think we can assume that a heavy user is a 'feature rich' user.
I'm sorry, I don't know enough about this box having never actually played with one. However, most of these sorts of systems are impacted by 'feature combinations'. Often a programmer will add a 'nice to have' feature using a collection of existing system routines because it became apparent to them during the development that they could. Some times this works well, but some times they over look code execution required to perform the task. What you think is just a 'press of the button' might be calling dozens of internal functions that were never really properly designed to interact.
In applications like TBox you have 'timers' that execute code internally from time to time. If you've selected a combination of features that cause execution of 'bad code' then things go pear shape.
Gary has said that the unit suffers memory issues. To me that's a red light that it has routines in it that aren't well coded (and perhaps they didn't need to be for their original purpose). For example, some times a programmer doesn't 'clean up' a process properly because he knows that another aspect of the system will clean it up later. Problem then occurs that the function gets called way more often than was expected before the clean up process hits and the machine gets swamped. Again, I don't know what's really going on, I can only speculate, but 20 years of programming, I have a few clues how this stuff goes off the rails.
ChristineNZL: Thank you Don -I think I kind of understand what you are saying.
Here is a crazy notion, lets give peace a chance.
TelstraClear: Hi everyone,
TelstraClear: Thanks for the feedback and questions. Rather than make a lot of posts quoting everyone, I’ll make one post covering the important points.
TelstraClear: We can understand your frustration at the time it has taken to get the update ready. We’re frustrated as well. We’re frustrated with the new issues that have arisen. We’re frustrated that we haven’t been able to issue the release as we’d planned. But we’re continuing to work through the issues and, as stated, we intend to get the update right so that we make things better and not worse or even different. It will be better, and that’s from the top TelstraClear management level. We are taking this very seriously and will be getting it sorted.
TelstraClear: The early version of the update that was shown, as some have mentioned, to those who visited the broadcast lab will, as they saw, improve the performance. However, during intensive testing of that update and subsequent iterations in a real-world environment we discovered other issues that would frustrate customers just as much as the issues it fixed.
TelstraClear: While we are confident that Digisoft.tv (the European software developer) has now ironed out most of those bugs and we’re close to being able to test a release in the real-world environment, we’re not 100% certain. Until we are completely confident that the new software will deliver as promised we can’t commit to a release date. As noted, and we admit, we were wrong with the expected timing of the release being ready at the end of the RWC.
TelstraClear: As also noted, during real-world testing of the customer-ready release we discovered new issues that, while they would fix the issues already raised, would introduce new ones. This wasn’t good enough and we delayed the release, as updated Monday. All going well, the release will be a couple of months away at most, quite possibly less. If we have to reject the update and get it re-worked then the release date will be later. As mentioned yesterday, the update does remain a priority for both us and Digisoft.tv and many hours both here and in Europe are being put into getting it right. As soon as we have more to tell we’ll update you.
TelstraClear: It’s highly unlikely that the update will take another 6-12 months as some have speculated. It’s quite likely to be a few months. However, given the issues that have been identified in earlier iterations of the release as mentioned, 3-4 months is also possible. We’re not denying that and giving you all the available information. We’ll have more certainty in 4-6 weeks.
TelstraClear: T-Box hardware– the T-Box has plenty or memory and has high quality hardware and build. The T-Box is not an off-the-shelf PVR and has been built and developed for New Zealand. It is the only PVR in the world (that we know of) that has the features we’ve included that will enable it to become more versatile as delivery and content options evolve. The reported issues are all to do with the software, not the box design, components or build. As enhancements have been made with each of the updates, the software has ‘bloated’ and this has been found to impact on the operating system memory. The audio and video processing memory has not been affected. As mentioned, Digisoft.tv has found further ways of reducing the load on operating system memory (reducing ‘bloat’). This will help address many of the issues that have been reported, as well as improve performance and response. The new build itself will also further improve performance.
TelstraClear: Early T-Boxes v later ones– they are the same. The specifications haven’t changed. The issues that some customers have experienced are related to the software, not to the age of their T-Box. The codes ‘D’ and ‘E’ relate to the manufacturers batch numbers. Our customer service records show no performance or internal hardware differences between the batches. While the manufacturer may have changed some brands of electronic components between batches, the architecture and specifications are the same, as are the QA requirements. As one poster noted, the manufacturer made a unilateral minor change to the external facia to improve the remote angle of response. In a few cases, some customers may experience IR interference. Moving the T-Box back into the cabinet or further away from their TV reduces the likelihood of interference.
TelstraClear: Number of issues– about 25% of our tens of thousands of cable TV customers have a T-Box. The percentage of customers that are reporting issues is very small (about 2% few percent). This is in line with levels of other computer-based technologies, including other PVRs and recording devices. We have logged the issues and, as stated, we are working to address these. All of these reported issues have been identified as relating to the software (apart from the occasional problem with a faulty connection in the cable to the home). As stated, the update under development will address the issues that most users find the most frustrating. The software has not performed as well as we or you would have liked. This is a new device and there have been some teething issues. These are being worked through. We remain committed to the T-Box. As mentioned, a few of the issues some customers have reported have been caused by faults in the cable or connections to the individual home. If you think this might be causing you some issues please call our faults team and ask them to check this. The number is: 0508 888 800.
TelstraClear: Delay in this update– based on feedback from Digisoft.tv we had high confidence that the performance release would be ready to upload to T-Boxes about now. However, our real-world testing of the update identified new issues. It did markedly improve performance, but also caused other unwanted behaviour and did not properly address existing issues. The software is being re-worked to ensure that it delivers the improvements expected.
TelstraClear: Heavy users’ experience– the amount of use or ‘work’ that the T-Box does is related to the operating system ‘bloat’ and impact on memory. A few small memory leaks have also been detected and updated device drivers to address this are being sought and incorporated. Together, these factors mean that light users (and those who regularly power cycle their T-Box) in general experience fewer issues. This is not always the case, as some unrelated behaviours occur anyway. These are also being addressed in the next and future updates.
TelstraClear: Early termination– if you have experienced problems with your T-Box, and have previously logged this with faults, and have read the information above on how we’re working Digisoft.tv to make improvements, but still feel you would like to return your T-Box, please email me with your customer number and contact details. I’ll ask one of our customer help staff to contact you and talk about the options on a case-by-case basis.
TelstraClear: Hope this is useful, Gary
|
|
|