What is the relation between the resolution size and the FF filter ?

Hello,

As there are already some threads about the problems rendering in resolutions
highers than 5000 x 5000, 8000 x 8000 or 15.000 x 15.000 and more.

I now I wonder if perhaps there some strange relation between filter forge filters and the high resolutions, Does it happen the same with ALL the filters or the errors could happen depending on the filter you use.

What is the relation between the resolution size and the FF filter ? (If there is any)

Does it happen the same error in both the standalone AND in the plugin version ?

Could it be the rendering setting that could be wrong put and that is why the error happens?

Or Probably could it be an Hardware problem ?

In the features is put

Quote
Huge Resolutions The biggest one we tried was 65536x65536 pixels – and it worked! Granted, it took hours, but anyway! Furthermore, the interface remained responsive – we were able to zoom and pan the preview while rendering that monstrosity

So I think that the FF team has tried to use this really huge and monstruosity resolution and it worked, they must be sure that it really worked, so perhaps the problem is NOT with Filter Forge itself, perhaps and probably the problem could come from the relation between the image and the filter used.

What filter was used to reach 65536 x 65536 pixels ?

Was this tried with one filter only ? Or with a few of them ? Or more ?

Was this filter a FF generated image or was it a Image based filter that depends on the image loaded ?

I suposse that is not the same that the filter does NOT depend on a image loaded and render the image from inside FF so is all depending on the engine of FF, than the filter that depends on an external image loaded. Or even more than one external images as now in FF 3.0 you can multiple image input on the filter.

Quote

CFandM wrote: I tried some filters of the list below and have had no issues with them....Tried at 9000x9000,15000x15000 and 20000x20000.....I have the AA settings set to render "All Pixels" 25 samples.....I also turn my ram usage to 40% so I can still do other things while FF renders.... Also I am on a slow machine by todays standards....Only an Intel Dual core OCed at 3gig.... Concrete Plastastic Woeful Wood Decay Energy Filtration Ink Ghost Lost Letter Grass Muscle Fiber Crackles Lake Bed Odd Rock Rock Salt Cyber Circuits

If you CFandM with your hardware have been able to render at this resolutions and choosing some different filters and have not had any problem at all, I even more wonder and want to discover the mistery of what is happening.

On most of the images I have tried to use with high resolutions (more than 5000 x 5000)on many filters nearly 90% of them gave me errors while rendering, normally when reaching the middle or near the end of the render. And I thought that with FF 3.0 would not happen as it happened with FF 2.0, but I was wrong, it happens the same.

Since a few months ago I have a new computer that has a Intel Quad Core i7 2600K 3.5Gz Sandybridge with Z68 chipset and 16 GB DD3 RAM using an SSD drive with the WIndows 7 64 bit OS.

Quote
GMM wrote: joBox, your anger is useless unless you provide more details. What is your OS, it is 32-bit or 64-bit, do you use Filter Forge in the plugin mode (if yes - under which host app) and – the most important – what is the exact error message you get.

Yes, you are totally right, perhaps the important key to solving the mistery and fixing the possible bugs is to know EXACTLY WHEN AND HOW the error happens.

We must take not of every single error and make a FF bug report of each one, and note also which filter has been used and if it was in standalone or plugin mode, and under which host.

So having all this important information the FF team could really find and know what is happening and could be able to reproduce the errors themselves and be able to find the solution.

So thinking on all these things I think that I will make some tests and will take good note of any error I find and put it here in the forum to help the FF team.

I will put the bug reports in this other thread here

Please help also with your own bug reports to help the FF team and ourselves to solve and fix this

Thanks very much

Also, when testing Filter Forge stability on huge resolutions, we'd appreciate if you could confirm or disprove that the plugin mode (which is thought to be inherently less reliable) is in fact more stable than the standalone application.

Quote
GMM wrote: when testing Filter Forge stability on huge resolutions, we'd appreciate if you could confirm or disprove that the plugin mode (which is thought to be inherently less reliable) is in fact more stable than the standalone application.

I have been making at least 30 tests with different resolutions, and even up to 10.000 x 10.000 pixels and 99% of the times it fails in standalone mode, BUT when using it as a plug-in mode inside Photoshop, from 30 test, only failed 2 of them.

So I can confirm that surely in my case the plugin version is hugely much stable and better than the standalone.

Perhaps also helps that I have 16 GB RAM, and so there is more room and space for applications to live toghether and FF that only uses up to 1,5 GB can be more stable as a plugin