If Not Dst, Why 6.3c?

[sluciani]

According to the canned message re: DST I'm sure we all received today, only version 6.3 was needed to compensate for the early switch to DST. I read that to mean 6.3x. If that's the case, I wonder what 6.3c was actually intended to fix? /s

[JimSpence]

And you believe that the canned message on the TiVos was correct? I wondered the same thing, but took it as sloppy reporting.

[sluciani]

You could be right, but it was pretty specific regarding other models. /s

• DIRECTV HD DVR HR10-250 (HD): 6.3 (or later)
• Philips DSR6000, Sony SAT-T60, Hughes GXCEBOT: 3.5b
• DIRECTV DVR R10: 6.1a
• All other Series2 DIRECTV DVRs with TiVo Service: 6.2a

[litzdog911]

Yep, Jim's right .... just sloppy reporting. 6.3c adds the DST fix to the previous 6.3b release.

[stevel]

Well, a little birdie at TiVo told me that the original 6.3 had the DST fix, or at least that's what the developers told him. Perhaps he was misinformed or misunderstood, I dunno. I'm in the "6.3c only" camp, myself.

[Philly Bill]

I still have 'b'. If the clock is off an hour tomorrow morning I'll plug in the phone line I guess.

[litzdog911]

I still have 'b'. If the clock is off an hour tomorrow morning I'll plug in the phone line I guess.

Yep, let us know.

[MisterEd]

www.tivo.com/dst states: "DIRECTV HD DVR HR10-250 (HD): 6.3 (or later)." Are they wrong as well?

[tnedator]

Wish I had read this sooner. I had the 6.3c slices downloaded on one 10-250, but not the other. Since I had read some iffy stuf, I hadn't run slicer to integrate them. I just did now, but it seems like it might not have been necessary.

This might also explain why the 6.3c update was pulled from the stream, and nobody seems to be getting it on call ins. It must not have been necessary for DST and they might have found some bugs, and therefore pulled it.

[sluciani]

Wish I had read this sooner. I had the 6.3c slices downloaded on one 10-250, but not the other. Since I had read some iffy stuf, I hadn't run slicer to integrate them. I just did now, but it seems like it might not have been necessary.

This might also explain why the 6.3c update was pulled from the stream, and nobody seems to be getting it on call ins. It must not have been necessary for DST and they might have found some bugs, and therefore pulled it.

That's what I'm thinking as well. Except for the long OTA audio dropouts, I've had no problems with 6.3a, and 6.3b was flawless on all four of my HR-10's. With 6.3c, I'm now experiencing sporadic and sub-second audio and video "hiccups", whether Sat or OTA. Maybe 2-3 per one-hour show.

Of course these could be transmission-related and the timing a coincidence, but for now, I choose to blame 6.3c! :)

For those on 6.3a or 6.3b, if you wouldn't mind checking your system info to see if DST is enabled, I'd appreciate knowing. Thx.

/steve

[beanpoppa]

My HR10 with 6.3b is showing the correct DST time this morning. My SD Tivo's with 6.2 are an hour behind. So, 6.3c was NOT for the DST patch.

[sluciani]

Thanks for reporting this. So my original question still stands. What was the "C" patch intended to fix?

/steve

[iaflyer]

TivoJerry also said you needed 6.3 (or later) in this thread:

http://www.tivocommunity.com/tivo-vb/showthread.php?t=343564

Sooo... like everyone else, why the C patch?

[drew2k]

6.3c also includes fixes for the HD-TiVos to handle the enhanced guide data is delivering. Without the "c" upgrade, we'd likely be running into the same not-recording problems experienced by many HR10 users this past January.

[Mark Lopez]

