Page 3 of 5
Re: How do I input OP Atom files to create OP1A
Posted: Tue May 19, 2020 6:20 pm
by emcodem
Julica67 wrote: ↑
Understood. I was hoping a new monitor type would be implemented for getting the Avid OP Atom files form a folder, matched by the MaterialPackage UMID or Source UMID as an option.
Should I better create a Feature Request for this?
Hey Julica,
I already told you that this is a trerrible idea and explained why in this thead. Is there anything you can comment to my explainations before about this monitor idea? Whats the win besides saving 1 or 2 nodes?
Re: How do I input OP Atom files to create OP1A
Posted: Tue May 19, 2020 6:48 pm
by Julica67
emcodem wrote: ↑Tue May 19, 2020 6:20 pm
Julica67 wrote: ↑
Understood. I was hoping a new monitor type would be implemented for getting the Avid OP Atom files form a folder, matched by the MaterialPackage UMID or Source UMID as an option.
Should I better create a Feature Request for this?
Hey Julica,
I already told you that this is a terrible idea and explained why in this thead. Is there anything you can comment to my explainations before about this monitor idea? Whats the win besides saving 1 or 2 nodes?
Hi emcodem, I understand the monitor just looks for files but got wondering as on P2 case there are multiple files - how is the %s_source% populate din that case? Please indulge my ignorance until I fully understand the flow.
There is no issue from my point of view to have Folder monitoring >> File Grouping >> Processing/mapping >> encoding. From your explanation, I understand the challenge is to be able to send to encoder a list of files (or better say to use a custom FFmpeg script). Did I get it right?
My goal is to be able to get the OP Atom files and wrap or transcode to different types of destination formats, including the Avid project structure for a "low Res" transcode workflow with a potential watermark option. I hope this provides a bit more clarity.
Re: How do I input OP Atom files to create OP1A
Posted: Tue May 19, 2020 7:23 pm
by admin
The P2 monitor rewraps all clips to OP1a so you end up with one file output for the next node: %s_source%
However, I'm aware of the shortcomming of having just a file as source for all nodes but this is a legacy design. The total rewrite to 1.0.0 was important in order to allow more complex data exchanging between nodes. This will also pave way for more complex source structures but that has not been the focus yet.
-steinar
Re: How do I input OP Atom files to create OP1A
Posted: Tue May 19, 2020 8:40 pm
by emcodem
Julica67 wrote: ↑Tue May 19, 2020 6:48 pm
My goal is to be able to get the OP Atom files and wrap or transcode ...
Sure and we were on a good path already, i just need the file samples that were not grouped correctly uploaded from you.
There is no problem existing as you assume it, all i wanted to point out is that we need some engineering to make it faster. In case it turns out that avisynth is not able to read the separate opatom files, we can still have our "new" processor rewrapping the files before they hit the next processor. The issue is just that we need "a single file" before we hit any of the existing filters or encoders.
In my mind, a "monitor" is not more than just monitoring. Creating "a single file" out of a bunch of other files is something that a monitor should not do.
in the end we were already on a good path here: it does not matter for me if we need to rewrap the files to a single one or if avisynth is able to process the original files. In the end our new custom processor(s) will do what you want, you just need to give me the example files that did not work which i requested.
Re: How do I input OP Atom files to create OP1A
Posted: Tue May 19, 2020 9:40 pm
by Julica67
emcodem wrote: ↑Tue May 19, 2020 8:40 pm
Julica67 wrote: ↑Tue May 19, 2020 6:48 pm
My goal is to be able to get the OP Atom files and wrap or transcode ...
Sure and we were on a good path already, i just need the file samples that were not grouped correctly uploaded from you.
For you to better understand, i explain what a monitor has to do: it has to check if a job needs to be started and not more than that.
Monitor processors that do mire than check if a new job needs to be started, e.g. p2 or ftp, that do some magic automatical stuff like rewrap or ftp download are a legacy thing that happened when ffastrans was still in its early years. With version 1.0 it did get mature and knows how to do things correctly.
In your case, a job can be started as soon as the video file from the package is ready because it means that all other filers are ready too, and you can set the monitor to watch for videos only by including only v0,v1 etc.. so no need for a new monitor.
The rest of the workflow has to take care about grouping and such... the monitor monitors and processors do the processing.
This is why i am currently working on a processor that allows you to do what you like, i just need your input (wrongly mapped files) to go on and finish it.
Got it! Looking forward to try the processor. I have uploaded the sample to the link provided. Thank you!
Re: How do I input OP Atom files to create OP1A
Posted: Wed May 20, 2020 12:19 pm
by emcodem
Ah, great examples! That should suffice to fix the issues.
By the way, i have good news: avisynth ffms2 plugin can read the opatom files, so we don't have to rewrap them to op1a before encoding.
This means the "to be created" processor must run in 2 different modes:
1) generate a ffmpeg -i and -map string just as the example processor did. This enables one to do just rewrapping to e.g. op1a mxf or create any other custom ffmpeg command...
2) generate a .avs file in the chache directory, just as the "A/V decode" processor does. This enables to feed existing encoder nodes with the input files.
Anyway, now i need some time to check out how to detect the correct file couples from your uploaded samples
Re: How do I input OP Atom files to create OP1A
Posted: Wed May 20, 2020 1:47 pm
by Julica67
emcodem wrote: ↑Wed May 20, 2020 12:19 pm
Ah, great examples! That should suffice to fix the issues.
By the way, i have good news: avisynth ffms2 plugin can read the opatom files, so we don't have to rewrap them to op1a before encoding.
This means the "to be created" processor must run in 2 different modes:
1) generate a ffmpeg -i and -map string just as the example processor did. This enables one to do just rewrapping to e.g. op1a mxf or create any other custom ffmpeg command...
2) generate a .avs file in the chache directory, just as the "A/V decode" processor does. This enables to feed existing encoder nodes with the input files.
Anyway, now i need some time to check out how to detect the correct file couples from your uploaded samples
Great news emcodem! Thank you
Re: How do I input OP Atom files to create OP1A
Posted: Tue Jun 16, 2020 2:38 pm
by Julica67
I was wondering if there is an update on this topic.
Re: How do I input OP Atom files to create OP1A
Posted: Wed Jun 17, 2020 2:51 pm
by emcodem
Hey @Julica67
yeah, i was able to spend some hours on your topic. The current result is a tool that seems to be able to find the files that belong together.
Maybe you want to help me and check if it works using different input files?
https://drive.google.com/drive/folders/ ... sp=sharing
usage:
C:\path_to\aaf_list_linked.exe E:\path_to\0x060A2B3V013645E536.mxf
Output:
Full list of all files that belong together. It should not matter if you give it an audio or a video file as input, it should always be able to find all relevant files.
Re: How do I input OP Atom files to create OP1A
Posted: Thu Jun 18, 2020 2:01 pm
by emcodem
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)