www.filterforge.com - Bugs and Problems (Windows)

Built In Preview Missing Error

CFandM — Wed, 08 Apr 2026 04:48:55 -0400

CFandM, Thu, 26 Mar 2026 23:11:47 -0400
Working on a filter today and using the built in images to test that filter. All the images work except for the transparent paddle boarding image. This one throws up an error dialog. It is not a crashing bug just a simple click and continue with what one was doing....I am working with the latest version of FF15...

GMM, Wed, 08 Apr 2026 04:48:55 -0400
CFandM, thanks for your report, the issue will be fixed in the next program update.

Random Crashes using FF14

PixelStar — Mon, 29 Dec 2025 21:43:56 -0500

PixelStar, Tue, 16 Dec 2025 10:11:31 -0500
Has anyone else been experiencing crashes on Windows 11 using FF 14?

I am running FF 14 Studio Pro on Windows 11 Pro (Version 24H2) I have used Group policy to keep my windows updates to 24H2 for now and stop it from updating to 25.

That said, I use FF sometimes in conjuction with photoshop, but usually I am working in the stand alone app. I experience fairly frequent random crashes. I decided to report this, because usually the crashes happen whenever I am creating a new filter, but yesterday, I was testing the new filter I created (not in the filter editor) and it crashed to the desktop! It is a fairly simple filter, that is, just several groupings of patterns that I creating using profile gradients, offset and a few curves. I have seen way more complex filters than this.

To mitigate some of these crashes, I save frequently and have backed up my filters to several other folders I created underneath the "my filters" folders. I just wondered if others have experienced crashing on Windows 11. Currently I am going to look into what processes I have running and clean those up. Windows 11 is very process and telemetry heavy.

PixelStar, Sun, 28 Dec 2025 16:24:12 -0500
I posting this in hopes it helps others who are experiencing similar issues running Windows 11

There has not been much response, or instruction on how to resolve these issues; I submitted a ticket for this quite some time ago. I have asked AI to look into the specifics of these current crash reports, one of which I did submit to you all recently.

Potential Fixes and Workarounds suggested by AI (some of which I applied)

1. Upd ate Filter Forge to Version 15. But I question FF developers as to whether or not they have addressed these issues with Windows 11 in Version 15
2. Update Graphics Drivers -->I did update my Nvidea RTX 4070 laptop driver
3. Adjust Display Settings: -->I se t my display to 100% - recommended settings
*Try setting your display scaling to 100% or 200% (Settings > System > Display). Some crashes tie to fractional scaling (e.g., 125% or 150%) messing with UI repaints. If using multiple monitors, test on a single screen or match DPI settings across them.
4. Editor Workarounds: -->I began using the in app zoom to fit and this has reduced the amount of crashes
*Keep your filter layouts compact—avoid spreading components too far, as this triggers navigation crashes.
*Use the "Zoom to Fit" button instead of manual zooming/scrolling.
*Save frequently (Ctrl+S) and work in smaller groups/snippets to minimize loss.
*If possible, test simpler filters first to isolate if complexity is a factor.
5. Other Troubleshooting: -->closed and disabled some processes
*Close background apps/processes before launching Filter Forge, especially anything telemetry-heavy (more on that below).
*Run a system file check: Open Command Prompt as admin, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth.
*If crashes persist, generate a new error report and send it to their support again, referencing your past reports and this exact stack trace. Mention the OS misdetection—it might prompt them to investigate Win11 24H2 compatibility.

Other information that AI included with workaround steps:
"Windows 11's telemetry can be aggressive, spiking CPU/RAM and potentially interfering with resource-intensive apps like Filter Forge"

**Check Task Manager
**Change advanced power settings, and disable wake timers or fast startup -->(I did go through some processes for my unique setup and apps running with AI and se t some parameters in Group Policy for unnecessary processes and apps to cut back on resources)

And finally a detailed answer by AI regarding my specific initial crash report which led me to complete steps above:

It looks like you're dealing with a frustrating, recurring crash in Filter Forge 14's filter editor, specifically tied to UI rendering (the WM_PAINT message handles painting/redrawing the window, and exceptions there often point to graphics or compatibility glitches during actions like scrolling, zooming, or moving components). The "kernel" references in the stack trace (e.g., KERNELBASE.dll) are indeed part of Windows' core system components, but they don't necessarily mean an OS-level failure—more often, they're catching unhandled errors from the app itself, like access violations during drawing operations.Your system's specs (i9-13900HX, 65GB RAM, 32 cores) are plenty beefy for Filter Forge, so hardware overload seems unlikely unless there's a GPU bottleneck or driver conflict. Note that the error log misidentifies your OS as Windows 10 (build 26100 is actually Windows 11 24H2), which could hint at a compatibility detection issue in the app.From digging into similar reports on Filter Forge's forums and elsewhere, this type of crash (XFW::Exception during WM_PAINT in the filter editor) has been reported across versions 5 through 14, often during navigation in complex filters. It's not isolated to you—users on Windows 11 (including 24H2) describe the same symptoms: random terminations when spreading out modules, scrolling, or zooming. Developers have acknowledged it in some threads but haven't released a targeted fix; they sometimes request filter files to reproduce it, but resolutions are spotty.

------------
Today, after having some success with these suggestions, I received another crash.
I sent it to the AI and its response was as follows:

This new crash is different: it's triggered by mouse interactions (WM_LBUTTONUP = left mouse button release, likely after clicking/dragging a component, connection, or button), and the core error is ::CreateFontW(Segoe UI, 14, 0) failed. That's a Windows GDI call to create a font object for UI text (Segoe UI at 14pt is common for labels/tooltips in the editor).
Failures here usually mean a low-level graphics/resource issue, like:
*Temporary exhaustion of GDI handles (rare on your beefy system, but possible if many apps open or a leak).
*Corrupted font cache.
*Graphics driver glitch when allocating font resources during UI updates.
*Compatibility quirk on Windows 11 24H2 (the app still misdetects it as Win10).
It's not as common as the paint-related crashes, but similar editor instability has been reported.

Potential Fixes and Workarounds suggested by AI (for second crash report) :

1. Rebuild Font Cache (since it's a font creation failure):
*Close Filter Forge.
*Open Services (services.msc), stop "Windows Font Cache Service" if running.
*Delete the font cache files: Navigate to C:\Windows\System32\FNTCACHE.DAT (delete it—admin rights needed) and/or C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache (delete contents).
*Reboot—Windows will rebuild the cache.
*Test Filter Forge.
2. Graphics Driver Refresh:
*Download and run Intel's Driver & Support Assistant (intel.com) for your i9-13900HX integrated graphics.
*If you have a discrete NVIDIA/AMD GPU, update that too.
*After update, reboot and test.
3. GDI Handle Check (unlikely issue, but easy to rule out):
*In Task Manager > Details > Look for high GDI Objects on Filter Forge process (normal is <500; if spiking to 10,000+, that's a leak—but doubtful here).
4. Continue Safe Habits:
*Keep scaling at 100% for now (or test the high-DPI override I mentioned before).
*Avoid rapid clicking/dragging if possible—use keyboard shortcuts more (e.g., Ctrl+C/V for copy-paste components, arrow keys for nudge).
*Save often!

One theme that keeps coming up within these crash reports are that the app seems to be pointing to "Windows 10" when, clearly, I am running Windows 11 Pro version 24H2. AI Response: "Note that the error log misidentifies your OS as Windows 10 (build 26100 is actually Windows 11 24H2), which could hint at a compatibility detection issue in the app."

And again, for the second crash report, it suggested upgraded to Filter Forge 15, however, please address whether or not the developers have upgraded Filter Forge 15 to be compatible with Windows 11. I just upgraded to Filter Forge 14 in Spring of 2025. I don't want to upgrade until I can see these compatibility issues are addressed. In the meantime I am going to try using FF 14 in Windows 10 compatibility mode.

STEPH08, Mon, 29 Dec 2025 08:45:10 -0500
No crashes, FF14 and FF15 work perfectly on my laptop with Win11.
Probably a Windows update on your laptop messed up your system. I've read tons of complaints about most Windows updates in 2025. Personally, I block all Windows updates with my firewall and disable all Microsoft spywares, so I'm still on version 22H something, but I've never had BSODs or software issues.

PixelStar, Mon, 29 Dec 2025 21:43:56 -0500
Thanks for the reply; this is good to know. I have had similar feedback from folks I assisted with upgrading to Windows 11 back in October whenever MS had decided they were ending their support for Windows 10. Issues like system thrashing etc. I had never really had this issue before back on windows 10.. yes the occasional crash but not like now. I have mine set to 24h2 and blocked for further upgrades.. that means sometime between 22 and 24 there has been some issues. I have tried disabling Microsoft "spywares" such as copilot, Phone Link & cross-device experiences, such as "resume", and out of box experience. After disabling and turning off, Windows 11 turned the "resume" (which is the cross device syncing) back on, even after blocking them via group policy and the registry. I have read that many times updates overwrites the changes. So frustrating :evil:

Is "snap to grid" actually working?

Raschid Abdul-Nour — Fri, 26 Dec 2025 16:42:51 -0500

Raschid Abdul-Nour, Fri, 26 Dec 2025 16:42:51 -0500
Hi!
Edit: Ok, jeez, consider this as BS. Sorry for spamming the forum with that, not sure what I have seen, but it seems to work..
I'm not having a good run with my two last post these days :( Feel free to delet this post if possible..

OP: Is snapping to grid in the editor working for anyone? I notice no difference when I have it activated. Either it is not working on my system, or the snapping increments are that small, that I don't recognize it. Third option of course would be I'm using it wrong, but I'm not sure what could go wrong, I can either activate the feature or deactivate it...

Unable to save projects

alfie — Tue, 04 Nov 2025 07:53:03 -0500

alfie, Mon, 03 Nov 2025 05:53:55 -0500
Hi

I'm using professional 14 (permanent license) and every time I try to save my images all I get is the following pop up

The professional version you are using doesn't let you save projects you create or edit. Please upgrade to studio

Surely that can't be right :?:

GMM, Tue, 04 Nov 2025 07:53:03 -0500
alfie, welcome to the forums!

Quote
alfie wrote: I try to save my images

Quote
alfie wrote: doesn't let you save projects

You need to save images but choose to save projects instead. Projects are not images, this is a feature to help you transfer your artwork to a different computer.

To save your rendered image, click "Save Image As".

Filter Forge 14 will not load into Adobe Photoshop version 26.2.0

DeGarthy — Fri, 24 Oct 2025 10:19:02 -0400

DeGarthy, Wed, 22 Jan 2025 21:13:20 -0500
I downloaded the appropriate file (I have a lifetime license). Executed the install package and it was successful. On launching Photoshop, Filter Forge was not listed in the plugins. Is there a problem. It installs successfully in previous versions of Photoshop. Is there a fix?

CFandM, Wed, 22 Jan 2025 21:34:23 -0500
A lot of posts about different versions of FF and PS but they work and are fixed the same. Adjust for your version of FF and PS. FF and PS manual install

DeGarthy, Wed, 22 Jan 2025 22:26:46 -0500
Thanks much. It worked. :)

CFandM, Thu, 23 Jan 2025 13:40:47 -0500
Glad you got it working. smile:)

RobH, Thu, 23 Oct 2025 19:58:18 -0400
Worked for PS 26.10.0.

Thank you...

CFandM, Fri, 24 Oct 2025 10:19:02 -0400
Cool.. :) Happy that it worked for you. :)

FF7 unable to update or download Filters

xxstyxx — Wed, 22 Oct 2025 05:45:45 -0400

xxstyxx, Mon, 20 Oct 2025 09:06:06 -0400
So, i did not used Filterforge 7 for a few Years.
Now its unable to connect to the Servers.
Its NOT a Firewall Problem, i disabled it completely to test it. It just says "unable to connect to server" i i try to update FF or the Filters and gives me the same Error if i try to download new Filters.
I reinstalled it again, same problem.

Rachel Duim, Mon, 20 Oct 2025 10:59:57 -0400
Try using the Mac or Windows version of.FF7 from this, top of this post:
https://www.filterforge.com/forum/read...sage162582

CFandM, Mon, 20 Oct 2025 14:23:34 -0400
I tried FF6 and it has the same issue. I then tried FF9 and had no issues of downloading filters. I have not tried FF8 since I cannot find the serial at the moment. So it seems at the moment anything FF7 and under does not work at connecting.. I have used the Windows version so I cannot speak for the Mac version...

Rachel Duim, Mon, 20 Oct 2025 21:58:24 -0400
Many outages today (Amazon Cloud Services was down, used by a lot of companies). I was able to download/update filters in FF6 and FF7 on my Macbook Pro just now.

UPDATE: FF6 and FF7 still do not connect to the servers under Windows 10. FF8 and above work properly.

GMM, Tue, 21 Oct 2025 06:39:46 -0400
Filter Forge 7 had been released in 2017 - that's 8 years ago - and was discontinued in 2018. It is very possible that recent Windows updates broke connectivity between the program and the library server.

The library itself is working properly, since Rachel is able to download filters under Mac.

xxstyxx, Tue, 21 Oct 2025 14:26:31 -0400
I tried the other installer, same result.
Is there a way to manually download the filters and add them to the library?

GMM, Wed, 22 Oct 2025 05:45:45 -0400

Quote
xxstyxx wrote: Is there a way to manually download the filters and add them to the library?

Yes, sort of.

Please check the "Filter Library Backup + Librarian" and "Filter Library Backup without Librarian" options here.

The Render Animation output goes almost pink

Matsuzaki — Wed, 15 Oct 2025 16:07:47 -0400

Matsuzaki, Wed, 14 May 2025 04:19:42 -0400
File > Render Animation > Image sequence, when Seamless Tiling is on and the Source is larger than a specific size, the colour pink is dominant.
Is this a lack of specs on my PC, or is it a bug?
It occurs in FilterForge 14.004

GMM, Thu, 15 May 2025 05:50:46 -0400
Welcome to the forums!

This is not related to the File > Render Animation command, you'll get the same result when selecting Save Image As.

The pink color is the default error color. Most probably your filter is trying to divide something by zero.

Matsuzaki, Thu, 15 May 2025 07:09:45 -0400
Hi GMM, thank you for your reply!
The Save Image As function is working correctly in my environment, too.
(I output 60 images individually to make an animated GIF.)

I tried it on two different machines with the same result.

GMM, Thu, 15 May 2025 10:51:17 -0400
Does it happen with a different filter?

Matsuzaki, Thu, 15 May 2025 12:10:06 -0400
I have checked through three filters.
Two of my filters are placed in the filter library.

The error occurs when the size is 1050 or more pixels.

Matsuzaki, Thu, 15 May 2025 13:18:00 -0400
I tried animation filters created by someone else. No errors appeared. There seems to be something unusual about my filters, but I haven't figured it out yet.

