Quantcast
Channel: MCEBuddy 2.x
Viewing all articles
Browse latest Browse all 10715

Commented Unassigned: Scheduling w/12 hour clock - 2.14.x [1748]

$
0
0
I would like for MCEBuddy to run during all hour EXCEPT prime time television, which in the US, Central time is from 7:00 pm to 10:00 pm.

I understand the Start Time is entered as a 12 hour clock assuming that it would start in the morning before noon (AM) as an automatic designation. Conversely, the Stop Time is also entered as a 12 hour clock assuming afternoon (PM)

If I would want stop time to be 7:00 PM (the beginning of prime time recording for WMC), and start again after WMC has finished recording 10:00 PM, how would those parameters me entered? I must be missing something. The 24 hour clock would be simple as start time would be entered as 19:00 and stop entered as 22:00 leaving the three hour window where MCEBuddy would be idle, not be processing files, and allow other processes, specifically WMC to use all processing power required.

The reason for this schedule is, most of the day and night, the server is doing very little work. To dedicate the maximum number of cores to MCEBuddy and not step on other processes that run during prime time, e.g. WMC, How would I configure this settings after the 12 hour clock change?

My server has only is a Pentium 4 Prescott DT, 3.GHz processor and to restrict affinity to 2 or 3 cores requires about 3+ hours for only "Conversion" with ffmpeg for each .WTV file using the "Normal" processing profile.

Any suggestions to speed the processing time and schedule MCEBuddy to use the CPU maximum capability in off peak hours is appreciated.

Thanks, --eieio
Comments: ** Comment from web user: eieio **

Thanks! I assumed with the 2.3.14 release a 12 hour clock was the ONLY method of entering stop and start times. Thanks for clearing this up for me.


Viewing all articles
Browse latest Browse all 10715

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>