I hate Sage 1.4

[visiontim]

So, I have (had actually) a great stable 1.3.8 system that was up and running. I had it on non-stop with no reboots for over a month.

Then I get the new Sage 1.4 email. So yesterday I decided to upgrade. Everything went relatively well except for the stuttering video problems and the changed mapping of my 250's remote. The top right button no longer went to the Live TV guide as before and the Full button wouldn't work...a whole bunch of crap. I tried to remap, but that didn't work. It wasn't even recongnized actually.

So at this point I say, "screw it, uninstall and put 1.3.8 back on". Great in theory. This is where the real problems start.

I do the above and when I go to launch 1.3.8 I get the Java Null blah blah blah error. After reading some posts I try the possible solutions and no go. So, I uninstall 1.3.8 and totally remove the Frey directory. I then install it again (1.3.8) and now it works (I thought so at least). I had to put all my favorites in again and do the entire setup over. The sleep button didn't work at this point, a familiar problem to some of us.

Now the part that kills me. I go to work and come home and the computer has crashed. WTF? I restart and sure enough, when Sage goes to record a show it moves along fine then crashes Windows XP Pro. I also hear a horrible wrenching sound in my new (1 month old) super duper new hard drive. Turns out there are errors on the drive now and scandisk won't even run.

So, Sage killed my computer. Everything went fine until 1.4. I know there are probably other factors at work, but I can tell you I did nothing but install and take out Sage. No other programs were installed and this is a dedicated Sage machine.

I'm pissed. I'm going to reformat the drive and install everything over again. I just don't understand how you can say this is stable and not even have a proper way to go back to 1.3.8 without some stupid text editing trick that does not work.

I love Sage, when it works.

[mlbdude]

The .dat file formats were changed with 1.4 to help correct corruption and 100% CPU issues. Doing so made going back to 1.3.8 impossible after an upgrade (at least for me as well). I knew about the remap requirement for remote commands early on so was prepared for that. The corruption of your HD, is odd and you are probably correct in saying "there are probably other factors at work". The best advice I have gotten and give is to copy your Frey folder prior to upgrading. This way you can go back super easy.

BTW, what Hauppauge drivers are you using and what MPEG2 decoder are you using? A few other users are getting stuttering video as well. Since not everyone is there must be some combination of files causing this.

Good luck.

[falchulk]

I did the upgrade from 1.3.8 to 1.4.10 and back to 1.3.8 3 times with no problems at all.

[visiontim]

Bully for you. Not so for me.

[malore]

I also had problems with the pvr-250's remote commands not matching up correctly with SageTV. If you are willing to give 1.4 another try, if you delete the keyboard_accelerators line from the Sage.properties file, then SageTV will revert to the default key mappings, which should match the settings in the irrmode.ini file that SageTV creates if you install SageTV with support for the pvr remote.

[rrussell]

Does that mean that the irremote.ini file included with 1.4.10 doesn't have the updated key mappings in it?

I thought it might have since they did include the grnpower fix to sleep/awaken sage when it doesn't have focus.

[StylinLP]

Hate to tell you this. But your hard drive failed. You will find that when you try and run scan disk it will find some bad sectors on our hard drive. Basically your probably in the middle of whats known as a IDE cascade failure. Its really common. You should still have the drive under warranty and have it replaced.

[malore]

Originally posted by rrussell
Does that mean that the irremote.ini file included with 1.4.10 doesn't have the updated key mappings in it?

I thought it might have since they did include the grnpower fix to sleep/awaken sage when it doesn't have focus.

The irremote.ini that 1.4.10 creates does have the updated key mappings with ctrl added to most of the commands, but on my machine when SageTV updated the keyboard mapping in SageTV it showed both the old and new commands, and a few of commands didn't match the settings for the remote. Rather than try to fix each of the commands manually, I deleted the keyboard_accelerators line to reset all the commands to the default. Then everything worked perfectly.

I think SageTV leaves everything in the irrmode.ini alone except for the [SageTV] and [SageRecorder] settings, so if you added a grnpower in the [default] section, it would be left alone.

[rrussell]

You're right - my remote is working fine now.

It helps when you make sure the receiver wire is plugged into the pc.

Ooops.