> I've got a User Job that symlinks my recording to another directory with > a filename like programname/episodename.mpg in a file system that's > exported to my xbox media center. Fantastic! However, every time I > schedule a recording that I want exported (most of them) I have to > enable user job #1 from the recording settings screen, kinda an > inconvenience, and this function isn't available on mythweb.
Yeah, I didn't think the User Jobs would take off as much as they have so I didn't make them as easy to use as the transcoder and commflagging jobs. > So what I was going to do was add a default for the user jobs so they're > not always disabled by default. First I thought I'd put the default per > job in the backend setup, but that's not a good idea because it's > per-backend, which may or may not be a good idea. This isn't necessarily true, there are "Global" settings and "Host" settings in the backend setup program. The Global apply to all backends and the Host apply just to the backend where you're running setup at. Currently the only place to edit a User Job is via the backend setup. So if you were going to make a UserJob default on or off it would make sense to do it in the same place you setup the user job. Maybe the user job config settings should be available via the frontend setup instead of the backend. Since the Auto Commercial Flag default setting is accessible via the frontend, I think it makes sense to have the User Job defaults settings be accessible from the frontends also. > My next idea was to add this as a per-recording profile item, which fits > with the "Automatically transcode after" per-profile option. The only > disadvantage I can see here is when you change the recording profile > from "Storage Options", it would automatically modify the settings in This I'm not sure about. What would be the reasons for making a User Job run by default for one recording profile but not for another? Are you thinking nuvexport or something? On that note, I originally had a commented-out setting to allow turning on/off transcoding jobs on a per-scheduled recoring basis, but took that code back out. This would allow the user to run transcoding for some shows but not for others that used the same recording profile. Does anyone see any value in this flexibility? For DVB & HDTV users, it might make more sense, you might want to transcode down certain shows that you plan on archiving for a while but not others that are watched and deleted fairly soon after recording. -- Chris
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
