Panasonic P2

[lieberreich]

Sry for my incompetence but It looks like advanced stuff for me. Maybe attachment will help. As you can see 2nd line of nodes works great (and i need it too). Main task is to make workflow for p2 just like for usual media files. Can i ask you to modify attached file if it doesn't bother you?

[emcodem]

Sorry, i was under the impression you were already friends with the mighty populate variables processor.

Here is how i applied the option2, which assumes that a CONTENTS folder is always the root of each and every P2

emcodem_proxy.json

(10.48 KiB) Downloaded 310 times

[lieberreich]

To be honest i started using FFAStrans last week

[emcodem]

hehe i see well you might want to know, the biggest problem for me is to guess what exactly you want to do in your watchfolders, e.g. in the p2 watch, do you want to allow just a CONTENTS folder to be dropped in or you expect some massive structures containing weeks of captured material, each of the folders for the week, containing a day and a card specific folder...

Options how "users" can use a "watchfolders" are kind of hard to foresee.

In difference if you told me that it is not a "user" but some "system" feeding the watchfolders that always delivers the same folder structure, it would be kind of easy to deal with it.

[lieberreich]

Sorry, i was under the impression you were already friends with the mighty populate variables processor.

Here is how i applied the option2, which assumes that a CONTENTS folder is always the root of each and every P2
emcodem_proxy.json

I tried to use your workflow, but it doesn't delete any file from incoming folder
got that message
Process exited with error code: 1 (\u040b\u0438\u0401\u040e\u0404  \u045e \u0431\u0401­\u0432 \u0404\u0431\u0401\u0431\u0490 \u0404®¬ ­¤\u043b.\r\n)",
"last_std": "\u040b\u0438\u0401\u040e\u0404  \u045e \u0431\u0401­\u0432 \u0404\u0431\u0401\u0431\u0490 \u0404®¬ ­¤\u043b.\r\n"

[lieberreich]

Watchfolders are specifed) FFastrans is used as separate render module

[lieberreich]

System can deliver structures like “folder1/contents”, “folder2/contents” but as I tested ffastrans handles that situation well. In watchfolder it will look like “!in/folder1;folder2;folderN”
All of folders will contain only one “contents” folder. But in “!in” folder may contain single *.mp4 file (not P2) and simple ffastrans folder node with deny instruction starts to work. And it works great, but only P2 doesn’t want to be deleted (for whatever reason)

!in/
Folder_name_1/
CONTENTS
Folder_name_2/
CONTENTS
...
Names may be different but P2 node works anyway

[lieberreich]

Thank you! I have read about cmd commands. Looks like you right and “rmdir” is what I need. Now I just need to check if render is still going, if not > rmdir, but how to do it . So many questions

[admin]

Hi lieberreich,

Interesting topic you arise here!
You have exposed some shortcomings of how the special monitors are integrated with FFAStrans in general. The problem is that the monitor returns both a set of files which is the actual media files and the original XML files which is actually the one it picked up when monitoring the folders. FFAStrans is designed to work with one source file, not multiple. So the multiple P2 files are available to FFAStrans in a nice structure but you cannot do anything with it currently. Deleting %s_original_full% will not cut it cause it only holds, as you discovered, the initial picked up XML files. The other multiple ones are "hidden". And if it was exposed, you still could not use the command executor in a simple way to delete the files.
The normal way to deal with this is to have special nodes that are aware of these files where you can perform delete, move etc. on the original P2 file sets. This is currently not on the road map but your topic may give us some push to further discuss the problem. And because the way you use the P2 monitor you would probably be a perfect test user

But back to what you're trying to do. It's actually not easy cause you cannot just delete the CONTENTS folder after a transcode because it can hold other files that are being processed. The only way you could easily come around this is to select the "Combine all clips into one" option which will take all the clips in CONTENTS and merge them. That way when you're finished you can delete the entire CONTENTS folder. But I take it that is not what you want to do. You probably want to delete the individual spanned clips, and this is the hard part. FFAStrans parses all the XML files to find all corresponding clips but that's not easy to do without some complex scripting or programming. Certainly not feasible within the current bounds of the inbuilt FFAStrans features available to the user. But I will try and discuss it internally with @emcodem and see if we can come up with a solution.

Another strange thing you encountered is the weird formatted error message. Could you please export the complete log for this job? We are very curious about what it is. Just right click on the job in the monitor and select "Open log folder...". Then pack all the files in a zip/7z file and send it.

Thanks!

-steinar

[lieberreich]

Thank you for responding! I was thinking about safe deleting and come to conclusion that I can just use if “number of successful renders” = “number of files in folder” then “rmdir”. Nom I’m trying to use both %s_original_path% and cd.. in command executor to navigate in selected folder