Yes already incorporated into the current version of Crop on browse menuis it possible that when cutting the ads via the bookmark thingy to introduce a bookmark into the newly cut program? ie the shorter one. so we could easily check if the cut is done according to our wishes?
I have never noticed this happen. The majority of the crop operations I perform happen to be on a HD-FOX, and I review the post-crop to check whether it needs adjusting.Saving the new bookmarks can fail (more often than not in my several tests) when run automatically after cropping as part of the "Perform crop" function because the newly cropped file is "in use".
Correct. There is a major sweep during the shutdown process, and apart from that it seems hit-and-miss (can't recall what else triggers it, if anything).IIRC it has been determined that its DLNA index is not continuously updated
Bookmarks are stored in the .hmt file, so why would that be a problem?with my build of minidlna running, and that is what is accessing (presumably indexing) the newly cropped .ts file.
Do the Humax processes not respect an in-use status themselves? If so, it will always be a problem. If not, the usual method for obtaining control of a file in a multi-process system is:I'm experimenting with a retry loop if I detect files in use but the problem is that there are still timing windows - something could open a file an instant after checking the inuse status
Saving the new bookmarks can fail (more often than not in my several tests)
There is a major sweep during the shutdown process, and apart from that it seems hit-and-miss (can't recall what else triggers it, if anything).
How are you timing the sweep? What indicates that a sweep is running?The sweep can take around a couple of minutes (literally 120 seconds) to complete on my box, therefore don't expect to see results instantly.
I hadn't known about this but can confirm it happens,I have an observation about disappearing bookmarks (ones that are set by the custom software). This particular issue isn't caused by file locking. Sorry if this is already known.
I timed the sweep by:-How are you timing the sweep?
Nothing that I know of. You only know that the sweep has happened by watching an un-indexed recording until it becomes indexed.What indicates that a sweep is running?
One suggestion is to have a new log file "bookmarks_history.log" or similar. It could contain a single line for each recording that has been bookmarked by the WebIf/ ad detection etc. The format for the file could be single lines like this:-How we can detect and solve this will be an interesting problem, hopefully it is fairly rare but I wonder if it also affects viewing a recording shortly after it has completed recording
Not exactly - only during turn-off (not as a result of turning on).A FULL DLNA sweep is triggered when:-...
- Turn the Humax off and on
OK - so in other words if the box crashes then a DLNA scan does not take place when the Humax is turned back on? I have not investigated this scenario.Not exactly - only during turn-off (not as a result of turning on).
This.if the box crashes then a DLNA scan does not take place when the Humax is turned back on?
The test is...
Bookmarks are stored in the .hmt file, so why would [minidlna indexing the recording] be a problem?
[system inuse $file]
which looks for $file (the file.ts passed from Browse Files) being open. There's no check on the .hmt. Unfortunately post #10 also highlights there is also a case where the bookmarks can also be overwritten when the recording is not in useI guess the intention is mainly to avoid clashing with the settop program's use of recordings, where bookmarks can only be set if the recording's .ts is open. As post #10 implies that bookmarks set while a recording is playing will be overwritten, this is a Good Thing.
No it doesn't (but of course we can't update bookmarks once the recording has started playing)I wonder if it also affects viewing a recording shortly after it has completed recording