Errors occur in three of my four filters in the filter library.

Matsuzaki, Thu, 15 May 2025 14:05:49 -0400
The filters that did not have the error could not use Seamless Tiling.
If Seamless Tiling is turned on, the same error occurs for filters created by others.

The result was the same for output via a video.

CFandM, Fri, 16 May 2025 10:13:17 -0400
When creating a filter one has to think of the usage for that filter. This will sometimes give a direction on when to use the components marked with the word Free. I took a look at some of your filters and seen that you were using the free components in the groups. Changing the xy Anchor to max seems to fix the issue. After I did this the filter above seems to work fine. There are also seamless and non-seamless components that once in a while do not play nice with each other so it is a balance of their usage when using those in the same filter. Sacrificing one thing for another thing is part of that balance.

Matsuzaki, Fri, 16 May 2025 13:16:36 -0400
Hi CFandM, thank you for viewing my node!

It occurs even with a simple animation filter, if seamless is on, which has only suitable components for seamless.

CFandM, Fri, 16 May 2025 16:40:15 -0400
The issue is with the lookup being a seamless component and the profile gradients being seamless. If you use the free gradients with this but slightly modded there is no issue, if this is what you are going for. Change the xy anchor on the gradients.

CFandM, Fri, 16 May 2025 16:41:48 -0400
Here is the filter for the image above.

CFandM, Fri, 16 May 2025 16:43:05 -0400
There are different ways to accomplish what you are going for and sometimes it takes a little tweaking. :) Rendered at 1500 by 1500 and then shrunk down after the fact.

CFandM, Fri, 16 May 2025 16:45:51 -0400

Quote
CFandM wrote: The issue is with the lookup being a seamless component and the profile gradients being seamless. If you use the free gradients with this but slightly modded there is no issue, if this is what you are going for. Change the xy anchor on the gradients.

Meant to say the lookup being a non-seamless and the profile gradient being a seamless.

Matsuzaki, Fri, 16 May 2025 17:06:53 -0400
The lookup was erased, but the error still occurs. Why is that?

File > Render Animation, output at large sizes will result in an error, but there is no problem when outputting in small sizes.

CFandM, Fri, 16 May 2025 17:17:04 -0400
First, what version of FF are you using?. Basic, pro, etc.......
Second, what size is the blank image and change the fill color alpha to transparent when changing the size.
Third, Instead of using the phase connect the Normalized time to the offset on the profile gradient and
connect the map component to the profile gradient. see if the same thing happens.
Also check the size,pixels by the seamless checkbox to make sure it is all the way up.
You could also try the filter I posted to see if the same thing happens.

Matsuzaki, Fri, 16 May 2025 17:51:54 -0400
Could I have done what you have shown me?

This also results in an error.

CFandM, Fri, 16 May 2025 18:05:57 -0400
If that is a bug and it is a weird one I cannot reproduce it. I am using win10.....

Matsuzaki, Fri, 16 May 2025 18:27:51 -0400
This cannot be seen in the preview.
Only images output from File > Render Animation show an error.

I also use Win10.

CFandM, Fri, 16 May 2025 18:49:18 -0400
I did not have any issue with rendering frames. The only other thing I can suggest although you may have done this already is create a new filter with just the above components that you posted if you have not done so. There might be a floating component somewhere.
Post in the bug section with a link to this thread.

CFandM, Fri, 16 May 2025 19:27:25 -0400
Ok I thought about this problem and thought back to a bug report I made over 15 years ago. Took me a minute to get to the right number to reproduce the error that you have. Maybe when reporting the bug the FF team will have a direction to go. ;) :)
Seamless tiling was turned on and a blank image of the size posted was created. Then rendered as you posted. :)

CFandM, Fri, 16 May 2025 20:13:16 -0400
One other thing that I noticed about this. Since I could not reproduce it it did take a bit to reproduce it. Once I did now the 1500x1500 now give me the result as above.

CFandM, Fri, 16 May 2025 20:14:13 -0400
Others sizes also give me the same result.

Matsuzaki, Sat, 17 May 2025 00:37:34 -0400
CFandM, Thank you so much for your reproduce!

CFandM, Sat, 17 May 2025 01:17:45 -0400
You are very welcome. Sometimes the hard part is figuring out how to reproduce the bugs. :)
I tried just a simple profile gradient and got the same result. Saving the image at 1500x1500 all was normal
then I rendered a frame of the animation and got the bug......

CFandM, Sat, 17 May 2025 01:35:02 -0400
It seems that now I have reproduced that bug on my machine it also affects the video as well. Before the bug showing up it did not. ;) :D

CFandM, Sat, 17 May 2025 10:45:48 -0400
Kinda of a odd issue although it could be a quick fix sorta maybe. I uninstalled FF 14 and reinstalled. I then used the gradient filter tree above and rendered a frame without the seamless tile enabled. I used 1651x1500 px. I then rendered another frame with the seamless tile checked at the same size of 1651x1500 px.
Now check the same method at the size of 1500x1500 to see if you now get a good image... If you get a good image then see if you are good to go..

Matsuzaki, Sat, 17 May 2025 11:37:16 -0400
I uninstalled it and then reinstalled it, and followed your suggestion. But that ritual doesn't seem to work on my PC.

CFandM, Sat, 17 May 2025 11:49:32 -0400
It is a random one when it wants to show up or disappear. I uninstalled and manually deleted the folders that the uninstaller does not. Then I downloaded the installer from the website and installed from that. Regardless I will now move on to something else and wait to see what happens with this one.. :)

Matsuzaki, Sat, 17 May 2025 12:28:26 -0400
Thank you for everything. I'll try this ritual again later.

I'm writing this as a note below, so you don't have to worry about it anymore.

I deleted the following folders after uninstalling, but it did not improve.
Is there anything else I should delete after uninstalling?

　C:\Program Files\Filter Forge 14
　C:\Users\<user>\AppData\Roaming\Filter Forge 14

CFandM, Sat, 17 May 2025 17:08:20 -0400

Quote
Matsuzaki wrote: Thank you for everything. I'll try this ritual again later. I'm writing this as a note below, so you don't have to worry about it anymore.

You are welcome and I had to try it again because it was annoying me that I did not have an answer. :D
I did figure it out and the reason. When you are in the main window for FF at the bottom there is a button to display the image
in draft mode. When you are in draft mode saving an image saves as normal but for some reason it does not when rendering
animations or frames. Simply clicking that off to get out of draft mode works.

CFandM, Sat, 17 May 2025 17:08:40 -0400
Here is the button location.

CFandM, Sat, 17 May 2025 17:21:41 -0400
One more image with the draft mode on and then draft mode off. The image was rendered at 1500x1500

CFandM, Sat, 17 May 2025 18:05:09 -0400
So now we got... With draft mode on and specific filters with specific components that have specific basic animated properties and seamless tiling turned on.
Create a new blank image of at least 1500x1500. Saving the image as normal works as it should. Rendering a frame or an animation will produce the oddness.
Turning draft mode off in the main workspace fixes the issue....
:)

CFandM, Sat, 17 May 2025 22:06:40 -0400
Just a quick video of the above method to produce the oddness. Draft on off render error

Matsuzaki, Sun, 18 May 2025 00:05:08 -0400
Appreciate your effort! It's interesting behaviour.
I have been working with Draft Mode off all the time ever, but the output is correct if Preview Size is Actual! Thank you!

CFandM, Sun, 18 May 2025 04:21:48 -0400
Glad you got it working. :D
Working in actual size is something I do unless there is a slowdown in rendering.
It is unusual for the draft mode and rendering of animated frames to have the oddness
on only certain filters while working fine with others in the same mode.

einfach Alberto, Wed, 15 Oct 2025 16:07:47 -0400
Hello and thank you to find a workaround for this bug by change preview size to actual. I had the same problem and reported a similar bug in May. Now, with actual Filter Forge version this bug should be fixed. I got a correct rendered higher resolution image while draft mode was on

FF Killing Resolution

StevieJ — Tue, 09 Sep 2025 05:22:32 -0400

StevieJ, Sun, 28 Jul 2013 14:12:04 -0400
I just discovered why all my renders at high res are not coming out right... FF is converting all resolutions to 72 DPI while keeping the same pixel size...thus degrading the result resolution of any image higher than 72 DPI put through any filter... This one should definitely be at the top of FF's "Must Fix ASAP" list... :|

ThreeDee, Sun, 28 Jul 2013 15:15:43 -0400
Can you not just resize them back to correct resolution (without resampling) in Photoshop?

SpaceRay, Sun, 28 Jul 2013 17:36:45 -0400

Quote
StevieJ FF is converting all resolutions to 72 DPI while keeping the same pixel size

WOW! I did not know about this and I did not notice until you have said it, thanks for letting me know about this.

Although is true and surprising that Filter Forge really convert all the results to 72 DPI for all the results and I did not know that, BUT as it keeps the same pixel size it does NOT resamples the image, so there is no loss of quality, and so there is no degradation of quality, unless you print it at 72dpi ;)

As ThreeDee have said, the simple solution is to "resize" (not really good word because you are not resizing it really) the dpi to the value you want WITHOUT resampling it, so you keep the same quality and can change the dpi as you want.

It can be done in Photoshop or any other similar software that allows to do this

___________________________________
___________________________________

I have also seen that it has been discovered also by another one in this website

JilbertÂ´s website about Filter Forge

Quote
Jilbert website Another little thing I discovered is that Filter Forge saves this â€œimageâ€ at 72dpi â€¦ if you are planning on using this for scrapbooking, you need to bring it into your favorite graphics program and save it back out at 300dpi. If you want to avoid this step, start from Photoshop; create a new document at 300 dpi; create a new layer; and start up Filter Forge from there (Filters > Filter Forge > ). That way you can insure the item is saved out at the right resolution.

Quote

Jilbert website

Another little thing I discovered is that Filter Forge saves this â€œimageâ€ at 72dpi â€¦ if you are planning on using this for scrapbooking, you need to bring it into your favorite graphics program and save it back out at 300dpi.

If you want to avoid this step, start from Photoshop; create a new document at 300 dpi; create a new layer; and start up Filter Forge from there (Filters > Filter Forge > ). That way you can insure the item is saved out at the right resolution.

_____________________________
_____________________________

I have also seen that this topic has been already been in another thread before

DPI question

Quote
jffe What's the deal with setting DPI in the FF stand-alone ? I cannot seem to find a place to do that, and I can't imagine that we're supposed to just do the pixel math, then convert it to 300DPI or whatever

Quote
Vladimir Golovin wrote in february 2007 (I've added this to the list, but it's currently placed on low priority, so don't expect it soon. There are things with higher priority that need to be fixed in this department, for example color management. Personally, when I need to change the DPI while preserving the pixel dimensions, I use Photoshop's Image Size dialog with the Resample checkbox turned off.

Quote

Vladimir Golovin wrote in february 2007

(I've added this to the list, but it's currently placed on low priority, so don't expect it soon. There are things with higher priority that need to be fixed in this department, for example color management.

Personally, when I need to change the DPI while preserving the pixel dimensions, I use Photoshop's Image Size dialog with the Resample checkbox turned off.

He was right to not wait and expect it soon ;) :D :D still in 2013 it has not been solved :D

BUT as he says there is the Photoshop Image size dialog OR there are also other FREE or alternative software that can also make the conversion without having to calculate anything.

StevieJ, Sun, 28 Jul 2013 19:25:30 -0400
This totally sucks!!! I want FF to pay for all the time that I wasted trying to render things correctly...and being misled to think that it was the rendering bug...when the whole time FF knew exactly what it was... :evil: :evil: :evil: :evil: :evil: :evil: :evil: :evil: :evil:

@ThreeDee... You loose all picture information beyond 72 ppi... For example, I discovered this by running a 10,000 x 10,000 pixel - 300 ppi image thru a simple filter...and the result came out totally different from what the pre-rendered display image showed the result was supposed to look like...because the result was a 10,000 x 10,000 - 72 ppi image...about 75% of the picture info was completely lost...with no way to get it back... The picture info is even further damaged by FF's re-interpolation of all the picture info down to 72 ppi...

The kicker is that the display image is showing what the result "should" look like at the original resolution... No wonder I couldn't get close to what it was supposed to look like without taking down the image resolution... This is astronomically bad...I'm upset that FF didn't disclose this about the program...and made me waste sooooo much rendering time over the years trying to get my image results to match what they were supposed to look like on the screen... Thanks FF!!! This is what happens when you care more about the money than a quality product... :evil:

Skybase, Sun, 28 Jul 2013 22:36:17 -0400
I think I get what you mean! ;) But allow me to explain this quickly before this becomes another confused thread.

Here's a small test I did with 72ppi vs 300ppi on a 1280x720 rendered via the Photoshop plugin.

Doesn't seem like there's much difference. Right because ppi doesn't affect image quality, it comes into play when you have devices set at that resolution. Pixels per inch is speaking about density of the pixels within a certain amount, in this case inches. Given that if you have an image set at 1280x720 at 300ppi, you basically have 300pixels crammed into 1inch of space on screen. Note that by changing ppi you're effectively targeting certain screen devices. But, it won't affect the number of pixels that image actually is.

PPI/DPI (while having different properties) often get shared a spot. For example a 900x900px image set at 300dpi becomes a 3x3inch image, but a 900x900px image set at 100dpi will be a 9x9inch image when printed. Note that the differences aren't in the image resolution but affects the size in print. Once again, just like with ppi dots per inch is telling the other device "cram more dots in 1 inch".

You can set ppi/dpi right in Photoshop without scaling the image of course. Just disable resampling and you're done. It won't affect what pixel size you have, it'll affect the density of pixels which get displayed when printed or observed on a separate device.

Pretty sure you already know this with all of the talk above! ;)

I think preview resolution is the culprit here. When FF renders a 600x600 resolution for preview, it's really only doing as much. So if you render 10,000x10,000 px resolution, but you sample the image with a 600x600 preview, you'll more likely get a different result. This happens with other high-end render engines too! Preview render is often a bit ... distorted and a bit messed up. You'd have to compensate for anything of that nature.

In FilterForge, you can right click and view "actual pixels" in preview and see all the pixel glory. Remember, you can fix ppi later in Photoshop without affecting the pixel image resolution.

I think that keeps a lot of things covered, I think much of what I said there was right but you know... if there's something faulty I would like to know. SpaceRay's provided several little readings that totally answer your issue.

Hope that kinda... helps?

SpaceRay, Mon, 29 Jul 2013 00:12:35 -0400
I have found this that maybe could be useful here

Andrew Dacey - Dispelling the 72 dpi myth

Quote
Andrew Dacey the dpi setting is just a tiny little flag in the file saying â€œif you were to print this you should print it at this resolutionâ€, you can change that at any time without changing the file size (assuming youâ€™re only changing the dpi setting and not resampling).

Andrew Dacey - DPI and PPI Explained

ThreeDee, Mon, 29 Jul 2013 03:10:26 -0400
I still believe (although I haven't tried it) that you should be able to render a 10,000 x 10,000 pixel 72 ppi image and then convert it to 300 ppi afterwards.

Skybase, Mon, 29 Jul 2013 03:52:05 -0400
Right, because you CAN change ppi/dpi without affecting image resolution in terms of the number of pixels present in the image. In the end ppi / dpi is about output.

So to me, all of this, as much as there's part with FilterForge's mild issue not respecting DPI, this thread's also kinda like... errm... technical misunderstanding?

SpaceRay, Mon, 29 Jul 2013 04:00:58 -0400
THE 72 DPI/PPI LIMITATION OF FF CAN BE SOLVED IF USED AS A PLUGIN APPLYING TO THE IMAGE WITHOUT SAVING DIRECTLY FROM FF

I have made some tests and if use the standalone version it will always save the result as 72 pixels/inch BUT I have seen that if you use FF as a plugin and use the "APPLY" to the image instead of saving it from FF, then it keeps the SAME resolution and dpi/ppi as the original when applying the filter to the image and it does NOT convert it to 72dpi/ppi.

BUT if you use the FF plugin AND you want to save the image directly from the FF plugin instead of applying the filter to the original image in the plugin host, it STILL will convert it to 72 dpi/ppi the same as in standalone.

So the problem seems when FF itself saves the image, so avoid to do it

Quote
ThreeDee I still believe (although I haven't tried it) that you should be able to render a 10,000 x 10,000 pixel 72 ppi image and then convert it to 300 ppi afterwards.

YES; you are right, and is true, I have tried it myself and you CAN SAFELY convert it to 300dpi from 72dpi as FF saves it because it keeps the same pixels resolution, BUT what Steviej is saying is NOT that this canÂ´t be done, what he is saying is that lots of color information is lost when saving at 72dpi/ppi by FF

Quote
StevieJ You loose all picture information beyond 72 ppi... For example, I discovered this by running a 10,000 x 10,000 pixel - 300 ppi image thru a simple filter...and the result came out totally different from what the pre-rendered display image showed the result was supposed to look like

Well, to see if this happens to me, I have made myself some tests with a 12000x9500 image using the watercolor by Kochubey filter.

FF WILL CONVERT ALSO ANY IMAGE TO sRGB COLOR SPACE INSTEAD OF KEEPING THE ORIGINAL WHEN SAVING DIRECTLY :evil: :(

So it will convert the image to 72dpi/ppi AND also will convert any image from another color space to sRGB and will not keep it.

For me the saved result from FF standalone version looks exactly the same as the one you can preview using View --> Preview Size --> Actual . I mean that for me all the colors are the same and it seems that there is no loss of quality. The result is converted to 72dpi/ppi

BUT then after I used the FF plugin version and using Photoshop I made 2 images from the filter, I saved one version directly from FF plugin and then after I clicked on "Apply" so the filter was applied to the image in the host software. The saved from FF was at 72 dpi/ppi, and the applied to host kept the 300dpi/ppi

WHAT I FOUND was a slighty change in colors between both versions, and I wondered why and discovered that the image that I applied the FF filter instead of saving kept the original color space and the one saved directly from FF has been converted without notice to sRGB!!!! :evil: :evil:

More information here

Why FF converts all the images to sRGB color space WITHOUT asking?

BE AWARE photographers that use Adobe RGB and printers that use CMYK!!

StevieJ, Tue, 30 Jul 2013 09:16:14 -0400
Guys... If you run a 10,000 x 10,000 pixel @ 300 ppi image thru a filter and the comes out as 10,000 x 10,000 @ 72 ppi... you've lost about 75% of the original picture information...not to mention the remaining 72 ppi information that gets degraded by interpolation to "re-fit" the original dimension... Here is an example of what happens...

This is how the 300 ppi image is supposed to render...

StevieJ, Tue, 30 Jul 2013 09:19:29 -0400
This is how it renders stripped of original picture info from 300 ppi to 72 ppi...

ThreeDee, Tue, 30 Jul 2013 09:59:12 -0400
I was about to again suggest converting the image to 10000x10000 72 dpi before feeding it into FF, then I dedided to give it a try. I think there is some other problem here, for when I tried a 4752x3168 pixel image both at 300 ppi and a 72 ppi and neither exhibited any issues: both came out at full resolution.

Yes, the 300 ppi image was converted to 72 ppi, but no pixel information was lost.

ThreeDee, Tue, 30 Jul 2013 10:19:08 -0400

Quote
If you run a 10,000 x 10,000 pixel @ 300 ppi image thru a filter and the comes out as 10,000 x 10,000 @ 72 ppi... you've lost about 75% of the original picture information

No, you haven't, UNLESS the information has been RESAMPLED, and per my test FF does not resample the image, it just changes the resolution. You have the exact same 10 000 x 10 000 pixels as in the original image.

StevieJ, Tue, 30 Jul 2013 10:28:55 -0400
That's because it is not so obvious below 5000...which is what I've been having to do to get close to what it's supposed to render like... The surface/HDRI filters really show it...

This will show it... Take or create a 10k x 10k @ 72 ppi image...and then up the same image to a second 300 ppi image in PS... Render both in a simple surface filter....then compare... Also compare the 300 ppi image result to the display image...because the dislay is showing what it "should" look like after rendering...

Skybase, Tue, 30 Jul 2013 10:32:54 -0400
Aye, probably do some more tests here as well.

But please make sure that resampling is disabled when changing 300 to 72. ;)

ThreeDee, Tue, 30 Jul 2013 10:38:17 -0400
You can see this for yourself: One of these images is a 300 dpi image that was input into FF, the other one is the 72 dpi image that was saved from FF. Which one is which?

StevieJ, Tue, 30 Jul 2013 10:42:14 -0400
Also can see it taking a full 10k x 10k @ 300 ppi...render it at 100% quality...then render the same image at 25% quality...

This source of this problem may also lie in HDRI mapping in surface results...

StevieJ, Tue, 30 Jul 2013 10:47:47 -0400
ThreeDee... it won't be obvious with an image like that... Try using a surface result creative filter that significantly manipulates pixels upon height and HDRI...using the low and high res of the same image....then you'll see it...

There's something majorly wrong with FF doing anything to image resolution anyway...and all images "should" come thru filters at the same resolution as they go in... Even as a PS plugin...creating a 72 ppi FF layer on a higher res image is an technical and unprofessional graphic no-no...

Skybase, Tue, 30 Jul 2013 10:56:51 -0400
What?

StevieJ, I'm honestly confused... you might wanna give us a full list of what you're doing step by step.

StevieJ, Tue, 30 Jul 2013 11:20:08 -0400
Just use a surface result creative filter that significantly manipulates pixels upon height and HDRI...using the low and high res of the same image....then you'll see what I'm talking about... The above images that I posted above shows it perfectly...picture info is gone...resulting in HDRI mapping contours of posterized tone...

Skybase, Tue, 30 Jul 2013 11:52:11 -0400
Gotcha. I see differences as well. Steps seem a bit complicated to do it exactly, but I'll pick up a creative filter that renders fast next time. So while you were writing that, I was conducting a test as well of my own. Quite curious myself. I kinda doubted myself here. heh.

So I made an image 10,000x10,000px at first 300dpi, then applied "clouds" Photoshop filter and saved that as png. The resulting image is 300.5mb. Then I changed the dpi to 72 via image size menu without resampling. I saved that as a separate file. File results in 300.5mb as expected.

I created a very simple filter that feeds the image right into the height of a surface filter for this test part because you were speaking about surface filters previously.

I first fed the 72dpi then fed 300dpi images into that filter. Now, I unfortunately don't have much time rendering the entire 10k image so I thought I take a portion of the render by screen capping a render in the FF window with "Actual Pixels" displaying (not the preview resolution). Note that both of these images are zoomed up at 100% of the 10k image on the left hand corner.

Now obviously, I've done something quite differently from what you've done. So I'm holding back conclusions here. But based on this test alone, I observe no difference between the two images. I hope this helps part of the discussion.

With love! :)

[Edited several times] Clarified details.

ThreeDee, Tue, 30 Jul 2013 12:05:28 -0400
StevieJ,

I made a similar test with identical results for 72 and 300 dpi.

I am suspecting a image resolution vs.pixel size confusion.

Let me guess: You have an original image that is not 10000x10000 pixels. The filter looks good on this original image. So you resize the image to 10000x10000 pixels, run the filter and it looks different.

If that is what is happening, it is not a Filter Forge resolution issue.

ThreeDee, Tue, 30 Jul 2013 12:07:36 -0400
Here is my 10K 72 vs. 300 dpi test render.

In fact, if I lay one on top of the other in difference blending mode, I get a fully black image. So there is absolutely no difference between the two.

ThreeDee, Tue, 30 Jul 2013 12:18:55 -0400
Are we having fun yet? :-p

SpaceRay, Tue, 30 Jul 2013 12:26:11 -0400
Hello StevieJ, I am sorry to say that I do not understand what you are saying and I have made another test and I canÂ´t see any difference, and I canÂ´t see where the image is loosing quality or information.

What FF is doing is ONLY a conversion WITHOUT RESAMPLING of the image fr om 300ppi (or whatever that is different than 72ppi) to 72ppi, and then you can take it back to 300ppi in any software that can do this and you are not loosing any information or quality if you do not resample it.

PLEASE GIVE US STEP BY STEP INSTRUCTIONS TO REPRODUCE IT

I think that we will not find what you mean and have discovered IF we do not know what we have to look for and where have to to look and what really happens.

Please tell us step by step what we have to do to be able to reproduce and test what you mean and what exactly have to do and what we have to search for and what is the problem and wh ere to find it and so it will much more easier to help you and really discover what is happening.

Also tell us wich surface filter to use that will give the bad result that you are telling

Also if you want you could show another screenshots and write what you are seeing wrong on that screenshot versus what should be.

StevieJ, Fri, 02 Aug 2013 15:36:05 -0400
No... The images are originally at high res size...display shows what the render should look like...but doesn't render even close to display image... As you cut the resolution to the original high res image, the render gets closer to what the display image is showing...and the same thing happens as you cut precision...

I think a start would be for FF not to be affecting resolution at all...like all other graphics programs... All images should come out at the exact resolution as they get put through a filter... My results are showing that something is most definitely wrong...and I think FF changing image resolution is pointing to the source of the problem...

Thanks for trying to help me figure this out guys... Much appreciated... :)

SpaceRay, Fri, 02 Aug 2013 23:49:43 -0400
When you save the render result fr om FF, what format do you use, is it TIFF, Jpeg or what are you saving it with? If Jpeg are you using a high compression?

Please StevieJ, have you tried to make the same that you want to do using FF as plugin with any host supported software?

Because I have tested that if you use FF as a plugin it does NOT convert the image to 72ppi and does not change the color space, and does not have any problem that may be possible with the standalone version.

Does it happens the same mistery thing that you are telling IF you use FF as a plugin also?

Quote
Skybase StevieJ, I'm honestly confused... you might wanna give us a full list of what you're doing step by step.

As Skybase say and also as I said above, if you want that the FF team or any of us in the forum can help you discover what is wrong and what is happening you have to tell us WHAT are you exactly doing so we the FF team and we can reproduce ourselves and see what really happens.

Quote
StevieJ The images are originally at high res size...display shows what the render should look like...but doesn't render even close to display image... As you cut the resolution to the original high res image, the render gets closer to what the display image is showing...and the same thing happens as you cut precision...

I am sorry that I now I understand even less than before, and do not know what you mean. :?:

When you mean "display shows" is this when you change the menu View --> Preview Size --> Actual that is wh ere you can see what the render should look like and what you are going to get for real?
And you mean that FF when you try to use File-->Save with that same image (using FF standalone I think) and then FF renders the result you are getting a different result than the one shown by the Preview Actual Size?

What do you mean with "if you cut the resolution to the original high res image" :?: when you have said that the images originally are already at high resolution size? How do you cut the resolution to the original size? which one is the original high res image and wich one is the source resolution? :?:

So do you mean that if you have a 10.000 x 10.000 image that is the original size, you cut or reduce the resolution to half of it, you are getting the renders better and closer to what Actual Size preview shows?

What do you mean when you say that you "cut precision" ? :?: What precision? Precision of what?

Quote
StevieJ I think a start would be for FF not to be affecting resolution at all...like all other graphics programs... All images should come out at the exact resolution as they get put through a filter...

FF is not affecting (at least in my version) in any way the resolution of the image at all if I understand resolution by the size of the image that it has and not the 72ppi that you said above. When you put a 3000x3000 pixels image through FF you will get exactly the same 3000x3000 when rendering the result so the image resolution is not affected or changed.

Another different thing is that the ppi is modified from whatever the image may have configured to the 72ppi that FF converts any image result ONLY IF you are using FF as standalone or saving with File -->Save in the plugin, because if you use FF as a plugin the ppi will NOT be changed or modified and will keep exactly the same as the original source

IMAGE RESOLUTION

Quote
What is Resolution? Resolution is the term used to describe the number of dots, or pixels, used to display an image.Put into some very basic terms, resolution is the quality of the image. As the resolution goes up, the image becomes more clear. It becomes sharper, more defined, and more detailed as well.

Image resolution explained very much in Wikipedia

What Is Image Resolution? Why Does It Matter?

Although with the same resolution you can have different quality depending on the file format you are using and if you are using lossy compression as it happens in jpeg files that degrades the quality if the compression is high.

PRINT RESOLUTION

Another different thing is the print resolution that means the size at what you can print an image depending on the image resolution it has that is measured in ppi (pixels per inch) and usually is 200 or 300ppi but for the web is used 72 ppi. BUT the ppi never affects or modifies the quality of the image what is important is the image resolution and if the image has some compression.

There this useful and interesting 7 pages PDF that explains it well Understanding Resolution and the meaning of DPI, PPI, SPI, & LPI

Sphinx., Sat, 03 Aug 2013 02:36:21 -0400
Well, FF resetting the DPI is quite annoying if you're going to use the images for layout and print. I actually had problems with this before. But like mentioned its not a big problem - just a little extra work: change the DPI without resampling the image. Its simply metainformation telling how "big" a pixel is when printed. ;)

(is it possible that PS "tricked you" into believing this mattered? you changed the DPI *and* accidently resampled at the same time?)

SpaceRay, Sun, 04 Aug 2013 13:04:45 -0400
To know if the guilty is really Filter Forge (FF) that as you say, is "killing" the resolution

Please can you be so kind to do the following to make the test and see if this is true?

StevieJ, can you do a test any image that you may want using FF as a plugin of any host software that may be compatible with FF?

And using the plugin, just "APPLY" the filter to the image instead of saving it from filter forge.

Because I have seen that if you use FF as a plugin:

