<div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This sounds like something to look forward to.<br>
<br>
I was wondering how wide a role you are planning for the labels?<br>
<br>
I've also been using Recording Groups as simple user accounts, but something I've been trying to work out (and failing for the most part) is how to bundle together recording rules so I only have to set the Recording Group when creating a new recording schedule, and different actions are performed based on the selected recording group. For example,<br>
<br>
Person A wants her cooking programmes indefinitely stored, so auto-expire should be false<br>
Person B only watches via a tablet after its been transcoded into xyz format and copied to a network share<br>
Person C is two, and so their programmes can be transcoded immediately after commflagging so they don't see all the toy adverts.<br>
Person D records dvb radio broadcasts, so if its a radio channel extract the audio and move it to his podcast archive.<br>
<br>
Currently this is set up each time I set a new recording schedule, but I've been thinking about implementing some script triggered at the end of the recording which decides what to do based on Recording Group.<br>
<br>
The holy grail though, and i accept, probably a nightmare to engineer, would be to define a user/tag/label and associated actions, and then when creating a schedule, select the type of recording and who its for, - with the normal scheduler options accessible behind an 'advanced' button for when you occasionally need to tweak things further - like when one action conflicts with another.<br>
<br>
Is this beyond what you're planning? If the answers 'yes', and i expect it is, then thats fine. I can't code and don't expect anyone to do it for me - i'll get on with the script and see if i end up with something robust enough for the wiki...<br>
<br>
</blockquote>
<br></div></div>
At this point, yes, it's beyond my plans. Once the labels are in place, it's quite possible that they will be extended and used for additional things.<br>
<br>
That said, a script-based approach using user jobs sounds like a good idea. I'll try to remember to update the user job code to add a %LABELS% expansion. And, if you create a script to do this (before and/or after labels), it would be welcomed on the wiki scripts category ( <a href="http://www.mythtv.org/wiki/Category:Scripts" target="_blank">http://www.mythtv.org/wiki/<u></u>Category:Scripts</a> + specifically <a href="http://www.mythtv.org/wiki/Category:User_Job_Scripts" target="_blank">http://www.mythtv.org/wiki/<u></u>Category:User_Job_Scripts</a> ).<br>
<br>
Oh, and FWIW, eventually (though this one has been on the TODO list for many versions/years, now), we hope to allow recording rule templates (to allow you to define your preferred settings) so creating recording rules with non-default values should become easier.<br>
</blockquote></div><br>Sounds like his thoughts are similar to mine with regard to tags... make them more than just a way of organizing/filtering recordings... make them the logic that the system uses to perform actions or report information about the recordings as well. A single recording could have many tags, both user selectable and system generated, and all of those tags can be used to filter the recordings using a single common interface (so I could filter to show my HD movies that include closed captioning) Obviously starting with just user tags makes sense, but ultimately I would love to see tags for post processing, and tags for recording details too.<br>
</div>