You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any thoughts on this issue? We are currently experiencing issues about this in our project, was this one of your goals? I think you describe something about this issue in processall, but unfortunately i don't speak italian :(
So how do I know when It is okay to access the memory, when the camera wants to store a picture simultaneously?
The text was updated successfully, but these errors were encountered:
First of all, I promise to translate the comments to English.
Then, could you clarify what exactly is your doubt? I assume that after a photo is written on the SD, it will not be modified again by the camera. So I can do what I want with it, ie wiping it with an encrypted version.
The only tricky part is understanding when the image has been fully written. If that's your doubt, I think that many eurhistics can be used if you don't care about realtime. For example you could:
check the size every second. When it's not increasing, it's done
(maybe) check some JPEG fact which should tell you if there's any issue
check the size every second. When it's not increasing, it's done
generally i like this idea, but the problem i see here is that we have to remount the SD card in order to detect new images. but how do we know at which point in time the camera is not writing to the sd card so we can remount safely?
Any thoughts on this issue? We are currently experiencing issues about this in our project, was this one of your goals? I think you describe something about this issue in processall, but unfortunately i don't speak italian :(
So how do I know when It is okay to access the memory, when the camera wants to store a picture simultaneously?
The text was updated successfully, but these errors were encountered: