FFAStrans forum

Hi all,

Firstly, let me say, I am loving the latest FFAStrans, it is a great tool!

I am having a little issue, I want to create a Preset Folder node, where the path being watched is:
\\Server1\Deliverables\FILE_PROCESSING\%s_wf_name%

But when I have this applied to a workflow (for example opatom_dnxhd_36_25fps), it does not automatically kick off the transcodes, if I change the watch folder path to:
\\Server1\Deliverables\FILE_PROCESSING\opatom_dnxhd_36_25fps

It does work.

Am I missing something, or is there a way to troubleshoot this?

Many thanks!

Hey crazytiger, great Nickname and yeah, the software is great but no need to repeat yourself, you already said this back in 2017 hehe

I fear at this point (so at the "monitor" processor), you can only use
-) STATIC variables
-) Time variables
-) Winows variables

We shall discuss this topic internally and add it to the wiki/documentation of the monitor processor.
Sorry for the bad news

Hi emcodem,

Yes it's been a while!

Thanks for that, no problem, its a small issue.

Thanks for the feedback!

Hello Crazytiger,

In my opinion, what you want to do is a little bit weird...
1 / If you enter "\\Server1\Deliverables\FILE_PROCESSING\%s_wf_name%" to view a folder that it has not been created before, it cannot work.
2 / If you create this folder and use "\\Server1\Deliverables\FILE_PROCESSING\%s_wf_name%" -> ok it doesn't work and it should be.
3 / If you create this folder manually, what is the purpose to use a variable in the path? You can easily browse it. More, if you change your workflow name(and the folder where the watch must be), the new folder will have to be created manually so easier to browse it. Hope you understand what I mean.
Anyway, it is true we have to avoid this nonsense inside FFASTrans, we will discuss it.
Please tell us what is your purpose, I should undestand your goal

Cheers.

Benjamin

PS: I added a special note on wiki to explain only static, time and windows variables can be used.