It does NOT convert the original ppi to 72ppi

It does NOT convert the original color space to sRGB

It does NOT change anything in the image (so it canÂ´t "kill" the resolution) and only exports the filter render result to the host software without changing the original source metadata.

So if you make this test and then the result is really what you want and as you wanted, then you can really know that the guilty is the standalone version of FF

If after making this test you continue having the same problems even when you FF as a plugin, then there is another mistery and unknown problem that should be found and see what is and what happens

Ozmandias, Sun, 04 Aug 2013 19:14:17 -0400
ThreeDee seems to be the only one that understands.

ppi (Pixels Per Inch) is important ONLY when printing. It has NO impact on the digital image itself. If no resampling is done and you maintain the original pixels wide and high, then there is no change to the image. It doesn't matter if it is displayed 72ppi, 300ppi, 96ppi... it doesn't matter!

People also seem to confuse ppi with dpi. They are not the same thing. dpi (DOTS per inch) is a parameter of a PRINTER, not an image.

Skybase, Sun, 04 Aug 2013 21:56:35 -0400
Statement above can use clarification: From wikipedia on PPI "Pixels per centimeter (ppcm), Pixels per inch (PPI) or pixel density is a measurement of the resolution of devices in various contexts: typically computer displays, image scanners, and digital camera image sensors."

PPI is important when handling computer monitor resolutions. Data set is the same, but what gets displayed is what's concerned: i.e. iPhone 5 has a monitor ppi resolution of: 326 ppi.

Ozmandias, Mon, 05 Aug 2013 08:30:51 -0400
Unfortunately, just like dpi and ppi, people frequently use the term resolution when they should be using the term pixel density.

Using the iPhone 5 as an example here...

The iPhone 5 screen has a RESOLUTION of 1136 pixels x 640 pixels... that's the number of pixels along the height and width. That screen has a pixel DENSITY of 326 pixels per inch.

Another way to see it without the confusing words. The iPhone 5 screen is 1136px x 640px. Measurement-wise, it is 90.25mm x 51.60mm. Converting those mm's to inches and rounding off the resulting numbers (for ease of calculation), we get approximately 3-1/2 inches high x 2 inches wide.

Let's look at the height first... Along the height of the screen, there are 1136 pixels. That divided by 3-1/2 inches is... 325 Pixels Per Inch (it would have been 326 had I not rounded)

and along the width... 640 pixels divided by 2 inches is... 320 Pixels Per Inch. (again, would have been 326 had I not rounded).

For example... you have two of the exact same pictures on your computer but in the image size box, one reports as 1136x640 72ppi and the other as 1136x640 300ppi. Put those on the iPhone 5. Both will look exactly the same. They will fill the iPhone screen and have the exact same quality. Why? Because they both have the same dimensions... the same amount of pixels along the height and width... 1136 x 640. THOSE are the important numbers here. It doesn't matter that one showed 72ppi and one showed 300ppi on your computer.

If you have a photo that is larger... say 1600px x 1200px and put that photo on the iPhone 5, it will be too big for the screen to display and you'll have to scroll/slide. Because, the iPhone screen can only display 326 pixels in an inch and at only about 2 inches wide, can only display about 652 pixels along the width (remember, we rounded... in actuallity, the number is 640). This larger photo has 1200 pixels along the width so it won't fit... you'll have to scroll.

This is a very difficult concept for people to grasp. Once you get it though... you'll say Ohhhhh.

StevieJ, Sun, 08 Sep 2013 12:50:54 -0400
Update: I understand pixel density...which still is a change in resolution at the same canvas size... It looses pixel info any way you look at it...

I have also narrowed part of the problem down to a difference in HDRI dispersement between the low and high pixel "densities" of images... Take a look at the first sample pics of the same image that I posted... That would explain the fact that the display image resolution/density showing the result correctly with the actual high res image coming out much different... In other words...the HDRI is coverage id being posterized at high resolution...and why the smaller you go with the resolution/density...the more closely it matches the display result image... Does this make any sense???

ThreeDee, Sun, 08 Sep 2013 13:48:24 -0400
Can you provide a filter that creates this problem?

EAdams, Thu, 08 May 2014 10:27:54 -0400
This discussion deserves a bump because the phenomenon is a real time consumer. Standalone FF does render images at a document resolution of 72 PPI. It doesn't make sense for a user to have to post-edit every rendered image in a graphics program to change the rendered image back to the original resolution or use Filter Forge only as a plug-in to avoid the problem. I hope this is fixed in the foreseeable future. :)

GMM, Thu, 18 Oct 2018 12:07:35 -0400
Starting with version 8 Filter Forge retains the original DPI metadata.

SpaceRay, Tue, 09 Sep 2025 05:22:32 -0400
It seems that it is still happening these problems that FF standalone will change
any dpi you may have to 72dpi
Will change any color profile to sRGB

But the good news is that as told above this does not happen if you use FF as plug in because it only applies the filter to the image but DOES NOT SAVE IT, so this is why it does not change the image to 72dpi and sRGB IF you use FF as plugin

Affinity Photo Plugin Doesn't Work FF13

SevenSuns1 — Thu, 08 May 2025 11:40:11 -0400

SevenSuns1, Thu, 08 May 2025 11:40:11 -0400
I have the plugin correctly installed in Affinity Photo. It opens FF13 perfectly. When it saves, it shows it saving but it never sends the result back to Affinity Photo. There is no error message. It finishes the save, and that is all. The screen doesn't go back to AF, and there is no file information exchanged. Help please.

Animator problems.

RLOwens — Wed, 12 Mar 2025 11:32:01 -0400

RLOwens, Sun, 02 Mar 2025 21:07:34 -0500
I'm using he demo of animator, and have run into a problem. I'm trying to render presets in the Animated Fire (by IFredQC). If I add the keyframes on time and hit the play button, it makes and displays the preset preview window just fine, but if I try to render it just does the first preset and not the preset I selected.

Also when trying to save out an animation, why am I not able to modify the save name directly in the input box instead of having to select browse and save a new file name?

GMM, Mon, 03 Mar 2025 04:40:06 -0500
RLOwens, thanks for your report but it's difficult to visualize. Please send us the source image file, the filter file (.ffxml) and the project file (.affproj).

Quote
RLOwens wrote: Also when trying to save out an animation, why am I not able to modify the save name directly

Click File > Save Project, and you'll be able to type in the desired file name.

RLOwens, Thu, 06 Mar 2025 23:07:30 -0500
Sorry for late response, I figured out the animation problem.
As for the naming problem, I don't mean when saving a project. I mean when saving out the rendered animation,shown in following screenshot.

GMM, Wed, 12 Mar 2025 11:32:01 -0400

Quote
RLOwens wrote: saving out the rendered animation

This is a universal dialog for saving video files as well as image sequences. You really don't want to type in all the file names in the sequence.

Fillter server down

Rachel Duim — Wed, 12 Mar 2025 11:29:17 -0400

Rachel Duim, Wed, 12 Mar 2025 10:32:39 -0400
The filter server and program updates have been down for at least a few hours, also noticed by Ramlyn, so it's not a local issue.

GMM, Wed, 12 Mar 2025 11:29:17 -0400
The library server was under maintenance and is now up and running - please try again.

Latest update to 13.06

Rod_D — Thu, 30 Jan 2025 00:46:08 -0500

Rod_D, Tue, 28 Jan 2025 02:21:17 -0500
Just updated 13 Pro to Pro - 13.06 and now my registration key will not work. Anyone else having this problem? How do i fix it?

Thx

CFandM, Tue, 28 Jan 2025 23:53:39 -0500
Studio Version works after updating.

Rod_D, Wed, 29 Jan 2025 01:16:51 -0500
It's kind of strange because it opens a window telling me the 30 day trial period is over enter key code.
But i originaly purchased the basic version and then updated to Pro. I've tried both keys and nothing will allow me to use the program. I'm stumped and need help. :(

GMM, Wed, 29 Jan 2025 03:07:33 -0500
Issues like this are never solved in public. With any licensing questions please contact the support team.

Rod_D, Thu, 30 Jan 2025 00:46:08 -0500
Thank you. I have sent a message to Support.

download new filter in FF14 and FF13 opens

Ilmeni — Wed, 22 Jan 2025 06:14:45 -0500

Ilmeni, Sun, 19 Jan 2025 14:57:33 -0500
hi all!
please help :?: me with this: i still have a FF13 studio on my PC, but am currently using FF14 professional. when i try to download Ramlyn's new filter Ap Gas it always opens the FF13 version and i thus cannot download this FF14 filter. how can i change settings so that the website opens my FF14 version and downloads the filter? thank you for your help! :)

Rachel Duim, Sun, 19 Jan 2025 16:05:09 -0500
The file association for .ffxml files (Filter Forge filters) is set to FF13. Which operating system do you have? What browser are you using?

Ilmeni, Tue, 21 Jan 2025 03:47:12 -0500
thank you, Rachel, that helped -- as always! :)

i first tried it with firefox (which i normally use) -- it still didn't work. but it did on microsoft edge/windows 10.
thank you for your help!
:ff:

Rachel Duim, Tue, 21 Jan 2025 22:05:34 -0500
Nice workaround. Here's how to set up the file association in Firefox. Run Firefox.
Windows:
Alt (to show pulldowns), Tools / Settings
Mac:
Firefox / Preferences

Click General at the left. Scroll just past halfway down and you will see the attached graphic.
Find the filterforge type and highlight it. Click the action field. Your choices for filter download that make sense:

Always ask - Lets you pick any version of Filter Forge (that are in the list) to download the filter to. If no versions are in the list "Use other..."
Use other - Change the default program to download the filter to.

Note: FF14 default locations:
Windows - C:\Program Files\Filter Forge 14\Bin
Mac - /Applications/Filter Forge 14

Ilmeni, Wed, 22 Jan 2025 06:14:45 -0500
Rachel, it worked -- and i learned something new! thank you very much! :) :ff:

Visual Batch Renderer errors

chrom — Sun, 05 Jan 2025 01:53:01 -0500

chrom, Thu, 19 Dec 2024 04:17:46 -0500
Hi,

there are many errors:
Many missing pictures for filters and presets.
Output format button not clickable (gray).
Some outputfiles are named png some jpg; opening jpg in viewer says wrong extension it is png.
crash durings tasks. Is there somewhere a logfile?
Cpu percentage setting does not work (set to 70% but use 90%).
for some search-strings search filter does not work. Empty result for existing search-string.

GMM, Mon, 23 Dec 2024 04:06:27 -0500

Quote
chrom wrote: Many missing pictures for filters and presets.

This is by design. Visual Batch Renderer is not intended to render thumbnails. You are expected to wait until thumbnails are rendered in Filter Forge, then add the filters from FF to VBR.

SpaceRay, Sun, 05 Jan 2025 01:53:01 -0500

Quote
chrom wrote: Many missing pictures for filters and presets. Output format button not clickable (gray). Some outputfiles are named png some jpg; opening jpg in viewer says wrong extension it is png. crash durings tasks. Is there somewhere a logfile? Cpu percentage setting does not work (set to 70% but use 90%). for some search-strings search filter does not work. Empty result for existing search-string.

Quote

chrom wrote:
Many missing pictures for filters and presets.
Output format button not clickable (gray).
Some outputfiles are named png some jpg; opening jpg in viewer says wrong extension it is png.
crash durings tasks. Is there somewhere a logfile?
Cpu percentage setting does not work (set to 70% but use 90%).
for some search-strings search filter does not work. Empty result for existing search-string.

it would be from my point of view to help GMM and FF team to help you that you could explain more in detail and depth what exactly is happening and how to be able to reproduce and test the errors you are showing so is more easily to identify and solve it

I mean for example, to tell what you do to get it, what do you expect, and what happens

so, please would be great if you can explain more about the errors you are having

thanks

Version 13 - Frequent crashes Creating Filters

PixelStar — Mon, 11 Nov 2024 17:01:09 -0500

PixelStar, Thu, 07 Nov 2024 10:26:42 -0500
This is happening very frequently. Using FF Version 13 Pro, I submitted a bug report but not sure I was as clear as I could be reporting it so I am reporting it again here.
Computer specs: Windows 11 Home; Laptop with Core i9 13900HX; 64 gb memory; Geforce RTX 4070 Laptop
When: while in filter editor or Group/snippets
How: if I spread my filter modules apart -trying to organize them, it crashes; :!: :?: it crashes as I move around/scrolling fr om one part of the filter to another. Can your team make it to where there is a much larger area within the filter editor that I can spread out the modules? Do you think it has something to do with the "dont panic" feature? Couldn't you make a "center it" button/feature while in the filter editor? So this doesn't just happen as a result of getting lost in the filter editor.. finding the filter modules. I am focused right on the modules and then attempt to scroll down to fix another part of my filter and that is when it crashes. Example: My filter has an image and manipulation to the image; then other parts blended into it such as a frame, etc.. when I scroll over to the frame part or whatever, this is when it crashes.
This is also happening when I am editing a "group" or snippet in the filter editor - it gets lost out of bounds, then while trying to scroll around, trying to find my end point of the filter, it crashes. Do you think maybe there is a limit as to how "hefty" or complex the filter can be? I have found the group and create snippet feature really useful, but not if adding it is going to crash the filter over and over.

And after this is all said and done, after it crashes, it somehow disappears from wh ere I have bookmarked it within my favorites folders. So I have to add it back all over again

PixelStar, Thu, 07 Nov 2024 10:28:25 -0500
Here are more screenshots of "Version 13 - Frequent crashes Creating Filters" After I reproduced the crash, it is gone from my saved place within my favorites folders
I have tried to make the filter smaller and more compact within the filter editor and this doesn't help. I have updated all of the components of the filter to match Version 13 and this doesn't seem to make any difference either

PixelStar, Thu, 07 Nov 2024 10:42:17 -0500
I reproduced the error again with this filter.. this time trying to unplug my "group snippet" from the filter. I don't know if you find this information useful, but the submit bug doesn't have a way to do screenshots. Also, I noticed this time, it happened when I was scrolling/zooming OUT within the filter editor space so I could see the filter better. If I stay zoomed in, it doesn't happen as much
Here it is:
Operating system: Windows 10 x64 Edition (10.0 build 22631)
Physical memory: 65275 MB
Number of processors: 32, available: 32
Processor info: 13th Gen Intel® Core™ i9-13900HX, ~0 MHz

