arkolbus wrote:Many of these episodes initially reported a very short duration (like 0 sec), so during playback PT has to keep extending the length (although at increasing intervals). This may not be the case for all of the problem episodes, but I noticed it for several.
Ok, so you were seeing duration issues. Basically the issue is that the media player is sometimes really bad at determining the duration of some files. It just reports the duration as some time, X, which may or may not be the actual duration. Sometimes, like with what you're seeing, X is actually much less than the actual duration, and the file plays past X. PodTrapper can see that we're now at position X+1, but the media player still insists the duration is X. The problem is that sometimes X is reported as 10 seconds on a 2 hour file. When that happens, if you stop the podcast and play another and I don't fudge the duration, it will look like it's complete, even if there's an hour left (since I can't know how much is actually left).
Is there no way to tell that playback has completed without comparing the reported playback time to the length of the media?
I do get an "end of media" event when the media has run out, but I get this in a lot of cases that have nothing to do with the end of the media (for example, when you pull the sd card, or it hits a minor corruption, etc etc etc). There are a lot of cases where that happens, pretty much whenever the media is stopped out of my control.
So really it's just a battle of heuristics trying to determine what the real duration is, if you're done listening, etc. The last change I put in was to counter the "Deleted before finished" issue, but I think I overcorrected and now have too much of a "never gets finished" issue. Unfortunately it'll never be perfect, but I have a lot of room to make it smarter than what it is now.
-Marcus