Tuttle OFX is a library to connect and batch operations with OpenFx plugins. It comes with a set of plugins that allows you to batch process on movies and file sequences.
g.compute( writer, tuttle.ComputeOptions(1000) ) //< here we ask the frame 1000
First we should be able to ask the frame "1.8" if we have a retimer in the graph. So parameters should be "double".
We need to add an option, with an enum to choose the time unit used: seconds or frames.
g.compute( [writer1, writer2], tuttle.ComputeOptions(1.23, 5.5, eTimeUnit_second) ) //< here we are asking to compute the time range from 1.23 to 5.5 seconds.
Discussion:
As the timing is specific to each node (time offset, retimer and fps changes) it maybe should be setted by node and not as a global ComputeOption argument?
g.compute( writer, tuttle.ComputeOptions(1000) ) //< here we ask the frame 1000
First we should be able to ask the frame "1.8" if we have a retimer in the graph. So parameters should be "double".
We need to add an option, with an enum to choose the time unit used: seconds or frames.
g.compute( [writer1, writer2], tuttle.ComputeOptions(1.23, 5.5, eTimeUnit_second) ) //< here we are asking to compute the time range from 1.23 to 5.5 seconds.
Discussion: As the timing is specific to each node (time offset, retimer and fps changes) it maybe should be setted by node and not as a global ComputeOption argument?