Hi Everyone, <br><br>first post here. I have a problem with mythcommflag. Somehow when it runs, <br>encoding (by PVR-350) seems to include artifacts. Playback has lots lof little split-second<br>freezes. There is no problem at all if I switch things off so that mythcommflag does
<br>not run while recording. Its an underpowered PC I know.<br><br>I know mythcommflag runs nice (17), but that seems to still not be good enough for<br>not interfering with other processes. <br><br>I also know it is possible to set up a window of time during which mythcommflag can run,
<br>and no jobs will be initiated outside this window. That works best if there is a window during<br>which I never want to record any shows. However some of the shows I record are sitcom<br>reruns that run at all sorts of odd hours. If I could keep these windows disjoint from the
<br>recording sessions, that would be great, but the interface is obviously designed so that you<br>set the mythcommflag window once and leave it alone.<br><br>So my suggestion is that if possible mythcommflag should be designed to be able to dynamically adapt
<br>its operation to run outside the recording and playback sessions. That is, when any recording<br>or playback is happening, mythcommflag will not run, and when nothing is happening, we don't need<br>to tell mythcommflag to run, it just kicks into gear on noticing the silence and does what it has to do.
<br>The goal is to have mythcommflag automatically know what the recording schedules are and what the<br>users' viewing activity is, and know how to stay off the radar in those times. If this can be arranged,<br>then mythcommflag can run with no high nice setting, just barge through the job and be done with it.
<br><br>One way I was thinking of doing this (preferably without touching any source code for right now),<br>is to misuse the commands for turning the machine off and on when nothing is happening. It is intended<br>for shutting down and waking up, but can we use those hooks to instead enable and disable
<br>mythcommflag? That way, whenever the machine thinks it is safe to go to sleep because no recording<br>or viewing is happening, it will instead permit mythcommflag to run. And when it thinks it is time to come<br>back on, it will instead disable mythcommflag.
<br><br>Any reactions welcome -- either on how to get this implemented as a standard feature, or how I <br>can configure my own installation to have that behavior with the minimum of work.<br><br>Thanks,<br><br>Ambrose<br>
<br>