Comments on: Filters Not Applied When The Image Size is Big

By: chris

chris — Wed, 26 Jan 2011 18:27:38 +0000

I ran into this error when trying to print as well. I got around it by converting my image to a bitmap before printing.

By: Rashmi

Rashmi — Tue, 06 Jul 2010 11:01:23 +0000

i was getting the same prob but after seeing the soln. i got how to solve thanks

By: ginj

ginj — Tue, 25 Aug 2009 05:35:51 +0000

I got this error when testing a print function in my app. The frame doesn’t come close to those sizes but the error says 2 display objects exceed 8000 pixels in some direction. No stray bits in the frame. No idea. I do use the URLLoader, but no actual filters as far as I’m aware (just printing text). Dunno..

By: Andrei Ionescu

Andrei Ionescu — Mon, 17 Aug 2009 20:38:47 +0000

Thanks Matteo! It is correct what you said.

By: matteo sisti sette

matteo sisti sette — Mon, 17 Aug 2009 20:35:34 +0000

Any undocumented behaviour is ALWAYS a bug, by definition. At the very least, it is a bug in documentation.
Any limitation, however small, however restricting, is acceptable, but no limitation is acceptable, however high the limit, if you have to find it out by trial and error.

By: Tomislav Pokrajcic

Tomislav Pokrajcic — Wed, 04 Mar 2009 14:35:19 +0000

Yeah, you’re right. There are many undocumented “features” around. I couldn’t find anything on Adobe sites regarding effects. They mention BitmapData size limits, but there are workarounds for that.
I have found limitations for decoders that are called from Loader class too. PNG decoder doesn’t work for me over 4095×4095, and JPEG decoder behaves weird over 8191×8191.
For effects, you can try Pixelbender. It works pretty well for larger images, but it’s on BitmapData level.

By: Andrei Ionescu

Andrei Ionescu — Wed, 04 Mar 2009 11:39:08 +0000

Hello Tomislav!
Thanks for your comment and for the links. Really helpful for some. My image is embeded in the SWF file so is not about the loading limit you’re saying. I think there is a “wider” limit in working with images that applies to more methods not only at runtime image loading. And another weird thing is that I wasn’t able to reach that 2880 limit specified in some articles about this problem. If this is documented please give me a link in the help (either off-line or on-line) or on the Adobe’s sites. Anyway… my opinion is that is poorly documented – on each method related to images should be a warning explaining the limitations or at least a link.

By: Tomislav Pokrajcic

Tomislav Pokrajcic — Wed, 04 Mar 2009 09:55:05 +0000

Hi Andrei,
this is documented, but takes time to find it
There are some workarounds for this. Check out:
http://tinyurl.com/b4lo8u
http://tinyurl.com/bw28hs

Cheers,
Tomislav

By: Andrei Ionescu

Andrei Ionescu — Wed, 25 Feb 2009 10:11:33 +0000

Yes. I also think is a technical limitation. But it must be documented. Developers will loose days trying to find what is wrong and if this happens in a big project that will take an eternity. I also noticed that sometimes the filter starts and doesn’t reach end but resets. And for some size it won’t even start – this is the moment when, if you’re in debug mode, you’ll see that warning text in console panel.

Regarding your idea about that applying the filter only on the visible part of the background is a good approach for some projects. But in mine I need a big background because I do transitions on x and y axis and use blur filter to give the impression of fast movement. So, to put is simple, I need a big background because the background is also moving not static.

Anyway, thanks for trying to find a way to overcome it.

By: Thomas

Thomas — Wed, 25 Feb 2009 09:58:55 +0000

Hi Andrei,

I also see it as a technical limitation instead of a bug. What about creating a viewport and applying the filter onto that viewport? E.g. a container around that big object? If you don’t want the container to be affected by the filter, try to create a snapshot out of the current visible area of the display object and apply the filter onto that snapshot.

Anyway, another objection of your example is that the filter stops even while running the filter. For example, try to use 2827×2875 in the example app: the filter runs fine (if low-performing). If you use 2828×2875, you will see that the effect is jumping back at once if the filter reaches the maximum width (2875/2880px). At 2875/2875 you will not even see that the filter has started to adjust the display object, because it instantly runs against the technical size limitation.

Hope this helps

Cheers Thomas