Recursive files and folders on a different drive

[kimble]

Hi there,

First off, great program. I can't believe I have just found this. You could do with some better SEO!

Now I have an issue that I really can't get to the bottom of and I'm not sure if it's me or a bug.

I want to watch a folder on the m: drive and convert and then replicate the structure on the i: drive.

I can manage to get everything working fine apart from the replication of the directory folder on the target. I swear I have tried all the alternative output %vars% but nothing seems to do what I want.

As an example, what I was to do is:

m:/folder1/folder2/1.avi -> i:/folder1/folder2/1.mp4

It would seem obvious that I use %s_original_folder% which should be path of original without UNC or Drive but when I do this folder2 is not recreated.

Can anyone verify this works or where I might be going wrong?

Thank you

[admin]

Hi kimble, thank you for using FFAStrans and welcome to the forum!

I'm having problems with recreating your issue. The variable you're using is correct and it's working perfectly in my test. Where and how are you using the variable?

-steipal

[kimble]

Ok so further information. If I just use the %s_recursed_path% prefix on a file in a watch folder thus:

1/2/3/file.avi

it get's converted to:

1/2/3file.avi

Why is the 3rd folder name being merged into the file name? This looks like a bug to me unless I have make some declaration on what's the path and what's the actual filename. Can anyone advise?

[kimble]

Hi Steipal,

I was posting as you replied so excuse the lack of acknowledgement in previous reply

I've been doing some more tests and the same problem seems to occur with the %s_original_folder% variable. The 3rd folder name gets added to the front of the clip name.

Can I send you my workflow or something to assist?

[admin]

Yes. It's easier to help if you show us how you use the variables. It might be a missing backslash (\)...

-steipal

[kimble]

Actually I think I might know what my issue is and I need a \ after the var. With my simplified test this becomes apparent.

[kimble]

Yes. It's easier to help if you show us how you use the variables. It might be a missing backslash (\)...

-steipal

This looks to be exactly what it is. Now I feel so stupid

Thank you.

[admin]

Hehe, working with paths in variables can sometimes be tricky Glad you sorted it out.

-steipal

[Jason]

can you send me the workflow ?

[emcodem]

@Jason
welcome to FFAStrans and thank you for using the forum!
Sorry i should have answered earlier.

You can use this workflow as starting base.

Copy_Folder_Structure.json

(3.78 KiB) Downloaded 7 times

You will need to change the "source and target" Base directory in the populate processor. Unfortunately there is no variable that allows to access the "watched folder", so you need to enter the watchfolder twiche, once in the first monitor processor and second time in the populate "source base path" variable.