Ben wrote: ↑Thu Oct 13, 2022 10:53 am
process.send("My comments here", [datestring]);
but it didn't work, cos I dunno what I'm doing haha.
ok so the idea is that you send an array and there will be one job started for each item in the array, so e.g. if you do
process.send(["first","second"]); you will end up having 2 jobs in ffastrans. For example, you could now go through a list of files, pick the ones you are interested and send the array of filenames using process.send. You would end up with one ffastrans job for each file.
If you want to just start one ffastrans job, you still have to send an array but only one item, e.g. process.send(["first"]);
So all you need to do to get to your goal is to first construct a string:
Code: Select all
var jobname = new Date().toISOString();
jobname += "_myawesomeaddition"
process.send([jobname]);
For debugging you do something like:
Code: Select all
var jobname = new Date().toISOString();
jobname += "_myawesomeaddition"
console.log(jobname)
and test run the script, you should see the calculated jobname in the log output.
Ben wrote: ↑Thu Oct 13, 2022 10:53 am
That sounds really good. I'm looking forward to the new release. I'm using the scheduler to fire off ffmpeg commands to record audio inputs at set times for set durations with very specific file names. Using variables and frequency I can control most of what I need all from the web interface.
But having the scheduled job know details of the workflow would take it to an even greater level.
Yeah i use it for starting ffmpeg recording from blackmagic
Have you got the latest pre-release version? There were some major updates to the scheduling stuff:
https://github.com/emcodem/ffastrans_we ... ag/1.3.0.1
Ben wrote: ↑Thu Oct 13, 2022 10:53 am
Perhaps having it in the main toolbar near the save button would be good.
Bulk selecting multiple schedules to perform actions such as enable/disable, test run, export and delete.
Folders to organise the schedules.
When adding in frequencies it defaults to 5 min. If I'm adding in a few entries each as 'every week', it'd be nice if the new schedule frequency I add remembers my last selection.
When job/s are Running allow the user to click on the Running box and it takes you to the job status page (hyperlink Running).
Make the log-in page mobile responsive (in case I need to check running jobs quickly on the go).
Uhh tahts a lot of ideas, most of them i already thought about but didnt do anything yet because i feel it would be more important to make it even more easy to use e.g. provide predefined condition scripts for example folder comparison and such. Anyway i'll see what i can do
Also we'd need a history of scheduled executions, e.g. there is no log about what it did and why...