Hey!
The program is great!
We have been using for a long time.
There is a video folder that is constantly updated (a lot of videos). The video should be stored for 2 weeks, and then compressed for the archive.
How to do delayed compression?
Delayed compression
Re: Delayed compression
Key klerbit,
thanks for using FFAStrans and welcome to the forum!
Sure a feature in the existing monitor folder processor to filter by date would be most elegant here but this would need a ffastrans update and that is not coming very soon i fear.
Any other way that comes to my mind involves comparing the 2 directories.
My way to do it would be like: use 2 Files Find processors, one to list 2 weeks old files in folder A, the other one list all files in Folder B. After that, we need some script that does not exist yet: compare the filelist from A to B and generate a list with stuff that is only found in A but not in B.
This "new processor" would need to output a list of files e.g. json array, which we can use in the for-each processor to start a new job for the found files.
Such a compare job would need to be started periodically, e.g. using the scheduler from webint or just on arrival of any random new file.
What you think, could it work for you, comparing the 2 directories and find out whats only in "A" and 2 weeks old?
Another way would be like to set a high sleep timer e.g. 1 hour and check in your workflow if the file is old enough, if not, delete the cache record and dispel the job (e.g. delete from job monitor). But that way you would have 1 job for each younger than 2 weeks file every hour running. You could further configure this job to run only on sunday or such.
So this way would lead to the users seeing 20 jobs acive and 200 queued (given that 220 files are younger than 2 weeks) every hour, each and every every job runs about 3 seconds.
thanks for using FFAStrans and welcome to the forum!
Sure a feature in the existing monitor folder processor to filter by date would be most elegant here but this would need a ffastrans update and that is not coming very soon i fear.
Any other way that comes to my mind involves comparing the 2 directories.
My way to do it would be like: use 2 Files Find processors, one to list 2 weeks old files in folder A, the other one list all files in Folder B. After that, we need some script that does not exist yet: compare the filelist from A to B and generate a list with stuff that is only found in A but not in B.
This "new processor" would need to output a list of files e.g. json array, which we can use in the for-each processor to start a new job for the found files.
Such a compare job would need to be started periodically, e.g. using the scheduler from webint or just on arrival of any random new file.
What you think, could it work for you, comparing the 2 directories and find out whats only in "A" and 2 weeks old?
Another way would be like to set a high sleep timer e.g. 1 hour and check in your workflow if the file is old enough, if not, delete the cache record and dispel the job (e.g. delete from job monitor). But that way you would have 1 job for each younger than 2 weeks file every hour running. You could further configure this job to run only on sunday or such.
So this way would lead to the users seeing 20 jobs acive and 200 queued (given that 220 files are younger than 2 weeks) every hour, each and every every job runs about 3 seconds.
emcodem, wrapping since 2009 you got the rhyme?
Re: Delayed compression
Hello Klerbit and welcome here !
If you want to delay some jobs, the better way is to use the webinterface :
viewtopic.php?f=5&t=789
This is a really useful tool and you can do a lot of things with it. You will delay your jobs with the scheduler: set day and time and webinterface will start the workflow !
For help, see the documentation here :
https://ffastrans.com/wiki/doku.php?id= ... binterface
Cheers.
If you want to delay some jobs, the better way is to use the webinterface :
viewtopic.php?f=5&t=789
This is a really useful tool and you can do a lot of things with it. You will delay your jobs with the scheduler: set day and time and webinterface will start the workflow !
For help, see the documentation here :
https://ffastrans.com/wiki/doku.php?id= ... binterface
Cheers.
Re: Delayed compression
Friends, thank you for the answer!
I will think how to implement =)
I will think how to implement =)
Re: Delayed compression
Let me know if you think a "diff" could work (e.g. filenames in the archive stay the same as in the hot folder). In that case, i'd prepare a corresponding processor for you. Again, how it would work: 2x Find Files, one in the hot folder, set to 2 weeks, the other one in the archive. Then compare the filenames only and output the files that were only found in the hot folder (and 2 weeks old) but not in the archive.
emcodem, wrapping since 2009 you got the rhyme?
Re: Delayed compression
Hi klerbit.
just an idea with dirty knowledge on CMD... Maybe you can use two workflows for that.
The 1st Workflow scans the original video-folder for files older 14 days. if it find Files older 14 days it moves them to the Watchfolder for the 2nd Workflow. This is done by a CommandExecutor-Node:
I´m sorry, but at this time I cannot confirm that this works with copy-and-paste, but maybe it is a starting point... Also check out https://ss64.com/nt/forfiles.html
cheers,
Thomas
just an idea with dirty knowledge on CMD... Maybe you can use two workflows for that.
The 1st Workflow scans the original video-folder for files older 14 days. if it find Files older 14 days it moves them to the Watchfolder for the 2nd Workflow. This is done by a CommandExecutor-Node:
Code: Select all
%comspec% /C "
FORFILES /p
"%s_original_path%"
/m *.mov /d -14 /C
"MOVE /Y
"%s_original_full%"
"Watchfolder\""
"cheers,
Thomas