-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
delete_source not deleting files #28
Comments
It can be used without monitor or monitor_once. By default the intermediate files (these are the video files created that have the merged cameras on 1 minute intervals) are deleted from the moment the merged file for the folder was created. Using --keep-intermediate those files will be kept. |
So, this is what I am using
Without keep-intermediate, I don't get a single merged file. This is understandable because the per-folder intermediate files are deleted (which is used to create the complete merged file) However, at the end of the process, I have my original front, right and left files, the intermediate file and the merged file. All I want is the merged file. Is there a way of achieving this ? Here's the output from the script
|
I just checked the code, --delete_source indeed only removes the source file using --monitor or --monitor_once; will change this in next release. Not specifying --keep_intermediate should result in the merged minute files that are created to be removed. They are then removed when the 10-minute clip (all 1-minute clips from the folder) is created. The merged files on the folder level (normally the 10 minute long clip then) currently would always be there as there is nothing in the code to remove that. Ran similar like yours, running it without --keep_intermediate does result in the final merged file being created for me. The 10-minute clip files are still there but the 1-minute clip files are deleted. Hence not sure why you are not getting the final merged file then. Can you run it without --keep_intermediate and provide me the output? |
Here's the output
Here's the resulting directory structure.
|
FYI, not ignoring this. Just haven't had time with end of school stuff for the kids etc.. :-) I will be looking into this and ensuring it is fixed in the next release however. |
No worries. It's a long weekend; Have fun! I have just created a quick batch file to help me sort it all out. It's a quick hack, but just putting it here in case it helps someone.
I know you mentioned you'll take care of delete_source. I think that should be good enough for me. Even now, I can get rid of all files with _front _repeater and it will do it, but I'd rather have it be included in your script to guarantee that the files have been processed |
Semi-related to this issue - I am also using this script with a NAS, which my Raspberry Pi copies to automatically upon connecting to WiFi (https://github.com/marcone/teslausb). Would it be possible to have a different flavor of --monitor that periodically (I'm thinking in the middle of the night to avoid starting to process files while my Raspberry Pi is still copying files to the share) checks for new folders, instead of looking for TeslaCam to be mounted? |
This is something I've already been thinking off to be able to do. My thoughts on this was for example when someone is using it with a cloud service, they could copy the files up there and then it would start doing the merging etc.. But in the end solution would work for your case as well then. :-) Would you mind just opening a new issue for this with the request? Won't be in next release (going on vacation so want to have the next release out before then as it also includes some fixes). |
Done, thanks. |
FYI, Just released test version that includes option for --delete_source when not using --monitor and fix for reported issue: |
Release v.0.1.10 has been made available with the fix: |
Is delete_source designed to be used in conjunction with monitor or monitor_once ? When I use that on my NAS, it does not delete the files that have been merged.
The text was updated successfully, but these errors were encountered: