Image Composer "Out of Memory" Message
Bonnie Miller
forgive me if I am in the wrong place.
I have used MS Image Composer 1.5 for many, many years and am
reluctant to replace it. However, I have a problem.
I just purchased a brand new desktop PC running Windows 7 Home
Premium. It has a 620g hard drive, a quad core processor, and 8gb of
DDR2 RAM.
I installed Image Composer, and the install seemed to go well.
However, I am getting the "out of memory" message almost as soon as I
open an image and try to do anything with it. (Got this with XP Pro
sometimes, but never as immediately as I get it now.)
I have been reading posts for about 4 hours now, and the closest I got
to an explanation of how to fix this was a post that said: "Figured it
out. The problem is related to when the memory should be allocated as
the program runs. If I move those memory allocation codes to the top
of the program, not at the point where such requests are
needed, it seems working properly."
Unfortunately, I have no idea what that means or how to do it on my
own computer.
Can anyone offer any suggestions or an explanation, please? I really,
really want to be able to keep this program if at all possible.
Thank you.
Bonnie
Jan Kučera
Image Composer cannot take advantage of your 8GB RAM - it has a fixed amount
memory which it can allocate, and unfortunately this limit prevents you from
opening large images, for example from today's cameras.
The post you reference is probably unrelated to the Image Composer, out of
memory is general error and the solution you have found is intended for
developers.
If I really need to edit such image in Image Composer, I firstly split it
into smaller images and then do the editing on all of them separately.
Jan
"Bonnie Miller" <bonni...@gmail.com> wrote in message
news:74731734-e071-4b35...@r5g2000yqb.googlegroups.com...
name-a-rooni
I have a Vista Ultimate machine running 2gb RAM.
I shoot using a 14.3mp SLR. Image Composer will not accept RAW images, but
I sometimes use it to assemble several jpgs into one panorama. JPGs are
typically in the 13mb size range.
Because I have never had this problem, I just tried using IC with seven
jpgs, each between 11 and 13mb. Then again, this time with five bmps. The
bmps were 24bit, 72dpi, 4672x3104 and over 41mb each.
In each case, the only "problem" I experienced was while attempting a resize
of an image: I lost the Undo function.
Aside from the accompanying very slight slowdown (which was not a particular
problem for me), and the fact that, even when zoomed out to 10%, it was
difficult to see more than three entire images at the same time, the whole
process was simple and successful without any crashes or out of memory
messages.
If it's happened on different machines running XL and Windows 7, it seems
that there is something else that is not directly Image Composer's fault.
As this is a new machine, and it's common to have onboard video as opposed
to a separate installed video card, I wonder if the root cause is something
as fundamental as onboard video hardware grabbing the memory that Image
Composer wants.
In that case it's probably going to need a video card with its own memory to
be installed and free up the PC's own memory.
Just my opinion.
James
"Jan Kučera" <kuc...@lupacovka.cz> wrote in message
news:%2374NUFk...@TK2MSFTNGP04.phx.gbl...
Jan Kučera
out of memory messages. Though, the problem is not in the size of the file,
I agree. I also don't have problems working with 9120x5640 jpegs, so the
problem must be anywhere else. Maybe in the decoders, I don't know. Maybe it
uses some special features in the file type...
Maybe if Bonnie could send me some example (kuc...@lupacovka.cz), I can try
to open it and if it will work for me, than we could try to find if there is
any help available.
Jan
"name-a-rooni" <name-a-rooni@site-a-mungo> wrote in message
news:u2$xw3GnK...@TK2MSFTNGP06.phx.gbl...