FFAStrans forum

This fixes the issue for me.

Thanks to you and steinar!

Now my testing for my custom plugin processor is complete and works.

If I removed the custom plugin processor and put in a populate variables processor and manually set the %s_source% simulating what the custom processor is doing the workflow works. The one thing I noticed is the ticket that is received in the original workflow's custom ffmpeg and cmd processors has ...

I understand that. I use native functions a lot as well.
I have entire library of native functions that I use PInvoking with. i.e. FileCopyEx because there is no managed version of copy/move with progress.

When s_source is set by a processor prior to a Custom FFmpeg processor, I would expect that the Custom FFmpeg processor would update the s_source after it is done transcoding. Am I wrong in thinking this? The first processor following the Custom FFmpeg processor in my workflow still shows the s_sour...

Thanks for that. The cancellation should have been completed within that time frame. I found the source of my problem. I handle catching the ctrl-c a little different then in the C# plugin example. Instead of PInvoking the native SetConsoleCtrlHandler() function I add a handler to the managed Consol...

Are you going to add FTP location capability in the next version?

How much time does FFAStrans give a processor to process the CTRL-C sent to it for aborting a job. I want to handle the event to do a proper cancel and cleanup. I have implemented the functionality in my code to handle this, but am getting force killed before I can finish. It this a configurable ite...

I figured out my problem. For the built-in outputs the structure in the outputs array is different. This is not very clear in the Wiki. The custom outputs structure is shown and that is what originally used. It took me digging into the force_error source to see how it was setting up the built-in out...

I am setting the "s_source" outputs data entry to the downloaded file location, but the next processor (for testing a delivery processor to copy to another folder) is not using this value for the source file location. It still uses the original ftp URI source. Below is the proc_data sectio...

Thanks for the feedback. I will use your suggested method on handling the null proc_data. 1. I am not trying to create a monitor plugin. I am trying to write a plugin that will process api or webinterface submitted properly formatted FTP URI's and have FFASTrans download the file to the working dire...