FFAStrans forum

Thanks for the help on this @encodem I was able to simplify things a bit with just one powershell script to convert the time from seconds to HH:MM:SS: powershell -ExecutionPolicy Bypass -Command "New-TimeSpan -Start (Get-Item '%s_job_work%').CreationTime -End (Get-Date) | ForEach-Object { '{0:D...

Let me know if this is already in the list of variables and I just overlooked it, but I want to add to an email that is sent out at the end of workflow, the amount of time it took to process the file from when the file was picked up in the watch folder till the file was sent to the destination folde...

@failsafe5000 The log viewing is done by direct file access instead of using the ffastrans API. If your ffastrans files are on a NAS, you'd need to give the webinterface service credentials that can access that NAS as well. For debugging, you can stop the webint service and start server.exe by just...

Hi, Having an issue with a new farm setup and accessing job details through the webinterface. Running latest versions of both, farm setup is working as expected, with 4 computers sharing the work, while one computer hosts the FFAStrans program and is the one running the Webinterface. Webinterface sh...

Hey @emcodem

I'll definitely use that, for the instance name. As for exposing it to the internet, I would have loved to have done that, but my workplace is really strict on opening ports and devices to the outside, requiring a bunch of paperwork and such. So the website setup was the easier option.

So a little background, I'm an IT Engineer for a local news station. The reporters have been complaining that editing and sending videos to air from their laptops both at the station and out in the field is quite a hassle, and requires multiple people to get them on air. So I started working on a wa...

emcodem wrote: ↑Sat Nov 09, 2019 9:37 am hehe i see
By the way, instead of rebuilding the whole workflow, it might help to just delete and recreate the watchfolder component, there were multiple issues reported in this direction...

So I created a new workflow and just copied over the nodes, and now logs are working as expected.

It's a bit more of a simple setup then that, as the transcode server is hosting the webinterface server. I'm just using the raspberry pi as a simple web browser to view the site.

I gave that a try as well, and it gave me two error messages saying the workflow isn't logging enabled. What I'll try next, when I get back into work next week, is to just create a new workflow, copy over the nodes, and use that one and see if that fixes it. The current one may have been duplicated ...

I don't have a 20191010184107.ini in the workflows folder, but attached is the workflow that is having the issue, and is the one currently in use