Separate names with a comma.
Discussion in 'TiVo Premiere DVRs' started by timstack8969, May 6, 2010.
When will the "TIVO Premiere" receive the next software Update?
According to TiVo, the next update is coming in a few weeks.
I was on the phone with Tivo support today and they told me that a software update will arrive in a few weeks, followed by a firmware update in the next month or two that will turn on the second core in the dual core processor in the Premiere.
You mean only one processor is working on the Premier XL???
Yes, only one of the two processor cores is currently enabled. More information in the Prepurchase FAQ stickied at the top of the forum.
Is there actually some firmware in the Premiere besides the boot code (ie spin the disk and start reading code from it)? I wouldn't have thought that a firmware update was necessary to shift to two processor mode. Firmware is usually just a different storage device for storing software.
Edit; Unit has 8MB Flash ROM. I'm sure there's a good reason why, but its not obvious to me.
I was told the same thing by a very informative tech. hopefully this will help the speed big time.
Ok let me ask this.
What is the most current version of the software?
The current version is 14.1c-01-3-746.
According to TiVo, the next software update is due within the next week:
"@cradix Focusing on both. Within a week I expect. Next time you freeze send me email with serial number and date/time of freeze. "
"@TivoDesign - So tired of my Premier freezing! When is the next update coming!? Focusing on freezing, or will performance boost, too? "
- Source: http://twitter.com/tivodesign
if this enables dual core and fixes the hd lagggg problem I will buy the day it comes out..
Should be any day now.
Can't wait using sd menus, only benefit now is 1 cable card. Activate that second core 1st then the software!
How is having 1 cable card a "benefit"? I have been using an HD for 3 years with one multistream card.
It seems to me if people are complaining about bugs, non-HD menus, reboots/freezes/crashing, and slow HD menus (only), activating the second core is the least important step right now. And "activating" the second core is not some magic pill... unless the tivo is already overloaded with multi-threaded tasks AND the UI software is already multi-threaded, then having a second core will make little to no difference.
As long as we are speculating in futility, this seems are more logical approach:
1) Fix rebooting/freezing/crashing
2) Fix other bugs
3) Finish the HD interfaces
4) Optimize the HD interface code
5) Thread the HD and other code
6) Activate second core
( 7) Now release the TiVo Premiere )
Actually, activating the second core may reduce reliability without significantly increasing performance.
1) Multi-threaded apps are complicated and difficult to debug.
2) The slow menu are likely a problem with flash or the way it is being used.
There are probably way to many calls.
3) The images are likely slow because they are being retrieved from the network with no caching. It may be from disk IO, but that is less likely.
This suggests, streamlining the use of flash and caching images would be a much better way to get the performance up. If you are I/O bound, adding cores is useless.
But he was acting as if you can't use a single M card "before", which you CAN in the HD.... Since he wasn't listing what he was comparing to, I was being facetious
I agree with everything you just said. I doubt the TiVo is I/O bound, though... unless it starts swapping or something due to low RAM and horribly bloated HDUI Flash stuff (does the TiVo even have a swap partition or file?)
It might be disk I/O but it also might be network bound to get images etc.
Trips across the net have a huge latency compared to anything local.
I have said it before and i will say it again, the user experience should not depend so much on the Internet connection any user may have, as TiVo has no control over that connection. I think caching as much as possible and never wait for an Internet response for pictures, if they come on great if not so what don't make the user wait for them.