Storing timecode for partially watched movies

[jeps]

Hi.

What I am trying to figure out is, where are those timecodes stored?

Normally they are remembered and the movie starts where I left it.
If I reboot the box, then all traces of the timecodes are gone.
Meaning all partially watched movies and TV-series start from the beginning.
Are they supposed to be stored in the media library for the individual file or what?

All my media is stored on a NAS and the mediabox has only read access (not write).
Is that a problem?

It is annoying to loose all the timecodes when the box freezes (and it does :-))

[netguru]

It does not work with NFS, but should work with smb, so ist in my case.

[Phil181]

Resume works fine for me after full switch off overnight, from multiple NAS units (Thecus, QNAP and Seagate Centrals). 
Allow it to write/save and you should be fine?

[Q10Pro on 2.0.4 using Ethernet-over-power]

[jeps]

Was afraid that someone might say that.

I had a bad (actually catastrofic) incident where I thought I said yes to deleting the media libary index and instead I had acknoledge to delete all my media files. You don't want to do that mistage again 

May be I should try once more and be really sure what I accept.

[drabisan]

In my case it doesn't work with a rw NFS share. I won't expect to be working on a read only share also. I didn't try with a SMB share.
So you're not alone

[jeps]

Okay, so the keyword is NFS or Samba shares.

I use NFS, so if I changed to Samba shares it would work?

[drabisan]

For some weird reasons when I add a SMB share I can't play movies with wrapper. It's a black screen. And this is since day one. I tried it today and the same with 2.0.4.
If I remember correctly it's about Kodi that's not passing credentials to wrapper and there's a strange workaround with mounting points. Or enable guest on storage (like anyone will ever do that)
NFS works but it doesn't resume. SMB has above mentioned problem. Granted it's a unit build with internal HDD in mind, but relying on network services should be a must they keep ignoring.

Personally I'm very close of giving this unit for free and buying a Zappiti...there are way too many small things that are pissing me off every day.

[futeko.com]

For some weird reasons when I add a SMB share I can't play movies with wrapper. It's a black screen. And this is since day one. I tried it today and the same with 2.0.4.

If it's a password protected share then you need to enter user/password details in wrapper app. My Apps - Wrapper.

You could also install this patch to mount multiple Samba shares to the filesystem, but it isn't necessary for just one password protected Samba share.

[drabisan]

I remembered yesterday to try putting the username&password in Wrapper and cjeck if the movie resumes. And it does.
So @futeko can ask Himedia to implement the same functionality over NFS. I'm sure there's no data written on my NAS, at least I can't find any trace Q10 Pro wrote anything on my storage, so "timestamp" for resume is stored on Q10 Pro and it shouldn't matter if the share is accessed via SMB or NFS (it looks more like a bug than a feature request). For what it matters there's no need for Q10 Pro to use an account with write permission to access NAS and still be able to resume a movie.

[futeko.com]

I will pass the need for NFS resume to work the same as SMB to HiMedia as a bug report.

[jeps]

Sounds good to me.
Although I am not totally convinced it is that simple.
I mean, why should this feature depend on the protocol (NFS or Samba) if the timestamps are stored locally on my Q5?

The timestamps work (90 %) on NFS if you don't reboot the Q5.
After a reboot all timestamps er wiped clean.

[futeko.com]

Sounds good to me.
Although I am not totally convinced it is that simple.
I mean, why should this feature depend on the protocol (NFS or Samba) if the timestamps are stored locally on my Q5?

The timestamps work (90 %) on NFS if you don't reboot the Q5.
After a reboot all timestamps er wiped clean.

It sounds like a bug (or at least a feature that was implemented for SMB and presumed to work for NFS also, but not properly tested).

[jeps]

Since I am going to do a full reset of the box, I would like to know if it has been confirmed to be a NFS bug.
I have changed to Samba just to for this issue, as it is really annoying.

I'm planning a reset and would rather "go NFS" since the user right is much easier to handle.
And also, is this behaviour registered as a bug at all?