FFAStrans forum

Hi abul,

You can simply use wildcards like this:

Contains: If %s_original_name% = *_P2High*
Ends with: If %s_original_name% = *_P2High
Starts with: If %s_original_name% = _P2High*

Hope this helps.

-steinar

Pay attention to quotes and paths:

%comspec% c/ ""%s_ffmpeg%" -i "D:\Abul\Documents\Projects\Trans-Wrapping\merge\%s_audio_filename1%.wav" -i "D:\Abul\Documents\Projects\Trans-Wrapping\merge\%s_audio_filename2%.wav" -c copy -map 0:0 -map 1:0 "<what path???>\%original_name%.mxf""

-steinar

Hi Mahmoud Rady, thank you for using FFAStrans and welcome to the forum!

Can you be a bit more specific? In what way is it not accurate?

-steinar

Hi abul,

The Workflow editor has several flaws. This issue and hopefully most (or all?) other editor issues has been properly addressed in the next version of FFAStrans.

-steinar

Hi Andre,

Sorry for not replying earlier but the bug has already been located and it will be fixed.

-steinar

Ok, so it's not the option to create 29.97i but rather that timecode should be written in DF? If so, well that's a good point. You can insert a custom tc with DF notation in the tc input field but FFAStrans does not insert this automatically. But this I will take a look at for the next release. Than...

Hi André, thank you for using FFAStrans and welcome to the forum!

The &quot: is an internal FFAStrans thing when dealing with variables and should not exposed, so this is a bug. Could you please export and send your workflow so I can take a look?

Thanks for reporting!

-steinar

$regext($read("%s_original_full%"),"(.+)") should actually be $regext("$read("%s_original_full%")","(.+)") in case the $read() returns a comma ',' character. @emcodem, single quotes will also work: $regext('$read('%s_original_full%')','(.+)') So the rule inside a function is: Everything that is or ...

Hi philthewiz,

Can you be a bit more specific? Ar you lacking TC track on output files from XDCAM-HD50, or are you referring too XDCAM IMX-50?

-steinar

Hello guys, sorry for late response. The xxhash implementation was supposed to be consistant between os architectures but obviously there's a bug here. Also, I found that the x86 hash output version would not be read correctly. So, the xxhash did probably NOT work on 32bit OS and gave as you pointed...