[mythtv-users] Job priority within Myth's job queue

[G. Panula]

~~ Steven Adeff wrote on 04/10/06 16:43 ~~
> On 4/10/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>> On 04/10/2006 04:33 PM, G. Panula wrote:
>>> Is there a way to give Commercial Flagging jobs priority over
>>> Transcoding jobs within Myth's job queue?
>>>
>> In mythtv-setup (on page "Job Queue (Global)"):
>>
>> Run Transcode Jobs before Auto-Commercial Flagging
>> If set, if both auto-transcode and auto commercial flagging are turned
>> ON for a recording, transcoding will run first, otherwise, commercial
>> flagging runs first.
>>
>> (Note, however, that if you specify transcode before commflag and
>> real-time commflagging, your commflagging won't be real-time because it
>> still waits until after the transcode, which occurs after recording.)
>>

>>> The *problem* is the transcoding job is the next job in the queue and
>>> the back-end faithfully starts working on it.  Even if I have the
>>> back-end only checking the queue every 5 minutes, it still picks the
>>> transcoding job first.  I think jobs are just processed on age; oldest
>>> one first aka FIFO(First In First Out)
>>>
>>> Ideally the commercial flagging jobs should have a higher priority than
>>> transcoding job or at least an option to say do commercial flagging jobs
>>> first.
>> Actually, the setting is meant for the opposite because after the
>> transcode, commflagging needs to be re-run (new format, new size, new
>> frame positions, ... whatever).  However, this is applied on a
>> per-recording basis--it's not a general prioritization.  So, you'll
>> still get mixed commflag/transcode jobs occurring.
>>
>> Mike
> 
> he means have commflagging queue up before any existing transcoding
> jobs, even those for other shows.
> 
> I agree, this would be a nice feature. I can deal with transcoding
> "later", but I'd rather have all commflagging occur before any
> transcoding begins uinless I tell Myth otherwise.
> 

Aye, I want all commflagging jobs to take priority over all transcoding 
jobs.

Thanks for confirming this feature doesn't exist... I can stop looking now.

greg