Canon XF watch folder

[ring4life70]

Hello All

first of all thanks a lot for your amazing software, i'm finding a way to combine multiple spanned mxf from Canon XF card to a single Xdcam 1080 25p mxf file, here below my simple workflow:

Screenshot 2021-04-15 at 10.56.42.png (244.58 KiB) Viewed 5842 times

As you can see, i'm using a Canon XF node as monitor folder, and an xdcam encoder node that convert the files in XDCAM MXF, but when i copy CONTENTS folder of the card, in the Canon XF watch folder, process starts but the node pass to the encoder node only the first mxf in the list, at the end of my workflow, in the delivery folder i have only the fist mxf file and not an mxf with all the mxf files joined on it.
this is an example of my folder card structure:

Screenshot 2021-04-15 at 11.23.52.png (121.05 KiB) Viewed 5842 times

I don't understand what I'm wrong
Best regards
Ring4life70

[momocampo]

Hello Ring4 ,
Welcome here and thanks for using FFAStrans.
To be honest i'm not a pro in Canon monitor node, I never used it. But, I think if you use a standard monitor node, accept only "*.mxf" files and tick "recurse" it will be ok. All the mxf files will be processed.
Meanwhile, I'am going to ask to the team why it doesn't work with canon-xf monitor node.
Cheers.
B.

[ring4life70]

Hi momocampo, thanks for your feedback,
yes if i use a classic monitor folder with "recurse" option, the process starts but at the and of workflow i have one mxf for each file processed, what i need is a way to merge all the multiple spanned mxf ( as you can see in the second screenshot, contained in the folder AA0315 and AA0316) that i have in the source Canon Folder.
if i understand correctly when you use a Canon XF as watch folder, all the multiple mxf file contained in the folder are merged in a single mxf file and and passed to the next node, but in my case only the first one of each folder is passed to the encoder node, for example of the files in the screenshot, only the AA031501.mxf is processed, all the other ones are ignored.

[admin]

Hi ring4life70,

First I would like to know which version of FFAStrans you're using. 1.2 addresses several problems with the monitors. But regardless of that, the "challenge" with this monitor is to wait until all related files are present when picking up the initial file. Currently FFAStrans use the file pattern to find and collect all files in the set. However, it might be that the first files "AA031501.MXF/SIF" are copied first and when FFAStrans sees these files and the rest are waiting to be copied, it might be that it won't pick up the rest of the files cause they are not present.

The best way to solve this would be to dump all the files in a folder outside your monitored path but on the same share, and when card it completely dumped, move it to the monitored path. And if you would like to try if it gets properly picked up you can try and change the name of the "CONTENTS" folder and see if FFAStrans correctly detects all files and merge them. I assume you're not monitoring the "CONTENTS" folder directly but the rather the parent level?

-steinar

[ring4life70]

HI Steinar and thanks for your feedback,
yes i'm using 1.2 version of FFatrans, i've tested both solutions, dump all the files on the same share but in a folder outside my watch folder, and when card is completely dumped, move it to the monitored path, and change the name of the "CONTENTS" folder already present in the watch folder, but nothing is changed, always only the first file of each folder is processed.
As you can see in my first screenshot, after the Canon XF watch folder I have directly inserted the transcoding node, is this correct ?
just to understand, it's the node of the Canon XF watch folder that merge all the spanned mxf clips into a single one mxf, or after the watch folder I have to add a particular filter node ?

[admin]

Oh damn it! Found a bug

Ok, so I'll fix that and I'm going to let you try the new upcoming 1.2.1 that will have the fix. Sounds good?

Thanks for notifying!

-steinar

[admin]

Ok, sent you a PM with the link to the upcoming 1.2.1 version.

-steinar

[ring4life70]

thank you for your help and your time, I'm very happy to test this version but unfortunately, at the link you sent me in pm I get this error message:
"Sorry. You cannot access this item because it violates our Terms of Service".
I think is a limitation of google drive service, please could you send me the link using another share drive ?

thanks

[ring4life70]

Hi Steinar,
I'm very happy to confirm that I just tried the 1.2.1 version and the bug is fixed, everything seems to work well, now all the spanned mxd are merged and moved as a single clip to the next step.

thanks again
Ring4life70