Open kissake opened 2 years ago
Possible approaches to mitigate this issue include:
Another tool to simplify locating useful information is to combine sequential segments of data into larger batches so that they can be processed at once. If other indicators can be retained (e.g. relative timestamps?), that would be ideal. Note that at this time the audio recording is explicitly cut early, with ~5 seconds of "grace", to avoid the next cron started recording from failing because the previous recording still holds the lock on the audio devices. This will cause some skew that will (for large number of sequential recordings) result in timestamps not being maintained if the recordings are simply concatenated.
A strategy for mitigation:
The ideal would be to extract this data along with timestamp information into individual files, I think?
Given that someone is likely to sleep for 8 hours at a time, and reviewing 8 hours of data (audio recordings) in 10 minute increments is ... a lot (could take more than 8 hours), it is important to facilitate review.