> Glad to hear. Because on my own todo list for some time has been looking > into a smarter transcoder, which would have a set of profiles, and some > simple rules for which one to pick. One simple idea is a set of rules > of the form, "Program >= X lines -> Use transcoding profile Y"
I agree, this logic or something like it would be nice in the future. > Yup, this is to be expected. Though most people with HD cards will have > HD capable CPUs and it won't be so rough... Do you do 2 pass? I do > that with mencoder, and it's not exactly fast. Myth's builtin transcoder only does single-pass. > Because of that CPU load, my dream transcoder probably runs only at > night or when the system is otherwise idle, and it has a threshold you > can set in the profile that says "Don't transcode until recording is > more than N days old." Well, part of that's coming in the JobQueue. :) Almost at the very top of my TODO list is to add a Job Time Window to allow the user to restrict jobs to starting within a certain window. So people can just let their commflagging or transcoding jobs run overnight or during the day while they are at work, etc.. It will probably be a simple begin and end set of times with the defaults being 00:00 and 23:59 respectively. Scheduling jobs may come in the future but I haven't thought about that much, but it would be fairly easy to implement. A job could have a specified starttime where it wouldn't start before that. When recordings are deleted, all running and pending jobs are deleted so if there was a queued job for 3 days from now, it would be deleted if the show was deleted before that. This would be another way of allowing jobs to be run only at night or while everyone was off at work. -- Chris
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
