|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#21
|
|||
|
|||
Hi Jeff,
I'll give that a try and post my results here for you. In order to isolate the recordings I'll have to remove the non-remote-encoder sources I think since it doesn't use those first. |
#22
|
|||
|
|||
Hi Jeff,
I'm going to post two sets of logs in these next two posts. Each .ZIP contains the two log files, as well as a readme.txt which I'll include in the body of these messages. The readme.txt explains what I did and when things went wrong (to the second, to the best of my ability). To make things faster, I decided to just cancel the recordings outright instead of waiting for them to finish. I see the exact same behaviour when I do that, so fixing one issue will likely fix the other. I should also point out theat it seems that the problem can only happen when the playback engine is active. As you'll see from the logs, I've never had a failure when playback was stopped (ie: the sagetv mediaplayer was doing nothing). If its playing or paused (on a show being recorded by a network encoder) though when that show stops recording, its toast. I'm not sure that the exact time will help you too much, as everything goes wrong in under 1 second typically, but in the first log you actually see the "recording cancelled" message and thats when it all goes batty. I've noted the times though in the readme.txt file for you. If there is anything else you want me to do (ie: get more logs, run a debugging version of the application, whatever) I'll be happy to do it. I definitely want to see this work. --- In these logs, I did the following: 1. I halted SageTV on both machines, removed all logs, and restarted SageTV. 2. I started some recordings until I found one that caused the encoding server to come into play. 3. I allowed that recording to go for a minute, then cancelled it. All was well. 4. I started another recording, which again used the encoding server, and then actually started watching that recording. I exited playback, which paused the playback. I waited a minute, then hit "cancael recording" (without first stopping the playback). The CPU instantly jumped to 100%. The time of the CPU jump was: 8:18:30 - 8:18:32 It hasn't come back. |
#23
|
|||
|
|||
Hi Jeff,
Here is a another set of logs (to go with the ones I just posted a minute ago): For this test, I did the following: 1. stopped sagetv on both servers, removed all log files, restarted sage tv. 2. removed all tuners that weren't network encoders 3. started a recording, watched it for a minute, exited (causing it to be paused) and then STOPPED the playback of the recording. 4. Cancelled the recording at 8:37:30. All was well. 5. Started a different recording, watched it for a minute, exited (causing it to be paused) but did not STOP the playback. 6. Cancelled the recording at 8:54:25. The CPU usage instantly went to 100% and stayed there. |
#24
|
||||
|
||||
Deria,
Try this updated filter on the network encoder machine (won't hurt on both, but that's the only one it'll have an effect on). I repro'd your problem and saw the same thing as you, so it wasn't that hard to find. Just unzip it into your SageTV\Common folder and overwrite the one that's there. Do it while SageTV is not running. Let me know the results.
__________________
Jeffrey Kardatzke Founder of SageTV |
#25
|
|||
|
|||
I'll give it a try and post my results for you. Thanks for the quick response!
|
#26
|
||||
|
||||
Seeing this kind of customer service warms my heart, even when it isn't a problem I'm experiencing being fixed.
|
#27
|
|||
|
|||
Hi Jeff,
That seems to have done the trick. I stopped SageTV, installed this new file, restarted SageTV, and then started recordings until the network encoders came into play. I was able to watch the show, exit (causing a pause) and then cancel the recording and it didn't lock up. I think you've solved it! Thanks for the quick response. I have to say that the support is one of the things that impresses me the most about SageTV. The fact that you started looking at this on a weekend (a holiday weekend, even) and moved the problem to a solution in under 1 day is extremely impressive. This is the kind of thing that makes me feel good about my investment. |
#28
|
||||
|
||||
Jeff rules! Dogs drool
He helped me out with an MP3 issue I was having over the weekend as well |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|