Troubles to write on a NAS

[_Ilan]

Took it back to basic.

Watchfolder > A/V Media > FPS Cnverter [60] > H.264 [1920:1080] [fit and keep aspect] > Deliver [NAS]

Corrected the access on the NAS. Seems to work
I'll need to try with multiple source medias.
The source folder that is watched is filled with media coming from a website backend. I red somewhere that if it's not done manually. The watchfolder isn't working well. Is this still true?

[_Ilan]

Is there a way to detect charachters in conditions?

IF %s_original_name% contain "XXX_" [to detect an id] then >

[emcodem]

Is there a way to detect charachters in conditions?

IF %s_original_name% contain "XXX_" [to detect an id] then >

Yes, check out conditional processor. Make sure to read the documentation of the processor hitting the ? on the bottom left in the processor. E.g. you can use "=" comparison but still use wild cards like *XXX*
The processor will invoke the "error path" if the condition is not met (or end the job silently if you hit "dispel"), make sure you understand error paths, see bottom of this page.
https://ffastrans.com/wiki/doku.php?id= ... w_building

The source folder that is watched is filled with media coming from a website backend. I red somewhere that if it's not done manually. The watchfolder isn't working well. Is this still true?

No it should work in most scenarios, the number of cases where it dont work is small. Watchfolders is among the stronger parts of ffastrans actually (maybe one main reason why it exists) but some cases need special attention. Just try and see if it works in your case, make sure the "check growing" is set to "once" in the monitor folder processor..

[_Ilan]

Thanks a lot for your responses!

We wrote a script by fear to not be on time and my colleagues were not trusting the watchfolder but i'll keep working on it by personnal interest. Learning a lot right now

Is there a way to detect charachters in conditions?

IF %s_original_name% contain "XXX_" [to detect an id] then >

Yes, check out conditional processor. Make sure to read the documentation of the processor hitting the ? on the bottom left in the processor. E.g. you can use "=" comparison but still use wild cards like *XXX*
The processor will invoke the "error path" if the condition is not met (or end the job silently if you hit "dispel"), make sure you understand error paths, see bottom of this page.
https://ffastrans.com/wiki/doku.php?id= ... w_building

Yes i did some tests with conditional by sorting the output files depending on their source locations. My workflow was completely stopping if any error occured when testing the conditions, but i didn't used the execute on error option. Thank you!

[_Ilan]

FINALLY UNDERSTOOD WHAT WAS WRONG WITH THE WATCHFOLDER
(My bad, i didn't understood when reading the installation process first).

I had not created a local account with admin rights.
Now that i have one and added the credentials in the service. It's working lightning fast!

[emcodem]

Congrats on finally sorting out the issues, it will be a lot more fun when you got a working setup
Also, i second your collegues opinion about going safe and use well known methods instead of tinkering with new tools when you are short on time. After all FFAStrans can be a pretty complex tool even if first usage is made easy. The run as application feature can add a lot of confusion when you install as a service, it becomes even more confusing once you setup a farm and install ffastrans from a shared UNC location. But one gets used to the specialities pretty fast usually.

Enjoy playing with it and let us know anything you need

Btw, welcome to the Forum and thank you for using FFAStrans

[_Ilan]

Thank you!

It's surely not optimised but here is what i can call my first (humble) workflow!

XDCAM 50p.json

(12.67 KiB) Downloaded 18 times

Encoded medias are delivered depending on the "ID" that the website backend assign to the source media. Then clean the inbox.

There's a branch i'd like to add to encode only PGMs into CMAF for the VOD website but i didn't make significant progress on this yet.

Thanks again fot all the advices

[emcodem]

Hehe that type of workflow is a classic

For advanced usage, you could turn it from a 4 path workflow into 1 path workflow by extracting the 4 character portion from the filename, store it in a variable and use the variable for delivery path.

In a populate vars processor (you have to create the user variable "extracted_string" first):
%s_extracted_string% = %s_original_name%:~0,4

In the deliver processor:
\\localhost\c$\Users\ledoc\Desktop\VIDEO_OUT\%s_extracted_string%OUT_OUT

Remember 50Mbit is far too less bitrate for XDCAM style output in 50p. It will perform really bad with complex scenes. Normal 50i XDCAM is already pretty lossy and you give only half the bitrate of XDCAM which turns it basically from a mezzanine format for editing into a distribution format. At the same time you use the ancient MPEG2 codec which basically is a huge waste of space combined with bad quality.
Use Prores or H264/AVC stuff for better quality at these low bitrates.
Also, your ffmpeg command will copy the layout of the first audio track, so if you input xdcam (xdcam mxf mandatory has always mono tracks, there is no multicannel track config allowed), you will get mono output. If you input a file with stereo on track 1 and 5.1 track 2, you will get a 1 track 2ch stereo output (which also violates the xdcam mxf spec because again no multichannel audio track is allowed). So after all your video, audio and mxf container violates xdcam specs.

Dealing with the audios is one other thing that ffastrans is really good with but it can only do that when you use inbuilt encoders.