FFAStrans forum

Hey tom,

it is never wrong to know a little regex;-) it is heavily used here and there in commandline tools, programming etc... It's just one of the best ways how to work with strings.

ThomasM wrote: Mon Feb 11, 2019 3:48 pm mea culpa - I installed ffastrans into c:\programs, but that is supervised by windows. So changes to scripts were not possible. Later I figured that out. Outside the Program-Folder everything works and the nodes are "sync" or "wait for Files..." as expected.

Having ffastrans in c:\program files is ok but sure the user executing ffastrans (e.g. the user you set to the windows service) should be able to write in the sunfolders. Sure you should take care that the "working" directories are set to some other drive than c:\

ThomasM wrote: Mon Feb 11, 2019 3:48 pm It is a good advise that the Hold node also functions as a junction back to one workflow - I was not aware of that.

Take care, i learned that synchronizing does not junction back, it just waits at this point for both jobs to come there but still all nodes after the hold node are executed multiple times

Cheers!
emcodem

emcodem wrote: Mon Feb 11, 2019 8:08 pm

ThomasM wrote: Mon Feb 11, 2019 3:48 pm It is a good advise that the Hold node also functions as a junction back to one workflow - I was not aware of that.

Take care, i learned that synchronizing does not junction back, it just waits at this point for both jobs to come there but still all nodes after the hold node are executed multiple times

Hi emcodem,

I will take care of that... I have a bunch of .AVIs run over night (about 1TB of data). I´m curious if it works now. The original workflow was split in two: One for "Recherchekopie" and one for "Ansichtskopie". The latter was the spread one with the FPS-query-Nodes.

And yes... regex seems to be very powerful. I have to work on that definetly...

so long,

tom

Hi to all,

problem solved.

I re-wrote some of the workflow ("Scanner_Recherche_und_Ansichtskopie_aus_ProRes_SHARED") and put the controlling of files already transcoded to another workflow (The "AVI-to-ProRes"-Workflow). This is also more logical and more streamline. So the discussed Workflow here now ends with the two deliver-Nodes.

The "AVI-to-ProRes"-Workflow I mentioned above is the pre-decessor to the "Scanner_Recherche_und_Ansichtskopie_aus_ProRes_SHARED"-Workflow. It transcodes .AVI to Prores - .MOV from where the "Scanner_Recherche_und_Ansichtskopie_aus_ProRes_SHARED"-Workflow begins to groove. After the transcoding to ProRes the "AVI-to-ProRes"-Workflow copies the .AVI to a temporary destination-Directory. When copying is done it waits via Hold-Node on the Files supported by "Scanner_Recherche_und_Ansichtskopie_aus_ProRes_SHARED"-Workflow. These files are directly delivered to the archive-Destination. When all files are copied, the .AVI-file is MOVED from the temporary destination to the Archive Destination. This is done with a CommandExecutionerNode with MOVE-Command because the Temporary-destination is inside the Archive destination.

Until now, this works. When I am back in the studio I can provide the Workflows for better understanding what I have done. Maybe someone has ideas for improving...

cheers (and again many thanks to emcodem),

tom