Filter Forge x64 13.005.4275.16034 Release, February 15, 2024 12:53 [11/7/2024 9:38:57 AM -0600]
[Controls::Control] Exception occured while processing window message 0x0000000F(WM_PAINT) (0x00000000 0x00000000) for window 00000000000A0B30/00000000000A0B30, control: <class Controls::FilterEditor>@00000000174A1840.
Critical exception occured at thread 0000000000003C40 'Application':
<class XFW::Exception> Application encountered an unrecoverable critical error and will be terminated.
Critical exception call location:
<unknown file>(0) : <unknown function>()+0 at 0000000140DCBE60 in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : <unknown function>()+0 at 0000000140DBE64B in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : UnhandledExceptionFilter()+492 at 00007FFDD117B21C in C:\Windows\System32\KERNELBASE.dll(00007FFDD1010000)
<unknown file>(0) : LdrResolveDelayLoadsFromDll()+5234 at 00007FFDD3ACABD2 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : KiUserApcDispatcher()+176 at 00007FFDD3A94080 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : _chkstk()+303 at 00007FFDD3A9517F in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RtlFindCharInUnicodeString()+2710 at 00007FFDD3A0E856 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RtlRaiseException()+405 at 00007FFDD3A44925 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RaiseException()+108 at 00007FFDD106FE4C in C:\Windows\System32\KERNELBASE.dll(00007FFDD1010000)
<unknown file>(0) : <unknown function>()+0 at 0000000140DC339D in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : RtlCaptureContext2()+1190 at 00007FFDD3A949C6 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : <unknown function>()+0 at 000000014044DA45 in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : DispatchMessageW()+1857 at 00007FFDD20C83F1 in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : DispatchMessageW()+1020 at 00007FFDD20C80AC in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : GetClassLongW()+1421 at 00007FFDD20D31DD in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : KiUserCallbackDispatcher()+36 at 00007FFDD3A94114 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)

[Controls::Control] Exception occured while processing window message 0x0000000F(WM_PAINT) (0x00000000 0x00000000) for window 00000000000A0B30/00000000000A0B30, control: <class Controls::FilterEditor>@00000000174A1840.
Critical exception occured at thread 0000000000003C40 'Application':
<class XFW::Exception> Application encountered an unrecoverable critical error and will be terminated.
Critical exception call location:
<unknown file>(0) : <unknown function>()+0 at 0000000140DCBE60 in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : <unknown function>()+0 at 0000000140DBE64B in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : UnhandledExceptionFilter()+492 at 00007FFDD117B21C in C:\Windows\System32\KERNELBASE.dll(00007FFDD1010000)
<unknown file>(0) : LdrResolveDelayLoadsFromDll()+5234 at 00007FFDD3ACABD2 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : KiUserApcDispatcher()+176 at 00007FFDD3A94080 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : _chkstk()+303 at 00007FFDD3A9517F in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RtlFindCharInUnicodeString()+2710 at 00007FFDD3A0E856 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RtlRaiseException()+405 at 00007FFDD3A44925 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RaiseException()+108 at 00007FFDD106FE4C in C:\Windows\System32\KERNELBASE.dll(00007FFDD1010000)
<unknown file>(0) : <unknown function>()+0 at 0000000140DC339D in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : RtlCaptureContext2()+1190 at 00007FFDD3A949C6 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : <unknown function>()+0 at 000000014044DA45 in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : DispatchMessageW()+1857 at 00007FFDD20C83F1 in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : DispatchMessageW()+1020 at 00007FFDD20C80AC in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : GetClassLongW()+1421 at 00007FFDD20D31DD in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : KiUserCallbackDispatcher()+36 at 00007FFDD3A94114 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)

GMM, Thu, 07 Nov 2024 10:51:16 -0500

Quote
PixelStar wrote: I reproduced the error again with this filter

Thanks for your report but without the filter file we're unable to look into your issue. Please attached it here or submit to the library.

PixelStar, Thu, 07 Nov 2024 11:14:14 -0500
Ok, I will attach it here, but it really is not a "submittable" filter I think....to the library
For 2 reasons and one is a question:
1) it is not in a place to be workable yet
2) it is a filter that is modified by other users and I was updating combining, experimenting and adding functions from these "other" filters via the group function to enhance it. The reason I did not upload it is that both of these received a reward and I was merely updating these for my own purposes..
This brings up the Question: Am I even allowed to add filters such as these to the library?
The filters' author is: Cartography: This filter created by Crapadilla - I updated / modified elements within the filter
Old Parchment: This filter created by Crapadilla - I updated / modified elements within the filter

PixelStar, Thu, 07 Nov 2024 11:33:12 -0500
I just noticed there is a "zoom to fit" button.. my bad for not seeing this, I will have to try that next time. Either way when I scroll out using the mouse in the editor, that seems to be when it crashes

GMM, Fri, 08 Nov 2024 06:58:55 -0500
What window scaling setting do you have?
Please navigate to 'Display settings' > 'Change the size of text, apps and other items' and set scaling to either 100, 150, or 200.

PixelStar, Mon, 11 Nov 2024 17:01:09 -0500
This time I tried it at 150 display through windows 11 settings and also at 100. Both gave me a termination. it happened when I tried to create a new filter. I had not saved the filter yet. I wanted to test the filter before saving and I went to change the window size within the filters settings at the very bottom "size, pixles" .. it had been pushed to zero on the slider and isn't it usually defaulting to 600 or 700 pixels?

I got this with display set at 100:
Operating system: Windows 10 x64 Edition (10.0 build 22631)
Physical memory: 65275 MB
Number of processors: 32, available: 32
Processor info: 13th Gen Intel® Core™ i9-13900HX, ~0 MHz

Filter Forge x64 13.005.4275.16034 Release, February 15, 2024 12:53 [11/11/2024 3:54:58 PM -0600]
[Controls::Control] Exception occured while processing window message 0x00000201(WM_LBUTTONDOWN) (0x00000001 0x0008000D) for window 00000000001E0C28/00000000001E0C28, control: <class Controls::TrackBar>@0000000013C2A320.
[Controls::Control] Exception occured while processing window message 0x00000008(WM_KILLFOCUS) (0x001E0C0C 0x00000000) for window 00000000001E0C28/00000000001E0C28, control: <class Controls::TrackBar>@0000000013C2A320.
Critical exception occured at thread 0000000000002034 'Application':
<class XFW::Exception> Application encountered an unrecoverable critical error and will be terminated.
Critical exception call location:
<unknown file>(0) : <unknown function>()+0 at 0000000140DCBE60 in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : <unknown function>()+0 at 0000000140DBE64B in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : UnhandledExceptionFilter()+492 at 00007FFDD117B21C in C:\Windows\System32\KERNELBASE.dll(00007FFDD1010000)
<unknown file>(0) : LdrResolveDelayLoadsFromDll()+5234 at 00007FFDD3ACABD2 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : KiUserApcDispatcher()+176 at 00007FFDD3A94080 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : _chkstk()+303 at 00007FFDD3A9517F in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RtlFindCharInUnicodeString()+2710 at 00007FFDD3A0E856 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RtlRaiseException()+405 at 00007FFDD3A44925 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : RaiseException()+108 at 00007FFDD106FE4C in C:\Windows\System32\KERNELBASE.dll(00007FFDD1010000)
<unknown file>(0) : <unknown function>()+0 at 0000000140DC339D in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : RtlCaptureContext2()+1190 at 00007FFDD3A949C6 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)
<unknown file>(0) : <unknown function>()+0 at 000000014044DA45 in C:\Program Files\Filter Forge 13\Bin\Filter Forge x64.exe(0000000140000000)
<unknown file>(0) : DispatchMessageW()+1857 at 00007FFDD20C83F1 in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : DispatchMessageW()+1020 at 00007FFDD20C80AC in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : GetClassLongW()+1421 at 00007FFDD20D31DD in C:\Windows\System32\USER32.DLL(00007FFDD20B0000)
<unknown file>(0) : KiUserCallbackDispatcher()+36 at 00007FFDD3A94114 in C:\Windows\SYSTEM32\ntdll.dll(00007FFDD39F0000)

FF13 won't load into Photoshop Elements 2025

PLSanders — Mon, 11 Nov 2024 11:53:49 -0500

PLSanders, Fri, 08 Nov 2024 11:53:23 -0500
FF12 works fine with Elements 2025. When I load FF13, I get the following message:

Also, FF13 does not recognize Elements as a plug-in during installation.

Am I doing something wrong, or is this a bug?

CFandM, Fri, 08 Nov 2024 11:57:25 -0500
Find some info Here use the elements file structure instead of the photoshop structure.

PLSanders, Fri, 08 Nov 2024 12:36:20 -0500
Thanks. ...so basically, I need to change 'false' in the config file to 'true.
I have tried multiple attempts to set up FF13 in Elements 2025, but I still get this message, no matter what I do:
<class XFW::StateError> The control <class Controls::Control>@000000000CD04560 has no window handle.>
(I've tried both x64 and non-x64 files, changing the false element to true).

CFandM, Fri, 08 Nov 2024 17:12:45 -0500
Yes try that and see if that works. This is what the Filter forge manual plugin install shows.

PLSanders, Sun, 10 Nov 2024 11:52:33 -0500
I did try that and it still does not work. Could it be the FF13 doesn't work with Elements 2025?

CFandM, Sun, 10 Nov 2024 16:47:46 -0500
It is possible that FF does not work with Elements. I do not use Elements so I am not able to try it to find out.
EDIT... I am downloading the trial so I will upload a video in the next day or so or I will post an update...

CFandM, Sun, 10 Nov 2024 17:35:15 -0500
I downloaded the trial of Elements and created a video of how to install FF manually. FF 13 and Elements manual install

PLSanders, Mon, 11 Nov 2024 10:19:08 -0500
Nice aurora pic!
Thanks so much. This worked.
The step that I missed was to save the changes to the config file. When I changed the parameter 'false' to 'true', I thought the change was being saved but it was not.

Also, I tried saving the changes directly in the Adobe plug-in directory, but was not allowed to save them because I did not have administrator access. When I copied the file to my desktop (as you did), saved the changes, and copied it back to the Adobe directory, I was allowed to do so.

CFandM, Mon, 11 Nov 2024 11:53:49 -0500
Glad you got it working. When I first started working on the fix and just using windows in general I came to the conclusion that copying that file to the desktop to change is faster.
Now copy that folder to a safe place so you do not have to go through the steps again. If you have to reinstall Elements or update the software all you need to do
is copy that folder over to the plugins folder.

Thanks, I have a lot of pics of the aurora for this year. It was very active this year and shown up more then usual around the northern part of the US where I am...Sleepless nights but so much fun.... :D

Unable to download filter: Library server connection timed out

Jevon — Thu, 17 Oct 2024 17:51:23 -0400

Jevon, Mon, 28 Mar 2022 20:04:57 -0400
Trying to download a filter but all I get is an error message:

> "Library server connection timed out.Please try again later."

Been trying over the last 15 minutes but no change. I will continue trying but it is frustrating that there's nothing I can do but wait.

Jevon, Mon, 28 Mar 2022 20:13:50 -0400
Site appears to be back up! Yay

SpaceRay, Tue, 29 Mar 2022 17:30:42 -0400
Sometimes happens, that the servers may be not working, and you can not download a filter, but in most of the cases, it will work back again after a few minutes, hours, or next day.

You have to keep trying and testing

Quote
Jevon wrote: Library server connection timed out.Please try again later."

Unless the message is different than this

Gil, Sat, 12 Oct 2024 20:15:14 -0400
I'm going to wait a few days for this to fix itself I guess. I'm glad I don't use this tool for real work.

SpaceRay, Thu, 17 Oct 2024 17:51:23 -0400
As far as I know is not frequent that this happens, and for me in all these years, it gets mostly fixed in some hours or 24 hours, unless maybe that it can be a weekend

FF12 in PS2025

al shawaf — Tue, 15 Oct 2024 14:53:56 -0400

al shawaf, Tue, 15 Oct 2024 05:07:47 -0400
Hi,
Just updated to PS2025, but FF12 has disappeared from the filters menu. Is there any way to get it back?
Many thanks

Djekki, Tue, 15 Oct 2024 11:03:31 -0400

Quote
al shawaf wrote: Just updated to PS2025, but FF12 has disappeared from the filters menu.

Do you mean the version 26.0 that was released yesterday?

Rachel Duim, Tue, 15 Oct 2024 13:17:02 -0400
This might help
https://www.filterforge.com/forum/read...sage162948
Adjust for FF12 directories. Basically this is a manual install. Also adjust for the photoshop version, ps25 instead of ps22.

al shawaf, Tue, 15 Oct 2024 14:53:56 -0400
Hi All,
Yes it is version 26.0 Thanks for your help. The issue was solved by manually moving all filter files from the old installation to the new one.
Many thanks.

Can't Connect to Server

Blazoneer — Wed, 02 Oct 2024 04:29:45 -0400

Blazoneer, Thu, 26 Sep 2024 08:42:56 -0400
Hi,
I'm getting an error message "can't connect to server." Please advise.

I'm allowing cookies. Have filterforge allowed to connect to the internet in the firewall rules. Still, nothing.

hiroweb, Wed, 02 Oct 2024 04:29:45 -0400
I have the same problem..
I copy setting from old pc's appdata roaming and using old filters.

New license keys after autorenew of sub

talos72 — Wed, 11 Sep 2024 10:48:46 -0400

talos72, Mon, 09 Sep 2024 18:48:07 -0400
Are we supposed to be emailed a key automatically when our subscription is renewed? Mine is every 3 months, but I never receive a single email and there is no customer portal to access updates and keys.

GMM, Wed, 11 Sep 2024 10:48:46 -0400

Quote
talos72 wrote: Are we supposed to be emailed a key automatically when our subscription is renewed?

Yes - please also check your spam folder.

Quote
talos72 wrote: there is no customer portal

We only develop the software and don't sell it. You may need to set up an account with your reseller (most likely, ShareIt/MyCommerce: https://www.mycommerce.com/)

Cannot connect for updates or downloading filters

ardlak — Sat, 27 Jul 2024 11:49:14 -0400

ardlak, Thu, 25 Jul 2024 12:09:37 -0400
Using version 6.0, freshly reset router with all firewalls disabled. Filterforge.net returns 403 as it should. Direct connection is selected in settings, no proxy is being used.

This seems to be reported every now and again but is never given a clear solution.

ardlak, Sat, 27 Jul 2024 11:49:14 -0400
Version 13 trial connects fine.

Hoping to get a solution here, otherwise just going to assume obsolescence of my purchase.

FF won't install as a filter in Photoshop 25

Vaylen — Wed, 01 May 2024 08:18:17 -0400

Vaylen, Mon, 20 Nov 2023 16:13:32 -0500
I have a fresh install of Photoshop 25.1.0
When I install FF 12 I don't get an option to install FF as a Photoshop filter, only as a standalone.

In previous versions of Photoshop I would see options to install FF as a filter.

How do I get it to install as a Photoshop 25 filter?

Rachel Duim, Mon, 20 Nov 2023 19:16:57 -0500
Forum user CFandM has produced a video that explains how to manually install the FF plugin. The video is about a different version, but it should work by using the proper version directories (in your case FF12 and PS25.1):
https://www.youtube.com/watch?v=HiO8b_rHBWs

Vaylen, Tue, 21 Nov 2023 11:21:18 -0500
OK, so I need to go into the Filter Forge.config file and change
<IndependentUI value="false"/>
to
<IndependentUI value="true"/>

It worked. Thanks!

Mr Mud Stain, Fri, 15 Dec 2023 05:55:25 -0500
I have a similar problem, but not quite the same:

I just updated to Photoshop 25.3.1
After which, I ran the FF 13 installation program, but the option for installing FF as a Photoshop Plugin was not displayed.

I previously modified FF 12 according to instructions on these forums, so that I could keep using it as a Photoshop plugin after a recent Photoshop update disabled it.

Photoshop is still showing FF 12.007 as the current plugin (working correctly), and I can't edit the FF program plugin config file because when I tried saving the edit, I got a Windows error saying access denied, even though I was running as Administrator. There may be other things that need to be edited, but I'm not sure.

Never had this problem before.

Can someone please help me?

CFandM, Fri, 15 Dec 2023 08:46:27 -0500
Copy the config file for whatever version of FF you are installing to your desktop or another folder on the desktop then edit that config file. Now copy that edited config file back to the original plugin folder. I show this in the video. Also when you set up many versions of Filter Forge in PS put each versions plugin/ config file into a different folder like the following. Each version of the FF plugin needs it own separate folder in PS. Also make sure that PS is closed before editing the config file.

Bookwormious, Tue, 30 Apr 2024 19:42:59 -0400
I have tried all this, but Filter Forge 13 will still not "show up for work" in Photoshop 2024 Beta.
Any ideas or help will be much appreciated :)
And please spell it out in details since I am not a professional and need it explanationed to me as if I was ten instead of sixty seven :D

