'''User Jobs''' are customized tasks which can act on MythTV recordings. A MythTV system currently supports up to four User Jobs.

'''User Jobs''' are customized tasks which can act on MythTV recordings. A MythTV system currently supports up to four User Jobs.

+

{{Note box| Beginning with release 0.26, timestamps of recordings are stored in UTC. Applications that use xxxTIME parameters to directly index the database will need to either handle timezone conversion internally, or switch to the respective xxxTIMEUTC parameters. See [[UTC]]}}

+

<br>

__TOC__

__TOC__

== Adding a User Job ==

== Adding a User Job ==

Line 16:

Line 18:

A user job is just a program or script which is passed some arguments to tell it what recording to perform work on. Either the channel and start time, or the directory and filename, should be sufficient to uniquely identify the recording.

A user job is just a program or script which is passed some arguments to tell it what recording to perform work on. Either the channel and start time, or the directory and filename, should be sufficient to uniquely identify the recording.

Revision as of 01:58, 17 September 2012

User Jobs are customized tasks which can act on MythTV recordings. A MythTV system currently supports up to four User Jobs.

Note: Beginning with release 0.26, timestamps of recordings are stored in UTC. Applications that use xxxTIME parameters to directly index the database will need to either handle timezone conversion internally, or switch to the respective xxxTIMEUTC parameters. See UTC

Important Note: If you use the MythWeb method for setting up a user job, you have to restart mythbackend for the changes to take effect. (Theoretically if you are doing it via MythTV-Setup, then mythbackend isn't running anyway.)

User Job arguments

A user job is just a program or script which is passed some arguments to tell it what recording to perform work on. Either the channel and start time, or the directory and filename, should be sufficient to uniquely identify the recording.

1 if this recording was reactivated after failing to start on time, 0 otherwise.

Event

%RECGROUP%

Recording group

Both

%RECID%

Recording rule ID, for DB lookups.

Event

%RECSTATUS%

Recording status as an integer for completeness, not currently useful.

Event

%RECTYPE%

This is the recording rule type as an integer, in the priming script example this could be used to do an extensive priming prior to some recordings and not others. These integers are listed in recordingtypes.h in the RecordingType enum.

Export recordings to small mpegs with or without commercials, suitable for use with Rockbox[1]. These examples are tailored for the screen and CPU capabilities of the SanDisk Sansa e200 series of media players.