64-bit progress? 32-bit Photoshop didn't do it or me anymore...

I was wondering how work on the 64-bit version is going.

I purchased FF, but got it at the same time I got CS4. I quickly was running out of memory in Photoshop-32, and had to move to 64-bit to work with larger images. Now I can work with photoshop using 16GB ofmemory and not worry about running out of memory -- but (correct me if I am wrong) -- I can't use Filterforge. PS-64 doesn't seem to read any of the 32-bit filters. (a shame they couldn't have implemented 32-bit compatibility). Even though it's slower for most things, I could have tolerated a 32-bit interface to Filterforge. But given that it doesn't work at all is a downer.

Is it that complicated to recompile for 64-bits? Sure is nice to work on 5000x15000 images all in memory...with scores of layers and full history and not be touching disk, let alone running out of memory.

Astera.
I am having the same problem. FF will only run with the 32 bit version of PS as a Filter Plug-in..On a XP64 Machine with 16 gigs.
PS64 doesn't even recognize it. I even tried Manually dropping it in the 64 and tried redirecting the Config file. No Luck.

Guess we'll have to see what FF2 brings

True, But the rest of our program does and it would be nice to be able to use it with the rest of our software. I am not complaining right now as when the current Filter Forge was created I think 64 bit processing was just a pipe dream. I am just hoping the FF2 will at least be recognized in PS4 64 as a Plugin and usable from within the program.

Quote
Astara Athene wrote: Is it that complicated to recompile for 64-bits?

Unfortunately, it seems to be so. We're using a very old Adobe Photoshop SDK (for host compatibility and legal reasons), and recompiling it for 64-bitness may turn out to be problematic or impossible.

Most likely, the 64-bit plugin mode won't make it into the release of Filter Forge 2.0 - but we may release it in a free update after that.

I don't care if it does or does not use more than 1.5G -- I just want it to seamlessly integrate in the menu of PS-64bit like "Noise Ninja" (which has a 64-bit version).

For reasons that I don't understand -- PS-64bit won't recognize 32-bit plugins. I'd call it a bug, but Adobe's $(%! doesn't smell, so of course it's a developer problem.

If it doesn't integrate with PS-64bit, then it isn't 64bit compatible. Plain and simple. I know 32-bit apps run on x64 -- but just like 32-bit extensions can't be used with a 64-bit Firefox, I'd usually prefer a 64bit Firefox as I don't use the 32-bit extensions that often. I *DO* run out of cache memory in Firefox due to process size limitations.

I don't need FilterForge to run in 64-bit mode so much as I need it to be callable from 64-bit Photoshop.

I can't speak of how fast it can convert a 70Mpixel image, but doing wavelet based noise removal takes about 10-20 seconds I don't know if it goes through a tmp file or not, but my disks are pretty fast. For smaller images, 5-10 seconds is typical. The speed of 64bits is noticeable faster than 32bits -- especially when Win7 is very good about keeping things in memory.

For what it's worth, as of January, 2010, Valve's monthly survey focusing on what hardware their customers were using showed Windows 7 64-bit running 2nd behind WinXP-32.

Code
The breakdown (in percentages):                   32-bit      64-bit      Combined(OS)                   ------      ------      ------------ Win XP      42.15       0.63      42.78 Vista          19.09       8.82      27.91 Win 7**       9.03      19.09      28.53                    ------      ------       Cmbd bts   70.27      28.54

** - Win7 is 5 months post release, and, as I asserted at release, most users
will opt for 64-bits on upgrade as they were already maxed out and 64-bit Win7
is in the same package as 32bit version (no longer costs extra).

I would be that a year from now, Win7-64 will have over 50% of that
market