FFAStrans forum

Your little tool is fantastic! It would be great if you can add a function to clear the history of the already encoded files. Right now I'm having the problem that when I want to encode a file that has the same name as a previous encoded file, the encoding process is not starting. When I rename the file, it starts. Also a function to pause and/or cancel a running encoding process would be great.

Hi bsti and thank you for using FFAStrans!

You can clear history from the "Folder" monitor processor. Press the "Clear cache" button and you're of. FFAStrans should not be fooled by just the name. Your new file must also have the exact same size and modify date as the previous for FFAStrans to not pick it up. However, if your new file DIFFERS in size, modify date and name, and FFAStrans STILL does not pick it up it must be a bug and I would like to know about it. However, I have never experienced that problem.

Regarding your second request, cancelling jobs will be available in the next release (0.4.0beta). Pausing will still not be possible but it's already on my own future wish list. However, it's not top priority.

-steipal

It was the same file that I tried to encode. I made some changes in the encoder settings of a workflow and wanted to test the new settings with the same file.

Well in that case you could just submit your file from your workflow window. You can submit the same file as many times as you want. FFAStrans won't store it in the history. Anyway, I will change the wording regarding monitors history in upcoming version. "Clear cache" and "Rebuild cache" are a bit misleading. "Clear history" and "Rebuild history" is much better

-steipal

Hello.
Have the same issue. Although I have checkboxes "Delete original" and "Delete from cache" marked new file with the same name is not processed.
I see in the ".\cache\wfs\20141011084344\mons\20141011084422\" folder that txt file are not deleted. If I remove them manualy, file with same name is transcoded.

Nice tool btw

Hi ASI and bsti!

I see now that it's actually a bug

Thanks for notifying! It will off course be fixed in the next release due in a couple of days.

-steipal