Shows don't autoexpire

[Thomas Mashos]

The shows retreived via mythnettv are set to not autoexpire by default. This would be a good command line option to have. This autoexpire (and also being able to set the recording priority) are values in the recorded table.

recorded.recpriority Range(-99 to 99) Sets the recording priority, useful for autoexpiring shows

recorded.autoexpire Possible(0,1) Sets whether the show will autoexpire or not

[Kevin Slade (gleenglobes)]

mythnettv should have a recording priority of -99 so that real tv tuner recordings override downloads.

Does recorded.autoexpire Possible only allow/disallow existing Autoexpire set in MythTV to function or not? If this is what it does then it should be On by default so user´settings are honoured.

[Thomas Mashos (tgm4883)]

I wouldn't say a -99 for all mythnettv shows, perhaps if the value is left out it defaults to a certain value.

It would make sense to me that recorded.autoexpire just allows the show to be expired when the autoexpire job is run, and that the global autoexpire setting is whether the autoexpire job is run or not. So you are right, the default should probably be 1 (or True) for that setting.

[Michael Still (mikal)]

Fixed in revision 274

[Kevin Slade (gleenglobes)]

The reason I asked for default recording priority of -99 was so that recordings available via tv tuner would be recorded rather than downloading them via mythnettv. No point in downloading an episode if it is available via tuner.

What has been fixed in Rev. 274 Mikal? Has auto-expire been switched on?

[Michael Still (mikal)]

Gleen Globes wrote:
> The reason I asked for default recording priority of -99 was so that
> recordings available via tv tuner would be recorded rather than
> downloading them via mythnettv. No point in downloading an episode if it
> is available via tuner.
>
> What has been fixed in Rev. 274 Mikal? Has auto-expire been switched on?

Rev 274 sets autoexpire=1 in the recorded table. There is currently no
support for avoiding duplicate downloads. Specifically, mythnettv uses
its own algorithm for determining what to download, and does not consult
the MythTV recordings table as part of that process.

It would be quite hard to avoid duplicates in this way -- titles don't
match character for character, so how do you determine what is a
duplicate without involving a human?

Mikal

[Kevin Slade (gleenglobes)]

Please see https://blueprints.launchpad.net/mythnettv/+spec/mythnettv-ted to further explain my intended use of MythNetTV. If mythnettv-ted was implemented then a recording priority of -99 for mythettv would be necessary so that TED didn´t download recordings available via tuner.

Duplicates could be avoided by allowing EPG data to be added AFTER mythnettv has found relevent files to download but BEFORE actual download occurs. Please see information about Shepherd and thetvdb.com in above linked blueprint for how this could be implemented. MythTV already knows how to identify duplicates and avoid them (can´t remember at this moment where settings for duplicate matching is found!).

[Michael Still (mikal)]

That's not an autoexpire bug. Please create a separate bug to discuss that design, as I don't want to have multiple issues per bug.

[Kevin Slade (gleenglobes)]

I will discuss further issues in my blueprint from now on and create a new bug report for recording priority. Duplicates paragraph was in response to your:

"It would be quite hard to avoid duplicates in this way -- titles don't match character for character, so how do you determine what is a duplicate without involving a human?"

As you stated this bug has been fixed by Rev. 274 setting autoexpire = 1