Jump to content


Photo

Why does nobody care about Permanent Timeshift?

Timeshift

  • Please log in to reply
24 replies to this topic

Re: Why does nobody care about Permanent Timeshift? #21 Rob van der Does

  • Senior Member
  • 7,262 posts

+163
Excellent

Posted 12 December 2016 - 09:17

So waiting for a fix for a plugin that isn't needed and leave it crashing in the mean time? Not my idea of maintaining feeds.



Re: Why does nobody care about Permanent Timeshift? #22 littlesat

  • PLi® Core member
  • 43,235 posts

+436
Excellent

Posted 12 December 2016 - 09:23

When you remove it, it is forgotten for ever ;)....


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W Thanks to Henksat

Re: Why does nobody care about Permanent Timeshift? #23 Pr2

  • Senior Member
  • 2,194 posts

+81
Good

Posted 12 December 2016 - 09:26

Suggestion:

- create a new feed with plugins that are reported to make crash OpenPLi so if people install them anyway they have been warmed and if developper(s) or any other member(s) want to fix them they will know that those plugins get troubles with OpenPLi.

So plugin are not lost forever (people looking for them will know that they exist but doesn't work properly) and this gives a chance to fix them and 6 month later if the plugin is not fixed then it can be removed from this "buggy feed".


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

 

Xtrend ET-9000 Openpli RC6.0: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W  + Sundtek DVB-C
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C


Re: Why does nobody care about Permanent Timeshift? #24 Rob van der Does

  • Senior Member
  • 7,262 posts

+163
Excellent

Posted 12 December 2016 - 09:38

When you remove it, it is forgotten for ever ;)....

You can leave the plugin in the repos, just not build it.



Re: Why does nobody care about Permanent Timeshift? #25 littlesat

  • PLi® Core member
  • 43,235 posts

+436
Excellent

Posted 12 December 2016 - 09:49

But then nobody notifies us that it does not work anymore.... ;).... (LOL)

By the way... and this is a lot of work... actually the complete timeshift stuff needs a big/huge revision... by making it a really timeshift..

 

e.g. by a defined buffer (e.g. 2 hours)...

it continue recording while you zap... it starts recording the next channel (when you want to keep the current program you need to start an instant recording e.g. via a popup it can remember what was in that timeshift).

 

etc... etc...

 

But nobody of the "Timeshift' bodies tries to make this really great...

 

The complete timeshift stuff made years ago is not what it should be... And a plugin like PTS makes it even worser... (as it works-a-round what was wrong in E2 - because as far I understood DMM was not willing to adapt suggested improvements - that is also the reason why it needs an additional binary - which is wierdness)....

 

Rewrite it from scratch is the best option and as I'm not really using it, and also c++ code needs to be completely revised, it has not my priority....

 

Hopefully someone stands up and is willing to make (permanent)time shift really as it should be... (I'm willing to adapt the UI)....


Edited by littlesat, 12 December 2016 - 09:59.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W Thanks to Henksat





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users