Yeah, I'm seeing the "file can't be found" problem as well but it only effects certain clone. Other clones work fine so the cause is probably going to be a real bear to find. What's weird is that if I play back the clip immediately before the "file can't be found" error, when the clip I click on is finished playing it proceeds to play the one that "can't be found". My guess is some kind of marker, or ID for the clip is being screwed up somehow.
You're clicking on the file when it's still a 'snapshot' and it plays, but when the trigger times out without alerting, it goes away--I'm sure you and Teaf have your .db and New folders on the same drive right?
When your cameras trigger, a .dat file is saved in the Alerts folder even if the alert is cancelled...when you analyze these by dropping them in the DS tab of the status window, what are you seeing? I'd be curious to see what analysis looks like for anyone who's having these issues.
Edit, I just reviewed one of my cameras expecting an alert, but there was none....review of the .dat file shows plenty of opportunity to confirm both a person and car; it even had the asterisk in the first frame at T+0, but there was also an Error 100 in the Custom portion of that frame...speculating that's why the alert wasn't saved even though it was confirmed. However, on a different cam, an alert was confirmed and saved at T+0 but had Error 100 in three of the five analyzed frames... frame 1 & 2 were error free, but the 3-5 had the Error 100. It looks like the alert was confirmed and marked for saving before the Error 100 could interfere. I haven't tried removing the custom 'dark' from the process yet to see if that resolves the problem. And for anyone following along, I also disabled facial recognition a couple of updates ago.
These Error messages you all are reporting, are they solely in the custom section of the frame?