Strange Problem with Commskip & SageTV

[tealcomp]

I am running the Beta 2.2 version of Sage and I run Sage as a service; I also use the Cayars v16 STV. Lately, I have noticed a couple of odd problems regarding Sage and Commskip, I believe the two to be unrelated.

1) If I exit Sage (but leave Service running) and commskip starts processing a file, I cannot bring the Sage UI up until either I a) kill that process or b) let it continue processing to completion.

2) When watching certain shows, commskip literally skips over 1/2 of the show; for example, when watching Dallas, when it hit the first commercial skip point, it jumped over several of them and then when it started playing, the video was stuck in fast forward (that may be the Nvidia fast-forward skip problem that has been mentioned); anyway, it is very frustrating.

I am researching the forum to see if this has been mentioned by others before but thought I would post this as well. I will continue to look around, but if anyone sees this as familiar, please let me know.

Thanks,
-Dan

[mdmint]

Originally Posted by tealcomp

I am running the Beta 2.2 version of Sage and I run Sage as a service; I also use the Cayars v16 STV. Lately, I have noticed a couple of odd problems regarding Sage and Commskip, I believe the two to be unrelated.

1) If I exit Sage (but leave Service running) and commskip starts processing a file, I cannot bring the Sage UI up until either I a) kill that process or b) let it continue processing to completion.

2) When watching certain shows, commskip literally skips over 1/2 of the show; for example, when watching Dallas, when it hit the first commercial skip point, it jumped over several of them and then when it started playing, the video was stuck in fast forward (that may be the Nvidia fast-forward skip problem that has been mentioned); anyway, it is very frustrating.

I am researching the forum to see if this has been mentioned by others before but thought I would post this as well. I will continue to look around, but if anyone sees this as familiar, please let me know.

Thanks,
-Dan

1) Normal comskip/Sage behavior. Just the way it currently is.

2) Never experience that one myself.

[tealcomp]

Originally Posted by mdmint

1) Normal comskip/Sage behavior. Just the way it currently is.

2) Never experience that one myself.

Thanks for that confirmation, as I haven't been able to find anything else on it so far. I suspect that item 2 is related to the quartz.dll fiasco with SP2..


-Dan