FFAStrans forum

Hi Hector and thank you for using FFAStrans! I think the best approach to your request is to make FFAStrans delete subfolder that holds the processed media. Thereby when setting your workflow to delete original file upon completion it will also delete the subfolder if it's empty. How does that sound...

Your wish is my command ;) I allready have plans for making "Command executor" global so you can use it anywhere. But this will proboably not be in FFAStrans until ver. 0.5.0 hopefylly later this year or early next year. 1. Deleting originals is allready possible. Look at you workflow prop...

Hi bsti. I have seen this happening from time to time, and this is one of the reasons 0.4.0 is still beta. I'm still investigating the issue and until I've found the root cause try this: 1. Make shure there is no real encoding going on. 2. Delete all files here: ...\FFAStrans\Processors\.cache\monit...

Ah, I see. That should not be a problem at all I'll look at it for the next release. Thanks for clarifying!

-steipal

It,s allready in there. Use the %source_path% variable. It was added in the 0.4.0beta2 release and documented in the "V" variable button.

-steipal

Hi Oren and thank you for using FFAStrans! The "Custom FFmpeg" would accept "-preset medium -tune film -profile:v baseline -level 3.0 -g 25 -keyint_min 50 -refs 6 -pix_fmt yuv420p -x264opts bitrate=800:vbv-maxrate=800:vbv-bufsize=1600:keyint=50:min-keyint=50:no-scenecut -vf scale=-1:4...

Even though the bug was fixed, ffms2 AviSynth plugin (which does the analyzing when using "A/V Decoder") will still have problems these kind of files coming from Handbrake. I don't know if it's a ffms2 problem or a Handbrake problem but if it's a ffms2 problem, I'm afraid it's also a FFASt...

Thanks for your suggestion Mono! It makes sense and I will look at it in the near future. Regarding your second problem; FFAStrans will check if the file is being locked by another process. However, there are some programs creating files which can be opened while it's being written. MXF files typica...

From what you are describing it seems you are running two independent instances using two sets of same configuration. Put your FFAStrans program folder on f.ex. something like \\FreeNAS\FFAStrans or v:\FFAStrans or what ever kind of share you like and run the .exe on both computers from the same sha...

It's not a bug, it's a feature ;-) If you look at the documentation for the "Custom FFmpeg"-encoder you will see that you should always add the "Channel Mapper"-filter if you are using the "A/V Media"-decoder. The reason for this is that when you create a custom ffmpeg ...