FFAStrans forum

@emcodem

Well that is certainly understandable. At this point my encoding farm is basically dedicated to FFAStrans anyway so I might as well upgrade to Windows server 2012 R2 or possibly even Windows 10, I'll probably be heading that route with this.

Thanks for the help on the UNC path as well.

Hello, Trying the latest version of the Webinterface 1.2.0.2. This is on a Windows 2008 R2 box for my farm environment. Trying to run server.exe Node.js is only supported on Windows 8.1 or Windows server 2012 r2 or higher and it says I could try setting NODE_SKIP_PLATFORM_CHECK to 1 to skip the chec...

Hi Steinar,

Yes, the issue started right after creating the new workflow. I went ahead and zipped the db folder and sent it to you before I reinstalled ffastrans.

Thanks!

Perhaps this is related, I recently upgraded to 1.1.0.2 and everything was working great. Workflows got upgraded, made a few new ones, but then just now made a new workflow and started getting this AutoIt v3 error and a whole bunch of FFAStrans processor manager has stopped working messages appear a...

Wow you really rocked it, thanks! The output is looking really good, best I've seen for PAL to NTSC framerates with free software. You've also opened the door for me to use more Avisynth in FFAStrans instead of just FFMPEG as I can expand on its use with this workflow as a starting point. Really app...

@FranceBB I'm going to be playing around with this today and I'll give what you suggested a try for sure, thanks! My main confusion on the Custom Avisynth script processor is how to properly use the m_clip variable as opposed to the usual avisynth sort of source assignment. It should be a fairly sim...

Well just to follow up it turns out that my main problem with doing it the way that I was originally, was that I was setting FPS Convert to 29.97 instead of 59.94 and when the output is interlaced, it does need to be set to 59.94 for the fields. That and the fact that my ffmpeg script was wrong in t...

@emcodem Your right, leaving that ffmpeg encoder at 23.976p was a mistake, its supposed to be a 30000/1001 interlaced DNxHD145. I am currently getting the error with 25i media inputs. @FranceBB You're right! I messed up on the ffmpeg part of the workflow for this example as well but it looks like yo...

Attached is a workflow (simple decode to convert fps to ffmpeg encode) I was using with good success back in v1.0.0.0 to convert 50i to 59.94i and 25p to 29.97p using Avisynth Convert FPS with the blend option. I noticed recently however that this no longer works in v1.0.0.5 and I just get an error ...

Steinar, I tested your patch and it works perfectly! I don't get the first error anymore and it looks like the second error was more or less an extension of the first error as it would only ever happen after the first. Thank-you so much! I am reducing my workflow down quite a bit now, but we now kno...