CFandM, Wed, 01 May 2024 07:07:52 -0400

Quote
Bookwormious wrote: I have tried all this, but Filter Forge 13 will still not "show up for work" in Photoshop 2024 Beta. Any ideas or help will be much appreciated And please spell it out in details since I am not a professional and need it explanationed to me as if I was ten instead of sixty seven

Have you watched the video in the link above?......

Bookwormious, Wed, 01 May 2024 07:58:41 -0400
Yes, that is what I mean by writing "I have tried all this" - I have both watched the video and done what it says. And changed "false" into "true" in all the places I could find it. And in general follow every advice already given here. I hoped, when writing the post yesterday, that somebody had something extra/new, but that might not be the case, I guess :|

I can use FF 13 as a standalone, but it won't show up in the list of filters in Adobe Photoshop (Beta) even though it promised to install itself there automatically when I downloaded it ... So I don't know what to do more.

Bookwormious, Wed, 01 May 2024 08:12:00 -0400
Umm, forget about it :D
I did change all the "false" to "true" but then copy/pasted one of them into Photoshop as shown on the video, and that apparently changed the word back again. Now everything is working, though, after I changed it for the second time - and I am pretty embarrassed.
I will see myself out in a moment :)
But before I do I just want to ask if anybody knows why one has to go in and change that word?
How does it benefit Filter Forge that their customers have to change something like that to get their program to work as it is supposed to?
Now I am going :D

CFandM, Wed, 01 May 2024 08:18:17 -0400
Glad you got it working. I did just download the PS beta and tried it myself and the above video is still relevant. PS has changed but the folder structure for PS has not changed for many versions.

Ramlyn — Sun, 24 Mar 2024 05:11:56 -0400

Ramlyn, Mon, 26 Feb 2024 09:22:21 -0500
Since the last Filter Forge update I have sometimes had <class XFW::Exception> error.
I am using Filter Forge 13.005 Studio Edition

It had never happened with 13.004 Studio Edition.

The error happens using the editor, while connecting components.

GMM, Tue, 27 Feb 2024 09:03:47 -0500
Thanks for your report but we cannot reproduce this issue. Components connect fine for us. If you happen to notice a more specific pattern that always leads to the error message and can be reproduced, please send us the failing ffxml file.

Ramlyn, Thu, 29 Feb 2024 06:08:35 -0500
Thank you. Next time I will try to see if I can get more information. :)
Unfortunately, until now, when this error happened, I could not get any ffxml file, because Filter Forge wasn't responsive.

Ramlyn, Sun, 24 Mar 2024 05:11:56 -0400
Unfortunately I continue to have this error.

It happens using the editor. Not only connecting components but also in other situations. This time I was working on a Map Script.

It shuts down Filter Forge, so it is not possible to send any report by email as I usually do when I get errors.

I can only suggest to check what was changed in the editor from the previous version of Filter Forge to this, because it never happened before.

Unable to download new filters from website

robert256 — Thu, 08 Feb 2024 11:46:33 -0500

robert256, Wed, 07 Feb 2024 17:26:47 -0500
OK I used to use version 4 of the program & you would preview filters on the website and simply click on "Open in Filter Forge" and the filter would load. Now I click on it in version 13 and nothing happens!

Also I purchased the library manager and filter library but nothing has been sent...

Thanks for any help on this, Rob

Rachel Duim, Wed, 07 Feb 2024 21:15:06 -0500
You need to fix the file association (in your browser) for the file type .ffxml (filter forge filter type). I would first try reinstalling the program to see if this fixes the problem. If not and you can't figure this out, I need to know the operating system and browser you use. You can also try another browser to see if it will download filters.

I would contact support about the licenses for the library and manager.

robert256, Thu, 08 Feb 2024 11:46:33 -0500
Rachel,

Thanks for that. Reinstalled FF 13.0 and downloading of filters worked fine.

Thank you, Rob

filter foirge 13 not loading

saralu — Sat, 23 Dec 2023 10:13:36 -0500

saralu, Sat, 23 Dec 2023 10:13:36 -0500
hi
i have installed filter forge 13 onto my pc but when i try to open it, it doesn't open.
i have unintalled and re-installed twice but still no luck, i click the icon to open it, but nothing happens.
i am not very computer savvy... i just know basic stuff, if anyone knows what this problem might be and how to fix it, please help :)
thank you

Unable to change website without changing password

saurabhgayali — Thu, 21 Dec 2023 22:23:29 -0500

saurabhgayali, Thu, 21 Dec 2023 22:23:29 -0500
I am trying to change my website to new instagram handle, but the form says incorrect new password.
In the old password section it is said that fill this only if you need to change the password.

Render never finishing

patrizza — Tue, 05 Dec 2023 14:14:28 -0500

patrizza, Sat, 02 Dec 2023 17:49:32 -0500
FF13 render hangs at like 99% forever. My filter is not heavy at all and has no blur. Same happens on many filters. Some works, some just hangs. 1920x wallpaper sized pictures, FF12 has no problem with it. What might be the problem?

Rachel Duim, Sat, 02 Dec 2023 23:45:51 -0500
This has been reported in the Beta 13 part of the forum: https://filterforge.com/forum/read.php...&TID=16938

Workaround: UNCHECK Tools / Options / Interface / Reduce preview size for larger images
ReOpen the image you want to work on
Then let preview completely draw the large image without clicking Save or anything else
Then do a Save Image As

patrizza, Tue, 05 Dec 2023 14:14:28 -0500
Thank you! It works this way, I appreciate the help.

Forum Issue

Valhalla — Thu, 09 Nov 2023 08:57:46 -0500

Valhalla, Tue, 07 Nov 2023 15:35:18 -0500
Is there a post length limit? My post is getting cut in half when trying to post autohotkey UF automation code that randomizes seed, guidance, steps and inserts a random number into save as EX: kitty.png will be kitty-4325.png and so on. My post is on pastebin so you can see the length of the post I'm trying to make. Any help would be awesome.

Thanks,
-Val

Thread https://www.filterforge.com/forum/read...sage162782

GMM, Thu, 09 Nov 2023 08:57:46 -0500
I'm afraid the forum software doesn't like posts with long stretches of code. Please use services like Pastebin for that.

New Version FF not completing rendering on any filter I try

Eplurbus — Tue, 07 Nov 2023 09:56:36 -0500

Eplurbus, Wed, 27 Feb 2019 14:24:55 -0500
Hey fellow FF users, I am a newbie to FF, and I have a problem,....Since I installed the update for FF, the program will not complete any rendering. I never had this problem before the update. I use FF with Photoshop 2019 and Adobe Photoshop Elements. It gets to 99.9% complete and stops rending the filter. It does not matter the complexity of the filter or the size of the project. There is no error code(s). The host program whether PS 2019 or PSE locks up and must be restarted. FF did not do this until the update was installed.
Any ideas as to whats happening would really be appreciated. Thanks.

Eplurbus, Mon, 04 Mar 2019 13:17:21 -0500
I see no one else has had the same problem. Hmmmmmm. I have uninstalled PSP2019 and FF8.04 then re-installed them again. No changes. FF will not complete the render and switch the completed filter to PSP. If I go to processes, it does not show FF as a active process. If I go to users and close the running FF 8.04 it closes FF and transfers the completed rendered filter into PSP 2019. I give up ? what could it be? It's not PSP2019 because it does the same thing using Adobe Elements. Never did this with the last FF I was using. This only started with the newest release.

Myrrdraal, Tue, 07 Nov 2023 09:18:41 -0500
I have the same trouble...
In fact the other night I fell asleep waiting and in the morning 7+ hours later it was STILL not done....just sitting at 98/99%

Today I discovered that I CAN save renders with it, however it WILL NOT complete a render of an image greater than 1024x1024.
I mean literally 1 pixel more and it gets stuck at 99%, I was able to duplicate this effect each time I tried it. The filter being used appears to have no effect on the render, it occurs with ALL filters.

I have had the issue occur both in standalone and plugin version.

Rachel Duim, Tue, 07 Nov 2023 09:56:36 -0500
There is a workaround:
https://filterforge.com/forum/read.php...&TID=16938

Edge Detector

Ramlyn — Sun, 08 Oct 2023 01:34:42 -0400

Ramlyn, Sun, 08 Oct 2023 01:24:57 -0400
I have a question. Isn't the Edge Detector component, selecting Coarse uniformity, giving too dark results?

Ramlyn, Sun, 08 Oct 2023 01:29:04 -0400
I know I may not understand well something. But it seems to me that, if I take a common image and I use the standard settings......

Ramlyn, Sun, 08 Oct 2023 01:32:12 -0400
Uniformity = None:

Ramlyn, Sun, 08 Oct 2023 01:32:39 -0400
Uniformity = Coarse

Ramlyn, Sun, 08 Oct 2023 01:33:09 -0400
Uniformity = Fine

Ramlyn, Sun, 08 Oct 2023 01:34:42 -0400
Shouldn't be Coarse something in the middle between None and Fine?

FF disappeared from Filter menu after Photoshop 25 update

talos72 — Tue, 26 Sep 2023 15:33:24 -0400

talos72, Mon, 25 Sep 2023 17:41:40 -0400
I am sure this has come up before, but how can I fix the disappearance of FF 12 (I have the latest version) from the Filter menu after Photoshop updated to version 25 (latest)?

CFandM, Mon, 25 Sep 2023 20:22:55 -0400
Same as this. FF12

Or if you have it installed for PS 24 you could copy the PS plugin folder and put it in PS 25.

talos72, Tue, 26 Sep 2023 00:44:55 -0400
I forgot. I am not gonna remember this stuff. Thanks for the link.

CFandM, Tue, 26 Sep 2023 15:09:27 -0400

Quote
talos72 wrote: I forgot. I am not gonna remember this stuff. Thanks for the link.

Once you get that worked out then you could also copy that plugin folder and save it somewhere safe. This way if you run into this again you could take that copy of the plugin folder and copy it back to the new version of PS.

talos72, Tue, 26 Sep 2023 15:33:24 -0400
I got it working again. I really appreciate it. I bookmarked the video. :)

Help. My attempt making a backup file filled drive and I can't delete

mizzbella — Tue, 19 Sep 2023 15:07:48 -0400

mizzbella, Mon, 18 Sep 2023 16:02:46 -0400
In preparation for transitioning to Filter Forge 13, I created a backup drive. When this function stalled, I cancelled. The created partial backup file was about 50 GB, filling my C drive.
But the problem is I can't delete it, getting a "program open" message. I deleted Filter Forge 12, and still got the message. I tried copying the Roaming file to the cloud and overwriting it; it still kept the problematic file.
How do I delete that backup? I can't use my computer until I do because it hazardously filled my C: drive.
Thanks

mizzbella, Tue, 19 Sep 2023 00:00:00 -0400
Update: I was able to delete the created backup file (it was 45 GB) copying everything to Dropbox, deleting, copying back, deleting. In process I deleted Filter Forge 12, which initially appeared to be part of the problem.
Could you kindly tell me exactly what I need to copy from the backup file, and can I do this from Filter Forge 13, or do I need to reinstall Filter Forge 12? Or can I just copy everything directly and skip the backup step?

I don't want to endanger my computer by repeating the mistake and creating another 45 GB file. My c: drive doesn't have room.
My Filter Forge 12 data is under

name>appdata>roaming>filterforge12

My library is under
name>appdata>roaming>filterforge12>system>library
which is the file I tried to copy

STEPH08, Tue, 19 Sep 2023 04:52:34 -0400
I use 7zip to archive all FF folders under Roaming. The file compression (Ultra) is far superior to FF's backup feature and I am sure I really have all the filters, including the one under MyFilters.

mizzbella, Tue, 19 Sep 2023 15:07:48 -0400
Thanks. Steph, good idea. I successfully directly copied, not bothering with compression. But good idea for storage. FF's backup unusable, though possible I made some error. Anyway, it's solved, and I'm updated with my old filters migrated.

v13BETA bug when saving with 'Draft Mode' on

STEPH08 — Tue, 19 Sep 2023 11:57:22 -0400

STEPH08, Tue, 19 Sep 2023 10:22:06 -0400
v13.003 >
If you save with 'Save Image As...' when 'Draft Mode' is displayed, the rendering will stuck at 99%.

GMM, Tue, 19 Sep 2023 11:57:22 -0400
Indeed. Thanks for spotting! Forwarded it to the developers.

v13BETA (and v12) bug importing mp4

STEPH08 — Fri, 21 Jul 2023 02:00:01 -0400

STEPH08, Tue, 18 Jul 2023 12:20:14 -0400
v13BETA (and v12) bug importing mp4
-----------------------------------------------------------------
BUG for importing standard size animations of 1920x1080 (mp4), the frames are slightly 'compressed' leaving a transparent or colored band at the bottom of each frame.

I lost many hours to isolate the problem and discovered this:
simple MPEG4 videos are compatible,
modern MPEG4 videos with H264 or H265 are incompatible.

My FIX: by converting the original video source to mp4 H265 and WITHOUT HARDWARE RENDERING from graphics cards, the new video is compatible (tested with 3 different graphic cards). all my videos rendered with hardware support or coming directly from modern devices are incompatible with FF.

