FFAStrans forum

Yes, 2016 or better. But it will likely also work on 2012....

-steinar

Hi djv6ru, Thank you for using FFAStrans and welcome to the forum! This is a bug :-( But thanks for reporting. To work around the problem (until a new release is out) you could try and put a priority change to the job right after you get the job id. That should work. There might be a small delay (2-...

Hi DCCentR,

We really appreciate your help with this issue, which is not an easy one to solve. Can I ask for you to also send some logs of jobs that was OK? That is jobs that did NOT have the stuck monitor files.

Thanks!

-steinar

So knk, it's basically the same use case as we have where we use FFAStrans to drive Whisper transcriptions. If you leave your hosts at 24 slots and set the GPU intensive node to utilize 13 slots, then you will still have 11 free slots for other operations but not enough room for two 13 slot nodes on...

Hi knk, You cannot limit a workflow like this. The closest (without adding another host for this one workflow) might be to use the feature where you tell a node (or even all nodes in your workflow) to occupy more slots in order to limit the total executed nodes per host. But it's limited occupy 16 s...

Baev12, did you try with the setting displayed in the screen shot I posted?

-steinar

Hey guys, About 2. The default AviSynth behavior of the fade filter is to add one black frame at at the start/end of the clip. And this is also how it was originally implemented in FFAStrans as well. But some would complain that the duration of the clip increased (by one or two frames) and thus the ...

Hi beav12, Emcodem is correct that there is no customizable global setting for frame rate. But FFAStrans has it's own internal parameter set to static 25 that's used when we have none. In your case you can use either what emcodem suggest or simply use the inbuilt "FPS Converter" filter: as...

Hi, sorry about the late reply...I've been on quite long vacation. I don't think there is a problem with the variable size per se but maybe the payload in total. This particular issue was fixed in the lates release 1.4.0.7. So unless you're already updated, can you please do that and report back? -s...

Hi amdx,

You have some excellent improvement points there for the stills encoder! Just use your workaround if you're happy with it, until these features are natively supported. I cannot promise it for 1.4.1 but they will definately be on the feature wish list.

-steinar