747 replies to this topic

[betacentauri]

@pieterg: And again thanks for looking into it and checking in the patch!!

@dima73: Please try tomorrow with the latest patch again.
I would guess, that you are using PTS, correct?
What do you do exactly do?
If you are not using PTS how long do you wait with pressing pause after zapping?
You press pause and afterwards immediately fast forward (or is it a fast rewind)?
Is it a SD channel with very low bitrate? Can you test with other channels?

[pieterg]

To start with, the name PTS should be forbidden, it's very confusing for people that know anything about DVB

But regarding the 'black screen when trying to rewind from the live point of the timeshift', I experienced that today, when testing the EOF issues with the normal timeshift.
On an average bitrate scrambled HD channel.

[betacentauri]

Ah, so you start timeshift, switch back to live tv and then rewind back (with rewind key and not 1,4,7). Correct?
I tried it (with EOF patch) on 2-3 channels and it works here. Did you also have the problem with the EOF patch?

[pieterg]

yes, I specifically tested with and without, because at first it looked like it was introduced by the EOF patch
But it wasn't, I could also reproduce it without the patch.

[betacentauri]

If I can reproduce this, I'll debug it.

By the way: I have never done it before. I always had used pause and then pressing seek buttons. Quite nice.

Edited by betacentauri, 3 February 2013 - 20:29.

[pieterg]

I think we should get the actionmap fixed, so we can just skip back from the live point.
(but I'm not really a python type of guy)

[betacentauri]

I think we should get the actionmap fixed, so we can just skip back from the live point.

Well, after timeshift start you can seek with 1,3,4,... If you switch back to live tv it's deactived again. The advantage of this is, that you can change channel with number keys but cannot seek with the number keys. For the user it's quite easy.[list]
[*]Watching timeshift -> number keys are for seeking
[*]Live TV -> number keys are for channel switching
[/list]
I would not change it. It confuses only people.
(If you ask me, I would find it better to have different keys for seeking and channel switching...my point of view).

(but I'm not really a python type of guy)

Me too

[pieterg]

I actually found that while you're at the live point of the timeshift, the number keys (at least, those which would normally skip) don't work at all, not even to change the channel.

[mik9]

There will be definitely several ways of controlling channel selection and timeshifting by users, this is e.g. mine:
1. I have timeshift on all the time (in fact, I do not see much use and convenience of timeshift only on demand, i.e. that user must switch it manually first); therefore I use Permanent Timeshift.

2. To avoid unintentional lost of timeshift buffer e.g. by accidental switch to another channel, I adjusted "number zap" function in live watching mode so that I have to press Enter to confirm the choice. To be frank, I almost never use numbers for zapping, as I like to go through EPG viewer or Channel Selection screen to see what is going on on other channels. Sometimes, I use the history buttons to circle between few last used channels. Side note: with the dynamics in satellite channels availability, the numbers are not stable and I do not bother to remember them except just few (not to mention remembering by my female part of family:-)

3. I adjusted cursor left and right buttons to be skip buttons (left = -15 secs, right = +1 min) as: A. it is very convenient, B. they are to big to be history buttons, causing sometimes accidental channel switch.

4. To clearly see if I am currently in live watching mode or time delayed (and not to be bothered by permanent OSD) I have the time difference on the VFD. In case of delay as -mm:ss, in case of live TV as +mm till the end of current event. Moreover, when reaching live TV, it shows me respective message for about 1 second.

I know that many people use timeshift different way (as only FF/RWD vs. skipping discussion showed) so just take it as an inspiration if you want.

[maigais]

Timeshifting problems with OpenPLi 2.1

Attached Files

•  screenshot.jpg   65.46KB   46 downloads

Edited by maigais, 4 February 2013 - 09:12.

[littlesat]

This is not related to this thread... it could simply not find where to store the timeshift....

[littlesat]

I think we should get the actionmap fixed, so we can just skip back from the live point.

Possibly in python we need to check for timeshift enabled in cpp instead of active... when in live timeshift is not active... (But we get into spooky kind of code here).
In python they check for timeShift is active and this checks for enable && not live in fact... When isActive returns true when timeshift is enabled I suggest backskip will work when in live mode.

Edited by littlesat, 4 February 2013 - 09:34.

[pieterg]

I think the infobar knows about the three states:

1. live tv, no timeshift
2. timeshift, behind the live point
3. timeshift, at the live point (osd displays 0.00 and the play symbol, so I'm quite sure this is a separate state, not the same as 1)

I don't think we should combine 2 and 3, as you're suggesting.
Having separate states allows for different actionmaps.

[littlesat]

Then at 3... the skip buttons are currently disabled.... As in phyton there is a check for timeshift being active... that means 2 in your summary.
A check for being in true Live mode is not available in python... python can only poll for isActive. And the timeshift_enabled is a shadow from cpp with no guarantee that it is in synch.....

Edited by littlesat, 4 February 2013 - 10:42.

[SpaceRat]

I don't see any relevant difference between 2 and 3.
Timeshift is timeshift is timeshift.

[littlesat]

Nope... you have timeshift in real timeshift mode... and timeshift recording while you watching live.

[SpaceRat]

However, there is no relevance for the user.

[littlesat]

There is a difference.... the user is watching live and the user interface behaves a bit different.

[SpaceRat]

There is a difference.... the user is watching live

Yes, but it is still timeshift ...

and the user interface behaves a bit different.

Which is confusing.

There IS no relevant difference between being 1 msec behind and being 0 msec behind. A proper user interface will behave identical. If it currently doesn't, fix it, it's broken.

[littlesat]

That was exactly what I was considering.... let the isActive return timeshift_enabled and the user can skip back when playing live as there is no differnce....

But when doing so on some boxes there is no way to quit timeshift...... not all remotes have a STOP button....