Tuning confusion

[trini0]

I see a few references to tuning problems similar to what Im experiencing.
But not as bizarre as what Im getting.
I have 2 cards in the htpc. One Digital, and one Analog.
Every now and then, out of the blue, if I tune Sage to digital channel 7-1, Sage
decides to tune analog channel 640 (of which its a channel, that I dont even have setup in Sage, as its a premium channel that I do not subscribe to).
Sometimes if I shutdown Sage, and restart the service it goes back to normal.
Anyone knows of a similar problem and a fix to it?
Im using Sage 5.0.4 with XP sp2.
Thanks

[trini0]

Bump
Do you need more info, or are you just as baffled with the problem?

[bcjenkins]

I think it would help to know which remote control you are using and if you could turn on logging. Post a log snippet when the error occurs.

B

[trini0]

I thought I had that info in my sig.
Sig has been updated.
My remote is a Harmony 520. I dont think its the remote.
When this problem does occur, Sage is firing off the USB-UIRT when it shouldn't
when tuning digital channels.
As far as a log capture, I'll see when it happens again...

[trini0]

Question. How large of a debug file can I send to the Sage Developers?
I just had this problem pop up on me again.
I immediately shutdown sage & the service. Set debug_logging=TRUE in the sage properties file.
Restarted the service, and started sage. But the problem didn't happen.
As stated above, if I restart sage & service, the problem goes away.
So, I'm going to try to leave it enabled to see if I can catch it again.
Just do not know how big the debug file would get by the next time, the
problem happens again.

[gplasky]

You could always edit the file for the pertinent info. I would think a period of time just before the error occurs would be enough. And you could always send multiple edits of the file. It's just a text file.

Gerry

[trini0]

Ok. I was able to have the problem happen again.
I was tuning to digital 10-1 to watch Grey's Anatomy, and Sage tuned to
analog 10.
The debug logging is still enabled. I'll try to see if I can do it again, before
I shut it down again...

[trini0]

I was able to replicate the problem again.
Log file has been sent to Sage Developers.

[trini0]

Got a reply back from a Sage Dev member.
They report that the problem should be fixed in the upcoming beta, 5.1.
I'm glad that they were able to have an idea as to what was going on
with my problem, and work something out.
Thanks Sage...