Jump to content


almero

Member Since 28 Jan 2012
Offline Last Active Yesterday, 09:12
-----

#260877 Permanent Timeshift max. 1 event?

Posted by almero on 4 March 2012 - 22:43

Ik heb inmiddels de oorzaak gevonden van het niet meer kunnen saven van events uit de timeshift buffer ("lengte 0"). Het is inderdaad begonnen met wat op 25 december 2011 is toegevoegd, namelijk een .sc file voor de timeshift buffer.

Zie deze thread uit het Engelstalige forum voor een voorlopige patch.


#260873 Permanent Timeshift

Posted by almero on 4 March 2012 - 22:27

Hey guys, I think I have found the cause of the problem and also a solution (at least for saving events from the timeshift buffer):

The problem is caused by the presence of the timeshift.BLABLA.sc file in the timeshift path (see the modification of December 25th I mentioned above).

The timeshift file has the syntax "timeshift.somecharacters".
PTS tries to identify the timeshift file by looking for a file that starts with "timeshift." and does not end with ".del" or with ". copy" (these suffixes are used by the background delete and copy processes).
This used to work, but since December 25th, there is also a file "timeshift.somecharacters.sc" and PTS confuses this for the actual timeshift file.

I have patched the plugin.py file by replacing

if filename.startswith("timeshift.") and not filename.endswith(".del") and not filename.endswith(".copy"):

with

if filename.startswith("timeshift.") and not filename.endswith(".sc") and not filename.endswith(".del") and not filename.endswith(".copy"):

on 3 locations in the file, plus


"if (filename.startswith("timeshift.") or filename.startswith("pts_livebuffer.")) and (filename.endswith(".del") is False and filename.endswith(".copy") is False and filename.endswith(".meta") is False and filename.endswith(".eit") is False):

by

if (filename.startswith("timeshift.") or filename.startswith("pts_livebuffer.")) and not filename.endswith(".sc") and (filename.endswith(".del") is False and filename.endswith(".copy") is False and filename.endswith(".meta") is False and filename.endswith(".eit") is False):

on one location in the file.

You can find the file plugin.py in /usr/lib/enigma2/python/Plugins/Extensions/PermanentTimeshift/

Once the plugin.py is patched, restart enigma and you're done.

Attached a rar file with the original as well as the patched plugin.py for the permanenttimeshift version:
enigma2-plugin-extensions-permanenttimeshift_3.2git20111109-r0_dm8000.ipk

Attached Files




#250581 Permanent Timeshift

Posted by almero on 29 January 2012 - 02:40

Hi,
I am experiencing the same issue on my dm8000: PTS works unreliably when shifting over more than one event. Plus, 'timeshift record current event / select event' leads to a recording with length 0.
Problems started when I did an update somewhere early January 2012. It was my first update in at least a month. During December, I didn't see the problem.

Today I uninstalled PTS and installed an older version of PTS from early December (I tried 10/12 and 4/12). But 'Timeshift record current event' again lead to a recording with length 0.


I do remember something was changed late December in the way the timeshift buffer operates. Maybe that has something to do with it.

In the enigma2 update log, I found the following information:


Record stream information during timeshift - Mike Looijmans [Sun, 25 Dec 2011 11:02:12 +0000]

servicedvb: Record stream information during timeshift
Write an sc file during timeshift. This allows smooth (re)winding
at >16x during timeshift, and also improves skipping and other seek
related actions.

Drawback: The AP data is stored in memory, consuming ~64k RAM per hour
which is not used for anything.


Could it be that the PTS plugin is not aware of the changed timeshift structure and therefore cannot record it to disk?