I entirely agree. I was describing the current code state, not suggesting it was a good idea. It's left as it is for now, not because I like it, but because it's not ye decided what to do about it.peteru wrote:I don't see a good reason for that. I'd go as far as calling it a bug, based on the fact that the only code that calls getResumePoint() only does so when the cuesheet has no entries. That implementation looks buggy to me as well. It will not allow you to resume if the cuesheet has edit points but no resume point. Notice that I say cuesheet, rather than .cuts file. This is because there could be other sources for cuesheets, such as DVD navigation or embedded chapter marks in MKV files, etc.prl wrote:There is explicit code in InfoBarGenerics.getResumePoint() that prevents it from returning a resume point if the stored resume point is for a recording.
However, not returning valid resume points is so broken that perhaos I should remove that block from the code anyway.
I haven't changed this in my current implementation of #537: Improve resume point setting performance in media player.peteru wrote:...I'd rather if you didn't. I think doing so introduces inertia in the wrong direction. ...prl wrote:for the current implementation, I could simply stop putting resumepoints for recordings (and .ts files) in the cache