Project

General

Profile

Bug #4614

%p in post recording command partly broken

Added by Ludi K. over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-09-20
Due date:
% Done:

0%

Estimated time:
Found in version:
4.4.20170707
Affected Versions:

Description

Hi,

When I manually start a record with season and episode information from an epg entry by hitting the "Record Program" button and stop it after a few minutes by hitting the "Stop" button on the Current/Upcoming Recordings page, the .nfo file produced by my post recording script contains the season and episode information.

However, the .nfo file created by the same script does not contain the season and episode information for recordings started with timers. Since the filename of the record contains the season and episode information (as the recording format string is configured to add the corresponding information to the filename), it is not a problem of the season and episode information not being available.

Could the problem be caused by the post record padding that is set to 29 minutes?

Thanks in advance for looking into this.

History

#1

Updated by Jaroslav Kysela over 3 years ago

This bug already exists (no time to check which now), but appearently the problem is that the connected EPG event is removed from the database, so information cannot be fetched. DVR database should cache it.

#2

Updated by Mark Clarkstone over 3 years ago

Jaroslav Kysela wrote:

This bug already exists (no time to check which now), but appearently the problem is that the connected EPG event is removed from the database, so information cannot be fetched. DVR database should cache it.

This one #3931?

#3

Updated by Ludi K. over 3 years ago

I performed a test with an automatic record with a post record padding of 1 minute. The same problem occurs: the nfo file produced by the postrecording script does not contain any season/episode information, though the information was present in the epg, since it is present in the filename.

@Jaroslav Kysela

I suppose that caching only the epg information corresponding to timer events should be sufficient; at least for this problem.

#4

Updated by Ludi K. over 3 years ago

I think that Mark Clarkstone is right: this seems to be a duplicate of #3931.

Also available in: Atom PDF