The 30K x 30K limit is for the Editor, not the Organizer. The table in the article shows the limits based on the amount of memory you have installed, e.g. if you have 1 GB of memory the limit is 36 MP.
For one of the offending JPEGs, what does the Organizer show as the pixel dimensions in the Properties pane? How much memory do you have installed?
Hope this doesn't show up twice - I did the migration in the middle of my first reply and now don't see it. Anyway...
I have 4gb of RAM installed. One of the images in question is 27.8mp (7200 x 10800) which half of the maximum according to the TechNote. I'm also getting the broken thumbnail on many of my .CR2 files. Could the two problems be related?
Thank you VERY MUCH.
Thomas M Nichols, CFA, CLU
Nichols Investment Advisors
111 Pine Street, Suite 1800
San Francisco, CA 94111-5620
(415) 307-5662 Cell
(866) 234-0075 Fax
California Insurance Lic 0B01127
Registered Representative FSC Securities Corporation
Securities offered through FSC SECURITIES CORPORATION
A registered broker dealer. Member FINRA/SIPC
Advisor services offered through Nichols Investment Advisors
a registered investment advisor not affiliated with FSC Securities Corporation
I have just started having this problem. When I crop an .nef file and try to save as a jpg, I get the File too large error back in organizer after closing the editor. I noticed that "someone or something" doubled the dimensions of the file?? I've cropped quite a few files the same way and they still come out 4288x2848 but this one was double. I have 8 gigs of memory and a terrabyte drive, so I don't think space is a problem. The .nef file is 13mb and the new .jpg is 9.5mb. I've done a catalog repair - it said no repair was needed. Is there some setting I've gotten changed to make the program keep the mb size but change the dimensions?
FYI - there is a registry change that can be made to allow
more memory to be allocated to the Organizer (apparently the size of the
file that can be viewed is limited by the memory availble to the Organizer).
The instructions used to be at
http://www.adobe.com/go/kb402760 however the link is "Unavailable".
Maybe someone is has an update. With OS 64 and more memory available, maybe the algorithm used to set up available memory in the registry should be modified?
Hi. Thanks for your help. I did look up the pixel dimensions and they were
the same. I believe the reason my pic was so large was that I had
inadvertently gotten 720dpi in my crop dimensions. When I set it back to
360dpi, everything worked as expected. I'll look into the registry issue as
I had inadvertently set the dpi at 720 for an 11x14 crop, so maybe it was that. When I reset it to 360dpi, I didn't get the file too large error.
Hmm, when I try that using the crop tool in the Editor, the pixel dimensions remain the same, just the ppi is changing.
However, if you were really created an 11x14" image at 720 ppi (e.g. using the Resize command), then that would have 11 x 720 x 14 x 720 = 79,833,600 = 76.1 megapixels, which does exceed the limit.