sirdir

By the way, I tried it again. The InfoBarGenerics.py from OpenPLI does not work on OpenATV - as soon as I replace it enigma2 doesn't load anymore..

[InfoBar] Failed to load resumepoints: [Errno 2] No such file or directory: '/home/root/resumepoints.pkl'
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 30, in <module>
    from Screens import InfoBar
  File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 18, in <module>
ImportError: cannot import name InfoBarINFOpanel

I guess that's where it fails.

Anyway, to be honest, I don't really like the look & feel of OpenATV, I like the 'lightness' of OpenPLI.

I guess there will be a version for the Duo2 soon?

Regards

Patrick

When you usually skip ahead it will go to the next service.....

? That must be a setting I haven't found yet. By the way if you skip to the end with > you get to the end, even with the patch.

So what?

That is exactly the reaction that triggers why we should sleep on it... (LOL)

At least I would only recommend to follow the patch when the current played recording is also at that time recorded...

If you think so… I don't have any problem with those 3 seconds. Normally I never intentionally jump to the end of a finished recording (wouldn't see what good that would do ) so I don't see a problem there, or I'm even glad I get the chance to jump back without 'falling out' of it...

Of course I'm not against a perfect solution, it's just a question wether it's worth the effort or not. 

If somebody does it they should send it to DMM so they can't complain nobody is contributing to enigma2

And no side effects with normal recordings?

 

Still the patch gives me a "hacky" feeling...

 

And with a normal recording that is not growing when "stepskipping" forward you always see the last 3 seconds of a recording repeated.... WHen correctly programmed we should at least detect somehow if the played recording is still a growing recording...

Is this really a problem?

So instead of just falling out of the recording you see the last 3 seconds… so what?

I'd be surprised if it's any different in OE2.0 by the way.