FFAStrans forum

Thank you. Tried but not sure what to populate for the Input and Output fields of the custom processor. Default is:

OPAtom video or audio file = %s_source%

AVSource = %s_source%
Created FFmpeg line = %s_file_list%
List of Found files = empty

Hey @Julica67
i believe @momocampo is working on some examples or description. Did you read the help?
By default, you don't need to do anything but just "hit OK once" after inserting the proc in your workflow, no change of the default settings.
This will lead to the follow-up nodes, e.g. filters and encoders to work as expected. While encoding, the source files are being accessed directly, no need for a op1a copy before encoding.

Another way of operation is when you just want to rewrap to OP1A (or mov, or.... ) , without filtering and encoding. In this case you need to provide a user_variable as you did for the "Created ffmpeg line" and use this variable in the next processor which is then most likely a commandline proc. Look in the help for an detailed example.

Hello,
@Julica67

Here is the page on the wiki, hope it will help you and others

http://www.ffastrans.com/wiki/doku.php? ... mxf_opatom

Cheers.

Benjamin

Thank you for the details, really appreciated.
I think something is not right with the custom processor, I can use aaf_linked but got an error in the processor:

....bb9994acd345","type":"plugin_htmlgui"},"split_id":"1-0-0","event":"_run_sys","type":"trace","data":"Input Source File: { id: 'source_file',\n value: 'I:\\\\AvidMediaFiles\\\\SONYSVRN7F1982C269D175351_v1.mxf' }\nInput Cache_dir: i:\\.ffastrans_work_root\\20200619-1020-2406-5961-8583ac05a740\\20200619-1225-3928-0dbb-3f8f2bd41bd7\nE:\\Program Files\\FFAStrans1.0.0\\processors\\plugin_nodes\\custom_nodes\\AV MXF OpAtom\\bin\\app.js:22\r\nvar force_32 = o_job[\"workflow\"][\"special\"][\"force_32bit\"]\r\n ^\r\n\r\nTypeError: Cannot read property 'special' of undefined\r\n at Object.<anonymous> (E:\\Program Files\\FFAStrans1.0.0\\processors\\plugin_nodes\\custom_nodes\\AV MXF OpAtom\\bin\\app.js:22:33)\r\n at Module._compile (internal\/modules\/cjs\/loader.js:678:30)\r\n at Object.Module._extensions..js (internal\/modules\/cjs\/loader.js:689:10)\r\n at Module.load (internal\/modules\/cjs\/loader.js:589:32)\r\n at tryModuleLoad (internal\/modules\/cjs\/loader.js:528:12)\r\n at Function.Module._load (internal\/modules\/cjs\/loader.js:520:3)\r\n at Function.Module.runMain (internal\/modules\/cjs\/loader.js:719:10)\r\n at Object.<anonymous> (E:\\Program Files\\FFAStrans1.0.0\\processors\\plugin_nodes\\custom_nodes\\AV MXF OpAtom\\bin\\processor.exe:352:30)\r\n at Module._compile (internal\/modules\/cjs\/loader.js:678:30)\r\n at _third_party_main.js:37:36\r\n"},
{"created":"2020-06-19T12:25:46.627+05.00","host":"DESKTOP-2IDN1VF","pid":14912,"node":{"id":"20200619-1020-3852-7df5-bb9994acd345","type":"plugin_htmlgui"},"split_id":"1-0-0","event":"","type":"error","data":{"command":"\"E:\\Program Files\\FFAStrans1.0.0\\processors\\plugin_nodes\\custom_nodes\\AV MXF OpAtom\\bin\\processor.exe\" \"i:\\.ffastrans_work_root\\20200619-1020-2406-5961-8583ac05a740\\20200619-1225-3928-0dbb-3f8f2bd41bd7\\1-0-0~200619122545949~14912~20200619-1020-3852-7df5-bb9994acd345~plugin_htmlgui.inputs.json\" \"I:\\AvidMediaFiles\\SONYSVRN7F1982C269D175351_v1.mxf\"","code":1,"msg":"Error, exit code 1 Input Source File: { id: 'source_file',\n value: 'I:\\\\AvidMediaFiles\\\\SONYSVRN7F1982C269D175351_v1.mxf' }\nInput Cache_dir: i:\\.ffastrans_work_root\\20200619-1020-2406-5961-8583ac05a740\\20200619-1225-3928-0dbb-3f8f2bd41bd7\nE:\\Program Files\\FFAStrans1.0.0\\processors\\plugin_nodes\\custom_nodes\\AV MXF OpAtom\\bin\\app.js:22\r\nvar force_32 = o_job[\"workflow\"][\"special\"][\"force_32bit\"]\r\n ^\r\n\r\nTypeError: Cannot read property 'special' of undefined\r\n at Object.<anonymous> (E:\\Program Files\\FFAStrans1.0.0\\processors\\plugin_nodes\\custom_nodes\\AV MXF OpAtom\\bin\\app.js:22:33)\r\n at Module._compile (internal\/modules\/cjs\/loader.js:678:30)\r\n at Object.Module._extensions..js (internal\/modules\/cjs\/loader.js:689:10)\r\n at Module.load (internal\/modules\/cjs\/loader.js:589:32)\r\n at tryModuleLoad (internal\/modules\/cjs\/loader.js:528:12)\r\n at Function.Module._load (internal\/modules\/cjs\/loader.js:520:3)\r\n at Function.Module.runMain (internal\/modules\/cjs\/loader.js:719:10)\r\n at Object.<anonymous>

Ouahh!! A big one yes
I think @encodem will be able to help you.
Strange because I tried it and it works well.
Can you tell us if you do a rewrap or a decode+encode plesase?
Thanks.

Benjamin

Same error on the re-wrap. Maybe the processor I downloaded is not the right one?

Well that is a Bad catch, we need at least ffastrans Version 1.005. I guess you are running 1.0.0?
On ffastrans.com, scroll a little down and download the 1.0.0.5 Patch please.

emcodem wrote: ↑Thu Jun 18, 2020 2:01 pm And there we go. Here is your Plugin Processor @Julica67:
http://ffastrans.com/wiki/doku.php?id=c ... processors

Usage example:
-) set the "Monitor" processor to accept only *V01*.mxf (only the video file of the OPATom structure)
-) after the monitor, use the OPAtom (you find it in in category Decoders)
-) after the OPAtom decoder, use any Filter and or Encode node just as usual (as you were using the stock A/V Decoder processor)

BTW, what if any of the atom files does not contain *V01* - some of the third party ingested files do not contain V and audio identifiers.
Also, the file grouping seems to be taking several seconds to return the list of files in the same clip.

If you cannot determine by using a file "name filter" if it is a video or audio file, you just set your watchfolder to watch for all *.mxf files. But to prevent processing the same file multiple times, you need to use a conditional node and check for something that qualifies the uniqueness. Make sure to check the "dispel" checkbox in the conditional.
There are many other options for that, e.g. watch for one file that comes only once for the sequence (e.g. xml) and parse/translate the name of the video out of it. The number of different options is exactly the reason why it is a bad idea to have this functionality in a "monitor" processor - in that case you would be limited to a very small number of use cases (just like the P2 Monitor is).

And you are right, the "grouping" can take some time. Several seconds should be OK but if it gets minutes then let me know, in that case i need to optimize the file anylzing.

It takes about 8-9 seconds for a small number of files, I am wondering if the time increases with the files number in the folder.

BTW, how do I overlay a text in the transcode case? I see only watermark option for this case.