William Turner
Posts: 33
|
I have a largish file (50mb or so jpg) which I'm trying to render using the 'Another Watercolor' filter (which I must say is a brilliant filter by Northernshadow).
It takes around 3 hours to do and just when you think its completed the app quits and I get an error feedback box. I've had this 3 times now and I send the errors to wherever they go but have never had a reply as yet.
Now I've used this filter before on a slightly bigger file which was 24269 pixels wide and it worked well and without a problem.
I'm just trying to find out why I should be getting this error with this file. I've changed the size a little and tried that but got the same problem and I'm now trying a tiff save rather than jpg. But I'm looking for any obvious workaround as I dont have an unlimited amount of time waiting for this thing to work. I have a deadline to meet !!!
Any help appreciated.
|
Posted: May 26, 2011 7:16 am |
Details
E-Mail
|
GMM
Moderator
Filter Forge, Inc
Posts: 3491
|
Quote |
---|
William Turner wrote:
the app quits and I get an error feedback box. |
If you agreed to generate a bug report and send it to the support team as the box suggested, you could receive a quicker solution. For now, we'll need to guess the error message, your FF version, whether you're running in the plugin or standalone mode, etc etc.
|
Posted: May 26, 2011 7:33 am |
Details
E-Mail
|
William Turner
Posts: 33
|
I've never yet got a reply which is exactly why I'm posting this. I only ever use FF as a standalone.
|
Posted: May 26, 2011 7:49 am |
Details
E-Mail
|
William Turner
Posts: 33
|
It finally completed the rendering this time, so 4th time lucky. It took 5 hours and I saved it as a tiff file, so I dont know if that made any difference. The file size at the end was 144MB.
Any ideas as to why I should have had any issue would be appreciated so I can make sure it doesnt happen again. I know this is like asking how long a piece of string is but perhaps there are known issues when rendering largish files.
|
Posted: May 26, 2011 8:47 am |
Details
E-Mail
|
GMM
Moderator
Filter Forge, Inc
Posts: 3491
|
We've rendered some 65k x 65k images with no errors. One of the reasons could be a hardware issue, perhaps overheating or faulty RAM.
|
Posted: May 27, 2011 4:19 am |
Details
E-Mail
|
William Turner
Posts: 33
|
Yes, I think its more likely to be a hardware issue
|
Posted: May 27, 2011 1:57 pm |
Details
E-Mail
|
William Turner
Posts: 33
|
Yet again, this time after two 10 hour renders, FF just quit. This is totally unacceptable and I really need to know what the problem is here. However, FF never respond to the bug reports I send. If nothing is done this time I shall make sure my position is felt quite clearly on this forum. This is simply appalling customer support. I like the software and find it works on small files but for large ones the app, takes 98% of CPU and takes hours on end to render and often quits before saving.
Here is the bug report if this means anything to anyone. I doubt whether I'll get a response from my bug report. If this happens again, I shall ask for a return of my money as I don't have the time to deal with this.
Operating system: Windows XP (5.1 build 2600) Service Pack 2
Physical memory: 2047 MB
Number of processors: 2, available: 2
Processor info: Intel® Pentium® D CPU 3.40GHz, ~3392 MHz
Filter Forge x86-SSE2 2.009.19400.34466 Release-SSE2, January 14, 2011 07:43 [07/06/2011 18:41:57 GMT Daylight Time]
[Controls::Control] Exception occured while processing window message 0x00000111(WM_COMMAND) (0x00003F08 0x00320234) for window 006501CA/006501CA, control: <class Controls::Panel>@01FDE4B8.
[Controls::Control] Exception occured while processing window message 0x00000202(WM_LBUTTONUP) (0x00000000 0x000F002F) for window 00320234/00320234, control: <class Controls::PushButton>@01FF3F08.
Exception caught at thread 00001040 'Application':
<class XFW::Kernel::StdException> bad allocation
<unknown file>(0) : <unknown function>()+0 at 0081AB84 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00818E15 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006C02FB in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 005628E4 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006C002C in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00A67B83 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 004713D0 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 005028E7 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0056B6C1 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0057608D in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00577EE6 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0056CEA2 in Filter Forge x86-SSE2.exe
<unknown file>(0) : GetDC()+109 at 7E418734 in C:\WINDOWS\system32\user32.dll
<unknown file>(0) : GetParent()+364 at 7E41B89B in C:\WINDOWS\system32\user32.dll
<unknown file>(0) : IsWindowUnicode()+161 at 7E41C63F in C:\WINDOWS\system32\user32.dll
<unknown file>(0) : <unknown function>()+0 at 0057608D in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00577EE6 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00560343 in Filter Forge x86-SSE2.exe
<unknown file>(0) : GetDC()+109 at 7E418734 in C:\WINDOWS\system32\user32.dll
<unknown file>(0) : GetWindowLongW()+295 at 7E4189CD in C:\WINDOWS\system32\user32.dll
<unknown file>(0) : DispatchMessageW()+15 at 7E418A10 in C:\WINDOWS\system32\user32.dll
<unknown file>(0) : <unknown function>()+0 at 0081D3BC in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00573847 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 004657E5 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00828DDF in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00A73A7B in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00827BE0 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00828B9F in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0082F144 in Filter Forge x86-SSE2.exe
<unknown file>(0) : RegisterWaitForInputIdle()+73 at 7C816FD7 in C:\WINDOWS\system32\kernel32.dll
<unknown file>(0) : ValidateLocale()+688 at 7C839AA8 in C:\WINDOWS\system32\kernel32.dll
<unknown file>(0) : RegisterWaitForInputIdle()+82 at 7C816FE0 in C:\WINDOWS\system32\kernel32.dll
CONTEXT_CONTROL: CS:EIP 001B:7C812A5B, SS:ESP 0023:00128D74, EBP 00128DC8, FLAGS 00000206
CONTEXT_INTEGER: EAX 00128D78, EBX 04CF5B48, ECX 00000000, EDX 00128E1C, ESI 00128E08, EDI 00128E08
CONTEXT_SEGMENTS: DS 0023, ES 0023, FS 003B, GS 0000
|
Posted: June 7, 2011 12:50 pm |
Details
E-Mail
|
William Turner
Posts: 33
|
I've decided to give it one last shot on my Mac using V3 and see what happens. If it quits this time, I shall be back spitting blood. I'm used to dealing with gigabyte sized files in my Photoshop CS5 everyday and have never had issues with any other software. I'm using this in standalone mode and if it really can't deal with files this size (around 100MB jpegs) then someone really needs to do something about it.
|
Posted: June 7, 2011 12:57 pm |
Details
E-Mail
|
GMM
Moderator
Filter Forge, Inc
Posts: 3491
|
Quote |
---|
William Turner wrote:
Filter Forge x86-SSE2 2.009 |
William, we do not support obsolete program versions. Please update your Filter Forge to 2.010.
|
Posted: June 8, 2011 3:27 am |
Details
E-Mail
|
William Turner
Posts: 33
|
Oh really ? You just abandon your own software do you ? Well, how nice to know.
Why don't I ever get a reply when I send the innumerable bug reports after your 'obsolete' software crashes yet again ?
I'm now going to update to your latest version and if it crashes again, I'll be asking for my money back because this is quite pathetic.
I've wasted days of my time using your 'obsolete' software.
|
Posted: June 9, 2011 2:00 am |
Details
E-Mail
|
William Turner
Posts: 33
|
I had to quit my Mac using V3 becuase it was taking so long. It was a third way through a file and had already taken a day and a half. And its an iMac with dual-core Intel chips. Is V3 'obsolete'. This software really is hopeless for big files using the 'Another Watercolor' filter and I'd advise anyone not to try on files of 50MB or bigger (jpeg).
Perhaps this whole thing could have been solved earlier if your support team (sic) was as efficient replying to bug reports as your sales team (sic) were at emailing me to offer sales discounts before I bought the software.
|
Posted: June 9, 2011 2:05 am |
Details
E-Mail
|
William Turner
Posts: 33
|
Well the good news is that since I upgraded to the latest V2 on my PC, I havent had a reoccurence of my problems. I still havent a reply to my bug reports however.
|
Posted: June 24, 2011 6:45 am |
Details
E-Mail
|