117 replies to this topic

[Dimitrij]

Patch.
author mogli123 www.et-view-support.com

[MrKappa]

Patch.
author mogli123 www.et-view-support.com

Hello' Dima73, please, what is the purpose of this hack? I tried to translate from et-view forum and I understood that it should prevent that we miss again PTS functionality. Is it correct?
How to install it?

[Dimitrij]

With this patch works rewind PTS.
To apply the patch need to edit */Screens/InfoBarGenerics.py

[MrKappa]

Many thanks. Hopefully it will be included with online updates.

[Lukin]

I've noticed that both timeshift from system and pts (if you have it installed) are generating their specific buffers, which I believe is causing a conflict...resulting in buggy Pts.

Is there any way to disable the system timeshift if I want to use Pts instead?

From Pts....
pts_livebuffer.1
pts_livebuffer.1.eit
pts_livebuffer.1.meta

From system timeshift...
timeshift.CVio3c
timeshift.CVio3c.sc

Thx!

[brdbch]

Good question!
Both files are exactly the same size.
It looks like the data is constanly being written twice on the hard disk.
Is this really useful?

[hemispherical1]

Yes it's useful and no it isn't actually written twice. The 2 files are linked together and actually use 1/2 the disk space as they'd appear to if they were actually 2 discreet files, for example:

du -sh /hdd/timeshift ; ls -lh /hdd/timeshift/
70.3M   /hdd/timeshift
-rw-------    2 root	 root	   69.9M Apr 28 16:56 pts_livebuffer.1
-rwxr-xr-x    1 root	 root		 292 Apr 28 16:50 pts_livebuffer.1.eit
-rw-r--r--    1 root	 root		 108 Apr 28 16:50 pts_livebuffer.1.meta
-rw-------    2 root	 root	   69.9M Apr 28 16:56 timeshift.ON8e06
-rw-r--r--    1 root	 root	  158.6K Apr 28 16:56 timeshift.ON8e06.sc
-rw-r--r--    1 root	 root	  108.9K Apr 25 10:31 timeshift.hlWXvn.sc

The diskspace used is 70.3MB, although it would appear to be using 140MB if they were actually separate files...

--
hemi

Edited by hemispherical1, 28 April 2012 - 21:57.

[nietgiftig]

Yes it's useful and no it isn't actually written twice. The 2 files are linked together and actually use 1/2 the disk space as they'd appear to if they were actually 2 discreet files
....

The diskspace used is 70.3MB, although it would appear to be using 140MB if they were actually separate files...
--
hemi

Thanks for the explanation.

Why is it "usefull " ?

Linux pffff !!!

[brdbch]

Strange,

How come:

diff -s timeshift.TzJAPi pts_livebuffer.1
Files timeshift.TzJAPi and pts_livebuffer.1 are identical

[hemispherical1]

Thanks for the explanation.

Why is it "usefull " ?

Without being a timeshift guru,I'd guess that a 2nd file is involved with allowing you to save Timeshift events. But in reality it is useful because the author of the plugin put it there, for a reason I assume. I don't see him/her having just said "Ya know what would be cool, if I created 2 timeshift files instead of one...

Strange,

How come:

diff -s timeshift.TzJAPi pts_livebuffer.1
Files timeshift.TzJAPi and pts_livebuffer.1 are identical

Because they're the same file? I thought I explained that, I tried anyways...

--
hemi

[nietgiftig]

But in reality it is useful because the author of the plugin put it there, for a reason I assume

hemi

Oke, it's usefulness is an assumption by you.
Hopefully it's usefulness will be explained by "the author", i'm always curious

I don't see him/her having just said "Ya know what would be cool, if I created 2 timeshift files instead of one...

hemi

No that would not be cool.
Maybe he thought "lets use a trick to accomplish my goal"
But that is an assumption from my side.

[Meega]

I've asked the author(homy-ger) also why he has two files and he said that one file is a hardlink and it was discussed many times on ihad.
But i don't speak german so if anybody .....

[malakudi]

The usage of hardlinks is an easy and very clever way to separate data of different events without having to do file operations (copy, truncate etc). When timeshift starts, PTS creates a hard link to the running timeshift file. When event changes, PTS starts timeshift ftom the beginning, zeroing the timeshift buffer and creating a new hard link. Previous hard link is still available and holds the data of the timeshift session of the previous event. Data in hard linked files is only deleted when all of the links have been removed.

Edited by malakudi, 30 April 2012 - 00:18.

[nietgiftig]

Thanks malakudi !!

[the6thday]

Is there any news on this subject?

Currently PTS still doesn't work correctly in the newest builds(no rewind possible), if I understand this problem correctly there already is a patch for this problem in post #81 http://openpli.org/f...post__p__265553

Can one of the openpli dev's please apply this patch? so we can use online update to get it? or can someone supply a patched InfoBarGenerics.pyo in this thread?

[littlesat]

FYI:
http://openpli.git.s...b0bfc5aea71fbcd

I hope this helps.....

[the6thday]

Big THX for this quick fix! it's working as expected now!

[littlesat]

It was not a quick fix .... but the orriginal patch was not exepted (not used sub function and too complicated)... so for me (as non PTS user) it take a longer time. Sorry.....

[umtauscher]

Is this fix also in the 3.0 feeds?
I experienced problems with PTS on an event change and I wasn't aware of any problems in 2.1.
So before I revert back to 2.1 perhaps anyone else could verify this?
Thanks
Umtauscher

[nietgiftig]

In my box with PLi3.0 PTS does not work perfect.
Timeshift recording is not always started after zapping to another channel or after you saved a timeshifted program.
I use mainly PTS to record something I want to keep after zapping to a channel and watching for some time.
Not a standard usage for timeshifting, but this is possible with PTS and not with the normal timeshifting

Also there is not a consistent recording symbol on the box, you are never sure if PTS is working
Sometimes the recording light is on sometimes not.
I use an USB stick to put the timeshift on, and I usually have to look at the LED on the USB stick to check if PTS is working.

But I do not know if this is only an issue with 3.0, I think it is the same plugin as in 2.1

PTS Timeshifting remains an problem, it seems it is hard to make it working rock-steady.
But the DEV's themselves do not use timeshift, so thats not creating a good environment for developing.