2.0->2.1 350 encoder broken

[bmadgett]

Hi all,

Upgraded to 2.1 over my 2.0 install last night, and I'm having problems with my 350 encoder. I'm running the background service, and using exetuner to control an external IR device to switch channels on my cable box. Everything was working perfectly prior to the 2.1 upgrade.

From a fresh boot, if I try to change channels via LiveTV, I get a message something like "no encoders support tuning to that channel" (or something similar). Recordings try to activate but just fail to record anything (presumably for the same reason). If I try to "force" the channel change by going into setup wizard & hitting "view" on a particular channel, Sage completely dies and produces the attached hs_err_pid log. The top snippet from this is :

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x4DF454E
Function=Java_sage_DShowCaptureDevice_setEncodingProperties0+0x4E
Library=C:\Program Files\Frey Technologies\SageTV\DShowCapture.dll

Current Java thread:
at sage.DShowCaptureDevice.setEncodingProperties0(Native Method)
at sage.DShowCaptureDevice.else(Unknown Source)
at sage.Sage.processMsg(Unknown Source)
- locked <0x13118208> (a java.util.Vector)

However, if I then restart Sage & try tuning, it all works perfectly!! Which is very very weird. Until the next time I reboot.

So - any clues what could've caused this? I've attached my properties files as well, just in case it's something in there that could cause the problem. I tried completely removing & reconfiguring the tuner within Sage but that made no difference. I can't think it's a driver problem (seeing as it worked perfectly before, and works fine after this weird crash). And I really really don't want to lose my viewing history etc, which I would if I tried a "clean" Sage install, presumably. Although I am a bit concerned these crashes will result in a corrupt wiz.bin sooner or later.

Thoughts?

Barnaby

[BobPhoenix]

You should be able to keep your viewing history as long as you save your WIZ.BIN files. When I installed 2.1 I renamed the 2.0 directory and installed 2.1 then just copied back the WIZ.BIN file replacing the 2.1 default that was created. I made the mistake of starting SageTV before I did this copy but it doesn't appear to have caused a problem - you might however just replace you WIZ.BIN before you start Sage. Don't know if doing your install this way will help or not but it worked for me.

BobP.

[justme]

Since you say you only have issues right after a reboot(just restarting SageTV after the first crash works) and you're running Sage2.1 as a service... You might want to try the "startup_delay" setting in your properties file. According to the 2.1 manual(appendix A) it's purpose is to help issues caused by loading SageTV at startup.

[bmadgett]

Originally Posted by justme

Since you say you only have issues right after a reboot(just restarting SageTV after the first crash works) and you're running Sage2.1 as a service... You might want to try the "startup_delay" setting in your properties file. According to the 2.1 manual(appendix A) it's purpose is to help issues caused by loading SageTV at startup.

Tried this and yes, it does solve my problem. Thanks!

Barnaby