the issue:

GMM, Wed, 19 Jul 2023 06:17:04 -0400
STEPH08, thanks for your report. Please send the failing MP4 file to us.

STEPH08, Wed, 19 Jul 2023 08:58:01 -0400
done, check your e-mail :beer:

I made a couple of quick videos with the smartphone but the issue is present with videos from any type of camera (smartphone, drone or sport camera). I also added the fixed version of the video compatible with FF.

GMM, Thu, 20 Jul 2023 10:07:27 -0400
Thank you, issue confirmed and forwarded to the developers.

STEPH08, Fri, 21 Jul 2023 02:00:01 -0400
good! thank you
...how long until the UF beta?

Filter Forge DOES NOT UPDATE!

Marannda — Sat, 20 May 2023 04:12:29 -0400

Marannda, Tue, 25 Apr 2023 19:08:16 -0400
:evil: After contacting the support here .. I have been patiently waiting for a reply. WHY charge for a product that has so many bugs .. customer care is nonexistent and I feel like the money I have spend is truly a waste. I have shared gyazos of what happens when I try and download the program here
https://gyazo.com/daebed2c2ab91a228ff1dda031585b08
Then to top all this bullshit off .... I CAN NOT UNINSTALL IT FROM MY PC!!!
The program does not have an UNINSTALL file .. so even trying to manually remove it does not work .. deleting the launcher is the same thing .. just error after error after error its sooooooooooooooooooooooo annoying .. FILTERFORGE support please get your s*** together! or im going to cancel my subscription and opt for a refund from my financial institution!

CFandM, Wed, 26 Apr 2023 10:30:31 -0400
I do not work for FF just a user and filter author. It looks like it downloaded according to the file path at the top of the dialog on that error. That is a windows error not a FF error. To uninstall use the windows uninstaller. apps/programs that sort of thing. Use Windows file explorer to find your downloads folder and find where FF downloaded to. Then right click on the Filter Forge Exe and choose to run as administrator.
Seems that windows is not giving you permission to run that.
This is what I got from your video.

STEPH08, Wed, 26 Apr 2023 10:41:12 -0400
To me it looks like a Windows problem, maybe you don't have enough privileges, try to run the file as administrator. To easily uninstall programs from the Start Menu search the app and right-click on it, choose uninstall, but there are several other ways.

Marannda, Wed, 26 Apr 2023 17:07:01 -0400
This is what I get and im an Administrator. I been having issues with this it does not uninstall .. I've even tried using a program that removes it for you but it has no uninstall file at all..

CFandM, Wed, 26 Apr 2023 17:46:23 -0400
This is Windows issues. Change the download of your browser to the desktop so the filter forge exe downloads to the desktop. Then try installing from the exe on the desktop. That program to remove it may have messed something up. Try to copy something to that downloads folder and then open from there to see if you can still access that folder. Could also be a security program that changed the access. So doing it from the desktop is a test to see if that is the case.

Marannda, Wed, 26 Apr 2023 19:02:04 -0400
I cant even get the Installer to open I have changed the download destination to my desktop and still the same issue. I really don't know what else to do at this point I'm using windows 11 ..

Marannda, Wed, 26 Apr 2023 19:12:11 -0400
https://gyazo.com/8600497efbbaa204bc30c166bc490246

Marannda, Wed, 26 Apr 2023 19:16:04 -0400
So disabling my ANTI virus seemed to help this problem the thing is now installed and thank you for all the help!

CFandM, Wed, 26 Apr 2023 19:33:25 -0400
Good deal. I do not know what Antivirus you have but you might be able to set an exception for Filter Forge then turn the Antivirus back on. So that way when downloading filters that Antivirus does not block it again.

Marannda, Sat, 20 May 2023 04:12:29 -0400
I use PC Matic I really like it .. way better then norton

Colors washed out after reimporting into Photoshop

Alisa — Tue, 25 Apr 2023 06:27:29 -0400

Alisa, Tue, 25 Apr 2023 06:27:29 -0400
Hi,

I have recently started having a problem with applying filters in FF from PS. I open the image in FF from PS, choose filter in FF, then click "Apply" and see that the colors in PS are all different from what I saw in FF in preview. I tried all settings of Gamma correction in FF to no avail. Also tried setting the gamma in PS to the same value as the FF corrects to - still get different colors.

Here's an example.
Image before applying filter:

Preview in FF:

Image in PS after applying filter:

Any help appreciated!

Renders take forever to complete

RiverMissy — Mon, 24 Apr 2023 11:04:54 -0400

RiverMissy, Wed, 19 Apr 2023 08:24:41 -0400
I keep running into problems getting renders to finish or finish in a timely manner. My files are 4500 X 5400 and the one's I am using today are right around 1.5M. I was trying to using Cartoon Creator and it appears to be using RAM to render and not the CPU's most of the render. I have found this problem with other filters also. Anytime I am having a problem I am noticing that the filter is using RAM and not CPU's to render for a lot of the render. I have 16G of RAM and it was showing 80+% used and it did complete the render but took around 30 minutes.

If anyone can shed any light on why this is taking so long and if there is anything I can do to speed it up I will be grateful. It completed the draft files ok and in an ok amount of time but I do need the other size file for the end result. At this point I am thinking large file size is a problem in Filter Forge. Is that what other's have found? Thank you.

STEPH08, Thu, 20 Apr 2023 08:59:29 -0400
I have been working for months with 6000x4000 images and I understand your problems with some filters. You need at least 32 GB of RAM, better if 64 GB or more, and a powerful CPU, preferably with a desktop or gamer laptop.

RiverMissy, Thu, 20 Apr 2023 17:33:00 -0400

Quote
leil08 wrote: I have been working for months with 6000x4000 images and I understand your problems with some filters. You need at least 32 GB of RAM, better if 64 GB or more, and a powerful CPU, preferably with a desktop or gamer laptop.

I am working on getting a new computer and thanks for letting me know that my problems should be solved after that :) .

STEPH08, Fri, 21 Apr 2023 08:26:12 -0400
Honestly, the problem will never be solved with some filters that are obviously designed for creating textures or instagram-like images and not for big photographic/artistic images. A large amount of RAM and processor cores helps a lot, though.

RiverMissy, Fri, 21 Apr 2023 08:41:41 -0400

Quote
leil08 wrote: Honestly, the problem will never be solved with some filters that are obviously designed for creating textures or instagram-like images and not for big photographic/artistic images. A large amount of RAM and processor cores helps a lot, though.

Got it, my friend that recommended Filter Forge was not aware of the large file problems, I don't think most people are. I guess I need to try to piece my files into smaller pieces, do FF and than put them back together. That is what I have done in the past and probably need to consider that going forward.

Thank you, your feedback really helps.

emme, Fri, 21 Apr 2023 19:12:12 -0400
This generally happens when using bitmap components (like blur) on large images. The higher the radius of the bitmap component, the slower things get - so you could try to lower the radius to speed things up. Best to avoid using bitmap based components on large images if possible. More info in the user manual under Bitmap-Based Components.

RiverMissy, Sat, 22 Apr 2023 07:16:14 -0400

Quote
emme wrote: This generally happens when using bitmap components (like blur) on large images. The higher the radius of the bitmap component, the slower things get - so you could try to lower the radius to speed things up. Best to avoid using bitmap based components on large images if possible. More info in the user manual under Bitmap-Based Components.

Thank you. Where is the user manual? Does it explain what the components do? I am totally unaware there is a user manual. That could be sooooo helpful. Thank you for your suggestion and if you can tell me a bit more about the user manual that would be great.

emme, Mon, 24 Apr 2023 11:04:54 -0400

Quote
RiverMissy wrote: Thank you. Where is the user manual? Does it explain what the components do? I am totally unaware there is a user manual. That could be sooooo helpful. Thank you for your suggestion and if you can tell me a bit more about the user manual that would be great.

https://www.filterforge.com/more/help/

The documentation can also be found inside FF under Help - Filter Forge Help

Does This Look Like an AA Issue?

David Roberson — Wed, 01 Mar 2023 11:51:52 -0500

David Roberson, Tue, 28 Feb 2023 17:50:46 -0500

These blocks with the square grid of pixels show up occasionally in my filters. In this case it might be an issue with a Map Script, but I've seen it with some Math components, too. If this is a common problem, what debugging steps should I try?

SpaceRay, Wed, 01 Mar 2023 06:05:53 -0500
Sorry that I do not know what may be the source of the square grid of pixels, BUT I can help to try to find what may be wrong.

What is important is to tell what FF version you are using, if it is the same with different render resolutions.

There could be different reasons why this may be happening. What I do when something weird happens there are some things you can do

OPTION 1 - Go to the FF options and preferences and see if there is something that you have that may be the reason for this, maybe there is not antialiasing active, or is active with wrong setting, or something else

OPTION 2 - Another thing you can do is to render each one of the components of the filter and see and test if the problem appears,

1 - start testing fr om beginning of the filter components and stop when this effects you are telling may appear in the result
2 - when you find where is it, you must see what are the components involved in this result and what settings you have
3 - Try to use different settings to see if it continues or could be removed
4 - Try to use another way if possible
5 - If you can not find out yourself, Try to make it reproducible (how to get the wrong effect) and tell the steps to reach it, so we could help you here in the forum or you could upload the filter that shows the problem and see what it maybe

If the problem is inside the Math Script component, I do not have any experience in scripting, but you could try to see each of the lines of the script and see what each do, and if they could be the reason for the problem, and can test where in the script it happens. And also you can share the script here if other that know about scripting can help you

You can also put a thread in the FF scripting part of the forum for others to see with the script that gives the error

OPTION 3 - Maybe it could be a combination of things and not just only reason

OPTION 4 - If this may be a bug inside FF then you have to contact the FF team and be able that they can reproduce and see wh ere it fails.

Wish you best and that you can find what is wrong and fix it

David Roberson, Wed, 01 Mar 2023 11:51:52 -0500

Quote
SpaceRay wrote: OPTION 1 - Go to the FF options and preferences and see if there is something that you have that may be the reason for this, maybe there is not antialiasing active, or is active with wrong setting, or something else

Yes. Since I wondered about antialiasing I did check those settings and increased the level a bit.

Quote
SpaceRay wrote: OPTION 2 - Another thing you can do is to render each one of the components of the filter and see and test if the problem appears,

I also looked at each component, though in my case I went in reverse order by following the input chain. I have tracked it down to a map script each time, though the grid of pixels seems to come and go. I repeated this a few times to confirm that the problem is intermittent and occurs when a noise map script is fed into a distortion map script. Individually, these scripts have no issues. I think the problem relates to the increase of noise during distortion.

Quote
SpaceRay wrote: 3 - Try to use different settings to see if it continues or could be removed

I have a pretty complex graph with multiple copies of four or five map scripts, and they are all essential, settings included. So, changing the settings isn't acceptable in practice. If I have time today, I will see if a simpler graph can reproduce the problem with a minimum number of components. I'll post that if it works.

Thanks for your advice!

FF11 librarian does not open anymore -- requires registration

Ilmeni — Fri, 24 Feb 2023 05:24:17 -0500

Ilmeni, Sun, 27 Feb 2022 16:55:38 -0500
Hi!

I'm using Filter Forge 11 Professional. Librarian worked fine last time I used it. But (apparently after the last update of Filter Forge to version 11.005) Librarian doesn't open properly anymore. Instead, it requires registration.

This ist the message I get: "Your Filter Forge copy is not registered. To use Filter Forge Librarian, please run the latest Filter Forge version and inter your license key in the Help menu." (see attached image)

After I enter "OK" librarian closes. When I open Filter Forge 11 after that it is indeed not registered and i have to reenter name and license key. (see second image below)

After that, if I try to "enter license key" in the help menu i get the message, that Filter Forge is already registered alright.

If I close it and try Librarian again, it apparently unregisters Filter Forge once more. I tried to restart computer, doesn't help.

Please advise!

Ilmeni, Sun, 27 Feb 2022 16:56:20 -0500
Here is the second image:

GMM, Mon, 28 Feb 2022 05:47:56 -0500
We believe this issue has been fixed. Please redownload and reinstall the latest Filter Forge 11, register with your license info, close Filter Forge, then redownload and reinstall Librarian 11 using your download link.

Ilmeni, Mon, 28 Feb 2022 06:20:25 -0500
Thank you very much, it worked! :)
I noticed there are very recent filters included now. Does it make sense to redownload Librarian 11 from time to time? Thank you.

GMM, Tue, 01 Mar 2022 05:57:16 -0500
Librarian only contains filters that are available in the filter library, and we haven't seen many new filters recently. If no filters are submitted to the library, there is nothing new to include in the Librarian package.

Ilmeni, Tue, 01 Mar 2022 09:33:25 -0500
Thank you very much! That helps. :)

Demigod420x, Thu, 16 Feb 2023 08:37:22 -0500
Hi I just bought Filter Forge Librarian 12 after enjoying Filter Forge 12 I decided on buying the big package $200 ish pack. I received the download link email & downloaded the app. I opened it up with no problem I then added a bunch of filters to my Filter Forge 12. I then decided to look at options as I always do in all applications I own & when I clicked file location just to see where file locations where but I didn't change anything except I clicked on Filter Forge Librarian 1,2 etc..in the options screen just to see why it was in options because I don't have that version even thought I would like to buy it if it was a option to me but I digress. I went back to Filter Forge Librarian 12 after looking threw the options & exited the app when I was done but. As soon as I opened it back up it said as a error "Failed to load the filter Library" can anyone please help me fix this or do I need to return it for a refund because $200 is a lot for a filter app to not work anymore! :evil:
PS: I don't go on forums often I am a busy man so if this is not where I post a question I am sorry in advance :)

GMM, Mon, 20 Feb 2023 10:59:15 -0500

Quote
Demigod420x wrote: it said as a error "Failed to load the filter Library"

Looks like you need to reinstall Librarian 12 using your personal download link.

Demigod420x, Fri, 24 Feb 2023 05:24:17 -0500
"Looks like you need to reinstall Librarian 12 using your personal download link"

Hi I did that in fact I did that and I then copied the Library folder fr om C:\ProgramData\Filter Forge Librarian 12\Library to my desktop. After I deleted the Library folder in Filter Forge Librarian 12 I then created a new folder wh ere the old one was & called it Library I loaded up the app pointed the folder directory to Librarian 12 and still nothing. :cry:

Filter download fail 12.005 windows

westdale — Thu, 12 Jan 2023 19:02:27 -0500

westdale, Thu, 12 Jan 2023 19:02:27 -0500
Prompted by my V12 FF to update; did so to 12.005 and now it seems that download of V12, V11 filters causes an error "get-filter-xml(16325,1) failed" and similar with different parameters - managed to download a V9 filter.
Any ideas ? I notice this was a transient error about a year ago

