FFAStrans forum

Hey James,

welcome to the Forum and thank you for using FFAStrans!

Personally i prefer a cmd executor over custom ffmpeg processor because it limits me far too much and it is kind of hard to debug but i tried it out and didnt find any issue using your parameters:

Oh it just came to my mind that if you change the http processor against the cmd, there is no easy way to let the next job know the current retry number so after all it might be a good idea to keep it as it is :D But as usual, do whatever works for you! Anyway, looking at the log, we see this: Exiti...

The good thing about franks workflow is that it's easy and clean, also it is more compatible to the different "monitors" processors, e.g. P2, image sequence and such. The bad thing is that it only works with watchfolder submission and there is no retry count so it would potentially retry forever. On...

Hey michael, i cannot tell whats wrong looking at this log, i'd need the "full_log.json" file for it. Regarding retry, i use this for live recording, here is how it works: emcodem_retry_with_count.json The 2 processors on the top are some example workflow, encode and deliver. both can fail, so both ...

I think for this usecase, i would go for the /tickets call instead of the jobs one. http://FFASTRANS_HOST:65445/api/json/v2/tickets The difference simple explained is that jobs only shows stuff that has already been picked up by some processor and tickets shows both, stuff that should be picked up b...

@Ferdinand2021 (just to send you the notification)
Here also some additional related post about XDCAMHD related and standard conformance:
viewtopic.php?f=5&t=1288&p=7214&hilit=mainconcept#p7218

Hey @dkoos i have seen such a case before when mediainfo "successfully" delivers "empty" output but i don't recall at the moment what case that was. Might this only be about the mov file type is not supported by this mediainfo version or such? Actually the output is not blank but it misses any data ...

OK sorry today was a little bit too messed up to test out if everything really works as it should. First, there was a change in "when" history jobs are being cleaned up recently, so there is a good potential for errors as with every change. Seconds, some history on "history" jobs: 1) initially, dele...

Neverthless it would be a good feature to have an output connector of the sub-workflow processor. But looking at the current implementation of sub-wf, we'd need more something like "start a sub-wf via API and wait for the result", which can be done already today using the HTTP communicate+ plugin pr...

Anyone who has time and muse, please check out the upcoming release and tell me all bugs you find
https://github.com/emcodem/ffastrans_we ... ag/1.3.0.1