Posts: 6,810
Joined: Jul 2010
Reputation:
198
That is an interesting question. Doing so would mean that you might lose content when you have paused playback. Consider the case that you have just paused a movie 5 minutes before end, then you have to leave for 30 min and the buffer gets overwritten. You would be disappointed.
There's also a worst case for the other solution.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
We could make this configurable, then the user can choose which death to die.
Posts: 220
Joined: Oct 2011
Reputation:
7
Yes, good idea. Both ways have their pro's and con's.
But the better way for user is: newer let the buffer overrun! I tested it yesterday many times and the result was disappointing.
Moving across the position with lost data will confusing xbmc again. The extreme situation was pressing BigStepBack moves forward, pressing BigStepForward moves 3min (permanently) instead of 5min, pressing StepBack does nothing again. It is currently totally unpredictable what happens after a buffer overrun occurs.
I think it would be very difficult to solve this problem, but we should think about a good strategy in such cases.
Kodi 18.6 @ openSUSE 13.1 x86_64 - Asus E35M1-I DELUXE | 8GB Ram | 240G 2.5" SSD
Kodi 20.2 on 1st Raspberry Pi B @ XBian | Kodi 20.2 on Raspberry Pi 3B+ @ XBian | Kodi 21a2 on Raspberry Pi4B @ XBian | Kodi 19.0 on SolidRun i.MX6 @ XBian
VDR 2.4.5 & Tvheadend4.3-1917 (for recording) on Cubieboard2 @ Debian Buster
Posts: 220
Joined: Oct 2011
Reputation:
7
Oh, good news.
Hopefully it will be working soon, so i'm waiting with further tests until it is available.
Kodi 18.6 @ openSUSE 13.1 x86_64 - Asus E35M1-I DELUXE | 8GB Ram | 240G 2.5" SSD
Kodi 20.2 on 1st Raspberry Pi B @ XBian | Kodi 20.2 on Raspberry Pi 3B+ @ XBian | Kodi 21a2 on Raspberry Pi4B @ XBian | Kodi 19.0 on SolidRun i.MX6 @ XBian
VDR 2.4.5 & Tvheadend4.3-1917 (for recording) on Cubieboard2 @ Debian Buster
Posts: 173
Joined: Jan 2010
Reputation:
1
te36
Senior Member
Posts: 173
My priority as a user is timeshift on a recording that is still in progress. I do not know the VNSI protocol, but i would hope that this is also the easiest option to implement. Maybe XMBC could simply re-check the length of the file when it has reached playing out to -30 seconds of the currently known length of the file.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
See post #29. Recordings in progress will be started by starting playback on the channel.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
Nachteule, seeking seems to be broken with recent changes from mainline. Did you observe the same?
Posts: 220
Joined: Oct 2011
Reputation:
7
No, not yet. I'm still using your osd branch and not the mainline and merged the patches from elupus into osd.
If i take your mainline xbmc branch, addon refuses to start
Kodi 18.6 @ openSUSE 13.1 x86_64 - Asus E35M1-I DELUXE | 8GB Ram | 240G 2.5" SSD
Kodi 20.2 on 1st Raspberry Pi B @ XBian | Kodi 20.2 on Raspberry Pi 3B+ @ XBian | Kodi 21a2 on Raspberry Pi4B @ XBian | Kodi 19.0 on SolidRun i.MX6 @ XBian
VDR 2.4.5 & Tvheadend4.3-1917 (for recording) on Cubieboard2 @ Debian Buster
Posts: 34
Joined: Jul 2012
Reputation:
0
jobe
Junior Member
Posts: 34
Hi FernetMenta,
is your master branch compatible with Frodo final? Or should opdenkamps repo be used for Frodo final?
Thanks for clarification.
Posts: 34
Joined: Jul 2012
Reputation:
0
jobe
Junior Member
Posts: 34
Oh, yes, sorry I just read your info on timeshift and you pointed out, that the most recent version is your master branch. So I wanted to know, if this will work with frodo final, to get timeshift to work.
Kind regards,
Jobe