Hi, I just fighting to save anyhow my workflow in 8.1.0.
I've already tried everything. My last success was on the v7.x.x FFAStrans.
When I like to start the conversion, a message pops up:
"Please save your workflow before starting it". I just trying and trying to save, but the result is just some weird .ini file and an .xml filled with completely unrecognizable (hexa?) codes inside. When I try to save, the screen freezes for 10-20 sec, then makes the .ini and the .xml, but the program believes: nothing is saved. So blocking me to start the conversion.
The v7.x.x had a "human-readable" config file to allow manual editing. Now it is disappeared in the 8.x.x.
Also remained the problem with the false positive virus alert.
My system is a carefully updated, fine-tuned, rock-stable Win 7 x64 on a brand hardware.
I was so happy as found the FFAStrans, as experienced lot of problems with the Sorenson Squeeze for years.
Is there any download link to get the older (7.x.x) builds?
I think something went on wrong with the new xml/ini direction, abandoning the good old, human-readable one. Is that difficult to save a simple config?(!).
As I read the comments, some important bugs just resolved in the 8.1.0, but the above major problem stayed with us.
Is there any workaround or hack to resolve it?
Thank you and have a nice day. In other hand this is a very nice project and a good tool (if working well) for any video people.
DeV32
Impossible to export workflow - even with the 8.1.0.
Re: Impossible to export workflow - even with the 8.1.0.
Hi DeV32, thank you for using FFAStrans and welcome to the forum! 
I'm a bit confused about your bug report because you're writing about exporting, saving and starting as interconnected problems. So just let me clarify how it's supposed to work.
Exporting workflows creates .xml files, not .ini files. This can be done wether the workflow is saved or not. You are correct about the .xml file containing hex data but the file is not meant to be read or manipulated by users. It was introduced in FFAStrans 0.7.6 and it only meant to be a transfer mechanism from one environment to another.
Saving workflows creates one .ini config file, not .xml. This .ini file is mostly easy to read and has never changed significally.
In order to start a workflow you MUST save your workflow IF it has been modified.
Now, I have no problems with any of the issues you're describing, apart from AV-issues covered later. I've tested on 3 different configurations (Win7, Win8, Win10). All seem to work as expected. There might of course be a problem with your workflow, that it's corrupt or something but that's just a guess. I'd rather you clarify the issues before reverting to an older version. So If you can try to be precise because it's not clear if you have problems exporting, saving or starting workflows. Or maybe all of them? I'm not saying it's NOT a bug but if I cannot recreate the issues they can't be fixed.
Regarding the false positives virus alerts that's a continous battle and it has nothing to do with FFAStrans per se, as it's not a virus. It's the way the AVs are designed and "unkown", not widespread programs are more prone to be attacked than widespread well known ones.
-steinar
I'm a bit confused about your bug report because you're writing about exporting, saving and starting as interconnected problems. So just let me clarify how it's supposed to work.
Exporting workflows creates .xml files, not .ini files. This can be done wether the workflow is saved or not. You are correct about the .xml file containing hex data but the file is not meant to be read or manipulated by users. It was introduced in FFAStrans 0.7.6 and it only meant to be a transfer mechanism from one environment to another.
Saving workflows creates one .ini config file, not .xml. This .ini file is mostly easy to read and has never changed significally.
In order to start a workflow you MUST save your workflow IF it has been modified.
Now, I have no problems with any of the issues you're describing, apart from AV-issues covered later. I've tested on 3 different configurations (Win7, Win8, Win10). All seem to work as expected. There might of course be a problem with your workflow, that it's corrupt or something but that's just a guess. I'd rather you clarify the issues before reverting to an older version. So If you can try to be precise because it's not clear if you have problems exporting, saving or starting workflows. Or maybe all of them? I'm not saying it's NOT a bug but if I cannot recreate the issues they can't be fixed.
Regarding the false positives virus alerts that's a continous battle and it has nothing to do with FFAStrans per se, as it's not a virus. It's the way the AVs are designed and "unkown", not widespread programs are more prone to be attacked than widespread well known ones.
-steinar
Re: Impossible to export workflow - even with the 8.1.0.
Dear Steinar, thank you for your quick response.
As I just revised carefully the whole software again, I could not find any "Save" option, menu or button. The only way to store any personal on my HDD is the "Export workflow(s)" menu item under the "File" upper root menu.
As you wrote, I must Save my workflow if modified. That is OK. But how? Because no any "Save" option exist. Just "Export workflow(s)". Do you mean this?
Is there any "Save" menu item somewhere? Or this function just done automatically?
Other strange thing: When I closing my instance of FFAStrans (which contained a complex, hand wired config of various deliverers, codec etc) and reopening again by clicking on the FFAStrans.exe, the boxes shown up on the top of each other, but all "hand-wired" between them just disappears.
The freezing frame-problem also remain: when I click on the "Export workflow(s)", the FFAStrains's own window freeze, like the Windows overlay control layer loses its control for a 10-20 seconds. While this machine has all driver updated, i7 CPU, 16GB brand RAM, without any overclocking, never freezes by months.
So now I cannot do:
- save or export any hand-drawn config of me, to reuse it tomorrow
- I cannot start the workflow as receiving the notice: ""Please save your workflow before starting it"
Now I have an xml file, with the name of my workflow and a .ini file with some parameters (like FTP settings) of my hand-drawn plan blocks, but I never saved it, it just appeared in the "Workflows" subfolder. It is some "automatically-born" .ini file with the date in the name. When I reopen the program, all my wiring disappears.
I have to use this encoder PC over Teamviewer always. Can it cause any interference with FFAStrans?
My virus scanner is AVAST. I know exactly, this software is not a virus at all, the false alert is just an idiot-ism by the AV itself.
Can the AV disturb the program running? I already disabled it to see, but no difference.
Kind regards,
DeV32
As I just revised carefully the whole software again, I could not find any "Save" option, menu or button. The only way to store any personal on my HDD is the "Export workflow(s)" menu item under the "File" upper root menu.
As you wrote, I must Save my workflow if modified. That is OK. But how? Because no any "Save" option exist. Just "Export workflow(s)". Do you mean this?
Is there any "Save" menu item somewhere? Or this function just done automatically?
Other strange thing: When I closing my instance of FFAStrans (which contained a complex, hand wired config of various deliverers, codec etc) and reopening again by clicking on the FFAStrans.exe, the boxes shown up on the top of each other, but all "hand-wired" between them just disappears.
The freezing frame-problem also remain: when I click on the "Export workflow(s)", the FFAStrains's own window freeze, like the Windows overlay control layer loses its control for a 10-20 seconds. While this machine has all driver updated, i7 CPU, 16GB brand RAM, without any overclocking, never freezes by months.
So now I cannot do:
- save or export any hand-drawn config of me, to reuse it tomorrow
- I cannot start the workflow as receiving the notice: ""Please save your workflow before starting it"
Now I have an xml file, with the name of my workflow and a .ini file with some parameters (like FTP settings) of my hand-drawn plan blocks, but I never saved it, it just appeared in the "Workflows" subfolder. It is some "automatically-born" .ini file with the date in the name. When I reopen the program, all my wiring disappears.
I have to use this encoder PC over Teamviewer always. Can it cause any interference with FFAStrans?
My virus scanner is AVAST. I know exactly, this software is not a virus at all, the false alert is just an idiot-ism by the AV itself.
Can the AV disturb the program running? I already disabled it to see, but no difference.
Kind regards,
DeV32
Re: Impossible to export workflow - even with the 8.1.0.
Oh 
Well now I see why have such problems!
Saving workflows are CTRL+S or rightclick in the workflow editor and select save. It's also described in the help section of FFAStrans.
The way you have been using FFAStrans must have been real cumbersome... and still you did'nt toss it out the window
-steinar
Well now I see why have such problems!Saving workflows are CTRL+S or rightclick in the workflow editor and select save. It's also described in the help section of FFAStrans.
The way you have been using FFAStrans must have been real cumbersome... and still you did'nt toss it out the window
-steinar
Re: Impossible to export workflow - even with the 8.1.0.
Dear Steinar, yes, I just forgot to use the right click on the editing area. It is a rookie act by me ...)
Now I am going to test the watch folder function.
Greetings,
DeV32
)Now I am going to test the watch folder function.
Greetings,
DeV32