6.3c also includes the new and improved audio dropouts. :(

[MisterEd]

LOL .... I've had zero problems of any type (reboots, missed recording, dropouts etc) with both B & C. (Knock Plastic). Box is heavily hacked as well. Used slicer for all upgrades, multiple drives etc. 6.3c also includes the new and improved audio dropouts. :(

[JohnDG]

6.3c also includes fixes for the HD-TiVos to handle the enhanced guide data is delivering. Without the "c" upgrade, we'd likely be running into the same not-recording problems experienced by many HR10 users this past January.

Reference?

jdg

[sluciani]

6.3c also includes fixes for the HD-TiVos to handle the enhanced guide data is delivering. Without the "c" upgrade, we'd likely be running into the same not-recording problems experienced by many HR10 users this past January.

You may be 100% right, but what's your source for this information? I never had any guide problems with 6.3b on four different HR10's. Many posters still on 6.b are reporting no problems whatsover for the past few days on many of the threads.

If the "hiccups" myself and others are experiencing are 6.3c-related, some fundamental change to the a/v processing or disk i/o was made, not changes to the database, IMHO.

/steve

[GreyGhost00]

6.3c also includes fixes for the HD-TiVos to handle the enhanced guide data is delivering. Without the "c" upgrade, we'd likely be running into the same not-recording problems experienced by many HR10 users this past January.
Call me skeptic, but I've not run into any "not-recording" problems on 3.1.5f and my Tivo has received the "enhanced guide data" ...

[sluciani]

Tivojerry confirmed (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4955860&&#post4955860) that all versions of 6.3 had the DST fix. He did not know what the "c" revision was supposed to be addressing. Looks like D* may have broken something that was already fixed, at least in my case, if the "hiccups" I'm seeing are 6.3c related. 6.3b worked flawlessly on my 4 HR10's. Sigh.

/steve

[phox_mulder]

If so, 6.3 sped up the menus and had the DST fix.

6.3a fixed a problem with multiple dishes not integrating properly.
(some locations get their locals off a lone satellite way low in the sky)

6.3b fixed the audio dropouts on OTA HD (FOX specifically)

(I might have reversed "a" and "b")

6.3c perhaps is for the enhanced guide, missed recordings, rebooting problem?


Just pure speculation of course.

Too bad we don't get revision notes.


phox

[GreyGhost00]

Looks like D* may have broken something that was already fixed, at least in my case, if the "hiccups" I'm seeing are 6.3c related. 6.3b worked flawlessly on my 4 HR10's. Sigh.
I think it's pretty much been proven that the 6.x code was a port from the 6.x version for Series2 rather than from the stable 3.1.5 for the HR10-250's, thus resulting in a bunch of regression errors. There's probably more.

[sluciani]

Based on my experience and comments from others in other threads, "b" definitely appears to have been the least problematic 6.3 release to date. Just as a matter of curiosity, is there any "inside" info on what the "c" patch was intended to fix or improve? Earl? Anyone?

/steve

[beanpoppa]

From what I remember, 6.1/6.2 is a branch from the old 4.x used in the standalone- hence the inclusion of the HMO/MRV code. 6.3 is a branch from the 7.x code used in the standalone- hence the inclusion of the HME code (which wasn't in 4.x) but they did exclude important parts of the HMO/MRV code.

In my experience, the 6.2 code on my SD DTivo's has been rock solid. Despite being heavily hacked with HMO, MRV, MFS_FTP, tivoweb, bufferhack, caller id, vserver, etc, I never have issues with lockups or random reboots. The only time they ever reboot is when I use tivoserver to copy a bad video stream onto the box. My HR10, OTOH, with 6.3, is much more flaky. I got lots of lockups under 6.3a. Less so with 6.3b. But I still have issues with lockups when I record OTA channels with poor signals.


I think it's pretty much been proven that the 6.x code was a port from the 6.x version for Series2 rather than from the stable 3.1.5 for the HR10-250's, thus resulting in a bunch of regression errors. There's probably more.

[Doright]

I've got 6.3b on 2 of my HR10's and 6.3c on one of them.
They all seem to be working just fine.

A couple of weeks ago I was forcing calls daily to try and get the "b" to "c" upgrade before DST. Nothing ever happened. But all is well anyway...