hd200 firmware is driving me nuts

[toony]

If I had a shotgun I'd take it out back!

I'm running the latest sage 7 and have updated the hd200 to the latest firmware 200909030 and it is super laggy! the menu text si all bunched up and garbled. I constantly get the circle of death and then it either freezes or if does start playing it is jumpy no matter what video I play. I have to restart the server to get it going again.
When I try the beta firmware 201007190 it runs nice and smooth excpet when it plays a video, well there is no video or audio.

I didnt change a thing, it started just recently.

Please help

[stanger89]

You have to run the beta firmware if you're running V7, and it plays video fine for me.

[kmp14]

Ditto - Beta firmware needed with V7. Go to the firmware update screen, then hit 2382 on the remote, this will active the check for beta firmware. V7 runs real nice on my HD200's with the latest beta firmware.

[TwistedMelon]

He's already running the current firmware. He says so right in his post.

Originally Posted by toony

When I try the beta firmware 201007190 it runs nice and smooth excpet when it plays a video, well there is no video or audio.

No video or audio sounds like a bit of a problem.

[toony]

Yep I am running the beta firmware. Well I'm not anymore cause when I do run it as I said in the op I only get a blank screen when I play a video. I can ff rew pause stop play fine but its only to a blank screen. The menus work fine. So I'm running the non beta firmware so I can at least watch a video when it decides not to be laggy jumpy frozen or the best is when it stops the sage service on my whs.

[TwistedMelon]

Go to the firmware announcement thread and download a few of the older beta firmware versions and manually install them. Hopefully you'll find one that is up to date enough to deal with 7's new UI code and without the video issues.

[GKusnick]

Before we jump to the conclusion that it's a firmware bug, maybe we should find out exactly what V7 version he's running. All he said was "latest", and who knows what that could mean. (He also said he "didn't change a thing" while doing three firmware updates.)

Toony, if you have a repeatable issue with Sage V7.0.12 and firmware 201007190, you should file a formal bug report so it can be fixed. If you then want to try rolling back to an earlier version of the firmware, fine. But first make sure you have a real issue with the current versions of everything, and that the Sage devs know the details.

[TwistedMelon]

What he said was he was running the latest version of 7, which doesn't have a known issue of showing black video.

The latest release firmware is not appropriate for version 7 according to the release notes.

He has tried the latest BETA firmware. With the latest SageTV software version.

The next thing to do is regression testing. You can do the software or you can do the firmware. You should only ever do one at a time.

If he does a clean re-install of everything it might be impossible to find out what went wrong this time. Before filing a bug report it's a good idea to have some additional information to give the devs so they can focus on as specific an area as possible. That's what regression is for.

[barney B.A.]

Originally Posted by TwistedMelon

The latest release firmware is not appropriate for version 7 according to the release notes.

Not true. according to the latest entry from Opus4 in the firmware thread for the hd200
"When using the STP-HD200 as a SageTV media extender, it is recommended that SageTV server beta v6.6.2 or newer be used."

[stanger89]

Right, for the extender, you need at least Sage V6.6.2.

However, if you are running SageTV V7, you need to be running the beta firmware. At least if you don't want the UI to grind to a halt.

[TwistedMelon]

You can run the new BETA firmware with SageTV v6.x server. You can't run an old (release) firmware with a NEW SageTV 7.x server.

[GKusnick]

Originally Posted by TwistedMelon

He has tried the latest BETA firmware. With the latest SageTV software version.

We don't know that. All we know is what he tells us, and he has yet to tell us specifically what version of the software he's running. (He believes it's the latest, but without seeing the version number, we don't know that his belief is accurate.)

Also, in my opinion he's muddied the waters enough with multiple firmware updates and rollbacks ("Yep, I'm running the beta firmware. No, actually I'm not.") that I don't have high confidence that we know what state he was in when he observed the bad behavior. We know what state he thinks he was in, but he was apparently doing a fair amount of flailing around at the time.

So to me the sensible thing would be to get him into a known current state (software and firmware) and try to replicate the bad behavior before proceeding further. If it can't be replicated in a known state, then there's not much point worrying about the unknown state that caused it, since that state was already gone before he posted.