Beta 10 - update batch renderer

I have updated FFEasyRender (my batch renderer for FF).
It now supports FilterForge till version 10 beta.

Free to use, but I 'll accept donations (hint, see "PayPal button" on my website).

You can download it from my website:

https://www.ipadtouches.com/ffeasyrend...ter-forge/

found the password but still need to know if this is for mac or pc.

Hello FFCreator.

Super thanks for developing your BatchRenderer. I'm trying it out now. Though, after entering all the pertinent information in the appropriate fields, then hit the Render button, I obtain a "Filterforge command line renderer not found!" message. Is there something I've missed somewhere? Many thanks again for your kind work and endeavors!
Pierre D.

Hello FFCreator.

Thanks for your kind reply.

As I did unzip the contents of FFEasyRender into a new folder and have legit versions of FF installed (e.g. version 9 and 10 beta), those versions of the software are installed on my D: dirve (for disk space issues I installed FF on another drive volume). Hence, that does explain why I'm receiving the message about the cmd line renderer not being found. I haven't had the chance yet to test the FF cmd line batch renderer (haven't tried that feature yet). So, I'll keep you posted with that test. In the meantime, is there a way around the issue if FF is installed on a different drive other than C:? Also, I'm trying to understand why the library file are stored in my C: Users path, although the FF SW is installed on D:? Anyway...

Many thanks again for your help!
Pierre D.

Greetings FFCreator.

It worked after I uninstalled version 9 and reinstalled v-9 in the default C: installation path. So, for users who install FF in non-C: drive paths, I guess that could be somewhat problematic to a certain degree. I'd also like to mention that I work with incrementally named image files, since I render out sequences from a 3d SW I use, and the files (obviously) are appended with the Preset info, thus resulting with no frame number suffix. Generally, I could have over 400 frames (image files), and renaming them is another issue. Would you entertain adding a file extension option that can increment image files in the case that one is dealing with large image sequences? Just a thought. But, your tool worked very well indeed, and I will make a donation for sure.

Again, many thanks!!!
Pierre D.

Hello FFCreator.

You've got it. Yes, just the ability to be able to keep an image sequence, such as image.1.jpg, image.2.jpg, etc. I used a basic batch file renaming app in the beginning of my render tests, to remove the extra file info in the filenames. But, I discovered that if I unchecked the 'Add filter filename' and 'Add preset Number' options, my rendered files retained their number sequence. So, that works out! Also, yes, my Windows 10 OS is installed on my C: drive and Breta 10 on my D: drive. To get things working for my evaluation, I uninstalled FF version 9 from my D: drive and re-installed FF v-9 on C:. The process works pretty fast and pretty error free. I think that if you are able to add features for saving render jobs (e.g. Open and save render files) and having the ability to select a filter that goes beyond number 20 (unless I'm not aware of how to make that happen?), you'd have a pretty powerful tool!

Again, many thanks for your valuable rendering tool and replies.
Pierre D.

Thanks FFCreator. I'll d/l your beta version and give it a test drive.
Much appreciated. PD

Hello PierreD.

FFEasyRender can't render directly custom presets from Library Filters for technical reasons:
1 The commandline renderer of Filter Forge doesn't render these custom presets of Library Filters either.
2 Custom presets of Library Filters are stored by Filter Forge in seperate files that can have different number of parameters in comparation of the "standard" presets from the same Library filter (probably caused by different versions of Filter Forge; Filter is released for FF version "X" and the custom presets of the Library Filter are written by FF version "Y").

I remember another post that this is more or less 'by design' of FF.

However there is an easy workaround.

1) Sel ect the Libary Filter with the custom preset you want to render.
2) Open the filter editor.
3) Save the filter as an User Filter.
4) Render the preset(s) fr om the User Filter you want.

Grateful to both of you FFCreator and SpaceRay for your kind help. I will give the workaround a go. Un gros merci!
Pierre D.

Works great. Many thanks again gentlemen! Pierre.

Oops. I made a mistake. There's no need for step no.6, unless one wants to submit their Preset to the FF lib.What I forgot to add, was that step no.3 should include this:

... From the 'Result' node, click on the 'Filter Controls option, then edit the parameters as needed, from the properties editor located at the bottom left-hand side of the Filter editor. Then proceed with the 'Save Filter as' step.

Sorry for the mix up.
P.