2015-01-12, 21:37
(2015-01-12, 10:00)speedwell68 Wrote:Yes and the figures can be adjusted in advancedsettings.xml.(2015-01-11, 20:42)mentat Wrote:(2015-01-11, 20:00)speedwell68 Wrote: I get this also. I thought it was a local caching issue so I modified my Advancedsettings.xml file to utilise the HDD instead of ram (I am using a Raspberry Pi) and it made no difference. It's no biggie if I need to pause the programme I stop it and resume.
I can also confirm this iPlayer (2.6.10) behaviour on my RPi (OpenELEC 5.0) with various combinations of cache settings.
I agree that using stop/start/resume is reasonable, however, as I use pause often (when viewing all other sources), I often forget to use stop (when using iPlayer).
I wonder if this issue is unique to RPi/OpenELEC/KODI, @ZaZen what are you running?
I would also like to take this opportunity to ask a question regarding logging (in attempt to capture issues, such as this, in iPlayer).
@exobuzz (Alastair, BuZz, Dink, dlake02)
Do you require/recommend selecting "Enhanced Debug output" in Advanced (Settings - iPlayer)?
Is this option required to capture/log errors in iPlayer and if so, is it safe to leave on for "normal" operation/viewing?
Thanks.
Now you come to mention resume. Is there a minimum time you have to view a programme for until the resume function works? Last night I was playing with the functionality of my new MySQL server and was happy that when I had viewed an iPlayer programme it would show that on all 3 of my Raspberry Pi (all running Openelec 5) and on my Android tablets, happy. But when I tried to see if the resume function would work. I played a video for a few seconds and it wouldn't offer me a resume option on the Pi I was using let alone on one of my others. I know it has worked in the past.