Edit - rebooted PC 'just in case' and downloaded a V5 filter but failed again on a V12 one.

Edit 2 uninstalled V10 V11 of FF in case of conflict. Downloaded Cubes (early release) but failed on Leafy V12

edit 3 12 hours later Leafy V12 download fine...... my earlier attempts were around midnight UK time -- was some sort of update to database / website happening?

Preset Window doesn't display new presets

PixelStar — Tue, 06 Dec 2022 06:57:46 -0500

PixelStar, Mon, 05 Dec 2022 16:57:19 -0500
[CODE][CODE][/CODE][/CODE]When I attempt to add a new preset in FF 11 it shows that it added the preset, yet the scroll bar stops and it does not display the new preset in the window. This is after I have added a number of presets to fill up the window. You can see that it added the preset (the number of presets changes at the top) however, again, the scroll bar stops and you cannot see the new preset nor access it.

A few facts:
* I am using this as a standalone application vs a plug-in in this case.
* Windows 10 Pro on a desktop machine; Core i7-5820K CPU, NVIDIA GeForce GTX 1070 Ti, 32 gb Ram
* this issue seems to not be an issue on my laptop (Windows 10 Home), but does happen from time to time, but not as often.

I thought maybe this was due to a large amount of presets, however, I tried it with a filter with only around 40 presets, and it did the same.

Why does the window scroll bar stop working? Is there a set number of presets it can use? I have been using FF since FF2 and havent encountered this before.

Any ideas? or has anyone else experienced this? :?: :cry:

PixelStar, Mon, 05 Dec 2022 17:00:27 -0500
Here is the other screenshot

PixelStar, Mon, 05 Dec 2022 17:01:13 -0500
Accidentally uploaded screenshot again :D

GMM, Tue, 06 Dec 2022 06:57:46 -0500
Thanks for your report, I forwarded it to the developers.

As a workaround, drag the separator between the preset area and the preview: the preset list will refresh and display the newly-added presets.

Rotate error?

Ramlyn — Mon, 21 Nov 2022 06:53:55 -0500

Ramlyn, Tue, 08 Nov 2022 03:56:51 -0500
I get a strange result using Rotate in combination with Free Gradient.

It happens with Filter Forge 11 when, in the Free Gradient, Start X is 0.5, Start Y is 0.5, End X is 0 or 1, End Y is 0.5, Type Angular.

Ramlyn, Tue, 08 Nov 2022 03:57:23 -0500
I attach the filter.

SpaceRay, Sun, 20 Nov 2022 02:35:26 -0500
Have you tested if this error still appears in FF 2 beta?

Ramlyn, Sun, 20 Nov 2022 05:17:20 -0500
No. I didn't. ;)

SpaceRay, Mon, 21 Nov 2022 06:53:55 -0500

Quote
SpaceRay wrote: Have you tested if this error still appears in FF 2 beta?

Sorry I mean really FF 12 Beta , there was missing the 1

Quote
Ramlyn wrote: No. I didn't.

You should try the latest beta 12.03 and see if this is also happens there and so the FF team can find a possible solution if it is still happening the same

Affinity 2.0.0 Filter Forge fails to launch

Elynde — Sun, 13 Nov 2022 14:44:21 -0500

Elynde, Wed, 09 Nov 2022 15:26:23 -0500
Just purchased the new Affinity version 2.0.0 suite and tried to use the Filter Forge plugin to no avail. I tried both Filter Forge 11 and the 12 beta. In both instances, the program gives the error in the screen cap. Any recommendations?

Adam P, Fri, 11 Nov 2022 04:15:28 -0500
I have exactly the same problem. Filter Forge wrote in the technical requirements note: Affinity Photo 1.8, 1.10.4 and NEWER! - But Affinity 2.0 not supported, what I have to do? Will there be an update? When installing versions 11 and 12, it does not detect Affinity Photo 2.0 Only standalone version. Will there be an update? Why is no one answering me, on messenger or e-mail?

CFandM, Fri, 11 Nov 2022 09:16:50 -0500
You get this when Filter Forge is not compatible with that version of whatever application you are installing it into. This is also the error you get with photoshop. I have made a video of how to fix this error in photoshop. So I would guess that if you find where the plug-in is installed in Affinity and change the needed config file then it would work. There is no guarantee since I do not have Affinity Photo to try it out and see if it does or not.

Here is the video for photoshop so skip through until you see me open photoshop in the video the second time. Around the 3 minute mark.
Installing Filter Forge

GMM, Fri, 11 Nov 2022 11:25:59 -0500

Quote
Adam P wrote: Filter Forge wrote in the technical requirements note: Affinity Photo 1.8, 1.10.4 and NEWER!

The system requirements are Affinity Photo 1.8, 1.10.4, and 1.11:
https://filterforge.com/download/

We are working to add a compatible plugin for Affinity 2.

Quote
Adam P wrote: Why is no one answering me, on messenger

We only provide support via the contact form.

Adam P, Sun, 13 Nov 2022 08:26:26 -0500

Quote
Oto wideo do Photoshopa, więc przejdź dalej, aż zobaczysz, jak otwieram Photoshopa w filmie po raz drugi. Około 3 minuty.

Yes! Yes! It works on Affinity Photo 2.0! Thank You Very Much :) :) :)

Elynde, Sun, 13 Nov 2022 14:44:21 -0500
Yes! I can also confirm this very simple fix works in Affinity Photo 2.0.

Draft Mode notice does not hide

STEPH08 — Tue, 01 Nov 2022 09:59:01 -0400

STEPH08, Tue, 01 Nov 2022 09:59:01 -0400
Preview Size -> Hide Notice is selected but the Draft Mode notice is permanent.
>I am on v12, I don't know if it was the same before, I have only recently been using FF regularly<

Temporary files location

STEPH08 — Tue, 01 Nov 2022 08:18:28 -0400

STEPH08, Tue, 01 Nov 2022 08:18:28 -0400
I can't change the Temp folder easily. I must edit the Options.xml file.

>I like to place the Temp folders of the applications I often use under a RAM disk, to preserve the SSD disk which has a much more limited lifespan compared to a Hard Disk<

The problem with the xml edit is that as soon as I change something in the options or update the application, the default Temp location is reset (FF v12)

I hope you can fix. THX

Filters applying offset

nervelli — Wed, 24 Aug 2022 05:30:05 -0400

nervelli, Sat, 20 Aug 2022 20:26:18 -0400
Whenever I try to apply a filter to a selected area, it applies it to an offset area in the shape of the selection. The preview shows it offset even though there isn't that much room on the canvas, and when applied it is still offset but runs off of the edge of the canvas. I am using affinisty photo and in this example only have one layer that the image is on.

CFandM, Sun, 21 Aug 2022 06:36:07 -0400
What filter is it?. I know it just can't remember the name. Could be a setting in the filter or one of the components need a setting changed.
Sometimes when you use a certain filter with the selection that is not designed with a selection in mind things get kinda weird without some
editor intervention. ie you would need to alter the filter for your own needs.

Update...Found the filter and I have no issues with it. But I am using Photoshop with filter forge.

nervelli, Sun, 21 Aug 2022 08:56:37 -0400
It happens with any filter, I just used that one for the example because it was easier to see where it was applying it.

I checked in photoshop and in affinity with other files, and it does seem to only be happening with files saved as affinity files. It also seems to offset it more if is use Select>Alpha Range as opposed to just using a selection brush (still offsets, just not as much).

I guess I will just use other file types for now, but I'm still curious why affinity files and filter forge would interact in this way.

CFandM, Sun, 21 Aug 2022 11:40:41 -0400
That is odd. I am not an affinity user so I can't answer that one. I think there was other affinity users here at one time so maybe they will see this and weigh in..

GMM, Wed, 24 Aug 2022 05:30:05 -0400
nervelli, welcome to the forums and thanks for your report.

We forwarded your issue to the Affinity developers and surprisingly received a quick reply:

Quote
We believe this may be caused by a document that uses Bleed. We have tested this using Affinity Designer to create a document with Bleed which we have then opened with Affinity Photo. Creating a selection leads to the filter appearing vastly offset. Can you please get back to your customer and ask them if they have Bleed set on a document. If not, is it possible to get a copy of their document so we can investigate further?

Quote

We believe this may be caused by a document that uses Bleed. We have tested this using Affinity Designer to create a document with Bleed which we have then opened with Affinity Photo. Creating a selection leads to the filter appearing vastly offset. Can you please get back to your customer and ask them if they have Bleed set on a document. If not, is it possible to get a copy of their document so we can investigate further?

I have no idea what Bleed is :) If you have it enabled, please turn it off; if you don't - please send your document to the support team.

Filerforge 11 and Windows 7 64 bit

yveslafont — Fri, 24 Jun 2022 13:44:05 -0400

yveslafont, Wed, 02 Mar 2022 11:46:21 -0500
Hello,
I just update my working FilterForge 10 to the 11, under Win 7 64 bit, and the software don't run
No error message, just nothing happen.
Can i have some help about ?

Greetings,

Yves

CFandM, Thu, 03 Mar 2022 05:55:29 -0500
Would help to know how you are running it. As a plugin with a graphics app or as a stand-alone program. What type of computer as in specs.

yveslafont, Thu, 03 Mar 2022 10:27:27 -0500
I use it as a stand-alone program.
My computer run on Windows 7 pro sp1 64 bit, intel i5, 8go ram, system on a ssd, and data on hd
Filterforge 10 run pefect...

Rachel Duim, Thu, 03 Mar 2022 15:36:06 -0500
Sadly... my 2 cents. Windows 7 is not supported for FF 11 (see the download page). This is not surprising given that MS no longer supports Windows 7.

CFandM, Thu, 03 Mar 2022 16:15:14 -0500
I would say go back to version 10 and see if that works....Then install 11 with the install rather then the upgrade path.
See if 11 work that way.

yveslafont, Fri, 04 Mar 2022 02:53:15 -0500
Thank you very much for your fast and precise replies.
FF10 was still installed, when i installed FF11.
I didn't use the upgrade path in FF10, but the direct download from the website.
So, that is pity, i continue for now working with FF10.

Greetings,

Yves

GuyLau, Fri, 24 Jun 2022 13:44:05 -0400
I have exactly the same problem. (New v.11 installed separately).

Just won't start with Win 7 Ultimate SP1 x64 !
[Intel Core2Quad Q9550 2.83GHz - 8Go RAM - OS: SSD - Data: X-HDD]
(One of my Multimedia stations which works very well)
- Standalone: Nothing happens - No message.
- Plugin: Freeze Photoshop (64 Bit) - No message.

... and Filter Forge 10.008 Pro works well ;)

Which component (Win 10) is missing ?
Filter Forge (.exe) has increased from 95MB (v.10) to 205MB (v.11) !

What's the trick ? :?:

Key code

Kraellin — Tue, 14 Jun 2022 17:23:15 -0400

Kraellin, Sat, 11 Jun 2022 16:47:40 -0400
Hi guys, i’m having a very hard time getting my perm code for unlocking and using ff 11. When i use the program to try and get it, it wont connect with the server. Using another method said that if my isp was at&t, that i could write you but you couldn’t write me. I think you probably have my email on file. I believe i’m entitled to two, free codes for the pro version. Could someone send those to me, please? This is getting frustrating. I’d like to be able to use 11. It’s already installed; it’s just my free trial has run out. If you can’t email me, then let me know here and we can try and work something out, even if it has to be normal mail.

Craig

traycaa, Mon, 13 Jun 2022 03:46:39 -0400
Hey Kraellin,

It's better you email support@filterforge.com. They are currently more responsive with the support emails :)

GMM, Tue, 14 Jun 2022 08:48:55 -0400
Craig, the support team has received and replied to your email. Please check your inbox and spam folders.

Also, it's not about your ISP, it's about the email service provider. Email accounts in the @att.net, @bellsouth.net and other domains belonging to the AT&T email service don't receive mail from filterforge.com.

Kraellin, Tue, 14 Jun 2022 16:56:09 -0400
Hi GMM,

I found an email just now in my junk folder from you guys. It was a response from support with a link to go to to submit my request. I submitted it and it said i’d receive another email with the code. We’ll see if it comes through. Thanks!

Why has at&t banned you? Because of the whole ukraine thing? That would be ludicrous!

Hope you guys are doing well

Kraellin, Tue, 14 Jun 2022 17:23:15 -0400
Hi GMM,

I got the code! Thank you! You guys have always given great help and support!

Now i’m off to find and shoot the idiot that thinks they shld control what i consider spam/junk. Bloody idiots!

Craig

Not working in Photoshop 2022

Jtol — Wed, 01 Jun 2022 22:26:53 -0400

Jtol, Sat, 28 May 2022 02:09:25 -0400
I downloaded today the latest FFversion and reinstalled including the PS plugin but it does not work. lister in the filters, but greyed out.

GMM, Tue, 31 May 2022 06:36:03 -0400
Jtol, welcome to the forums!

You cannot apply a filter to a grayscale image nor to a smart object.
Please open an image in Photoshop and select Image > Mode > RGB color to be able to apply a filter.

You can also use FF in the standalone mode without Photoshop.

Jtol, Wed, 01 Jun 2022 22:26:53 -0400
Thank you, it worked.

Can't Download Filters

Peachy Carnehan — Tue, 31 May 2022 06:34:29 -0400

Peachy Carnehan, Fri, 27 May 2022 16:39:28 -0400
Just purchased the Pro version of Filter Forge 11 and am unable to download filters. When I attempt to do so I am transferred to a web page informing me that Filter Forge is not installed or I need to allow cookies. I click to allow cookies and am transferred back to the original filter page. When I click the filter download button again, nothing happens.

I have tried this in Firefox, Edge, and Google with the same non-results. I have also tried it with Filter Forge open via the most current version of Photoshop and with Filter Forge open in stand-alone mode - with no effect.

Additionally, I have specifically allowed for cookies from filterforge.com with no effect either.

Any suggestions?

CFandM, Fri, 27 May 2022 18:24:17 -0400
Windows might not be associating the files with filter forge. Its a windows thing. A couple of things to check. Using google make sure that the checkbox is checked to allow filterforge.com to open links....

CFandM, Fri, 27 May 2022 18:25:12 -0400
Check your windows apps associations to see if ffxml is listed.

CFandM, Fri, 27 May 2022 18:46:21 -0400
You can also give the built-in browser a try. In the main windows menu of filter forge go to tools-options then in the dialog that pops up go to the online tab. Select to use the build-in library browser and then hit OK.

CFandM, Fri, 27 May 2022 18:49:12 -0400
Then at the top right click on the text in the red circle.

GMM, Tue, 31 May 2022 06:34:29 -0400

Quote
Peachy Carnehan wrote: When I click the filter download button again, nothing happens.

A possible cause is a broken FF installation. Please redownload and reinstall FF from the Download page.