"HVnitro006" <webfor...@macromedia.com> wrote in message
news:c4r60t$91g$1...@forums.macromedia.com...
Dave
"HVnitro006" <webfor...@macromedia.com> wrote in message
news:c4sao2$ba5$1...@forums.macromedia.com...
> 512 MB of RAM
--
Jim Fee
Viking Electronic Services
jfee (at) vikinges (dot) com
"James Fee" <jame...@verizon.net> wrote in message
news:c4u8h6$sqe$1...@forums.macromedia.com...
"Dave" <dgri...@sewanee.edu> wrote in message
news:c4ubqh$4eg$1...@forums.macromedia.com...
"HVnitro006" <webfor...@macromedia.com> wrote in message
news:c50rnm$mbt$1...@forums.macromedia.com...
maria-
For anyone who cares ... no one? :) Oh well. Although I do not know the
exact reason for my error message, I think it is related to the library ...
linkage problem? I tried to trace back what I did prior to the error message
(not wanting to redo everything) and realized that when I imported a series of
images replacing an older set, it didn't replace one image in the middle. I
checked the images I was trying to import and they were fine. I tried
importing the series several times with the same results (this is even after
doing a cold-restart of my system and flash) So this time, I eliminated the
series from the library before importing and was successful. I saved the file
and was able to load it without any error messages.
And here's a lame link about
http://www.macromedia.com/support/flash/ts/documents/bigflash.htm for
Flashback10
As for size of files, I've worked with a 270meg AVI file and have
converted to a FLV (which came down to about 30megs). So for size of
files and such, I wouldn't imagine it should be a problem.. (BTW, that
was done on a dual P3-500 with 256megs ram...since then I've dropped in
another 512mb which makes things better on a whole <can't imagine why,
chuckle>, granted no speed records were broken, but it did chugg through
all ok.
Cheers,
-xyst
How it made its way into the windows version is either a practical joke or
confirms that programmers at Macromedia really are monkeys, sitting in a room
banging on the keyboard waiting for a program to emerge from their nonsense
code.
Unfortunately I was unable to find a solution. It is almost certainly related
to the Library getting overloaded with stuff. I had a ton of bitmap graphic
animations and such. I tried opening it on several other computers, updated
Flash to latest version, added more RAM (2gigs on a dual 2ghz G5), and still
got that lame error message. Finally, it just worked and didn't crash when I
opened the library. I was able to trim out the unwanted fat and now things are
smooth sailing. May only be specific to MX 2004.
Hope this helps. Hope Macromedia pulls their act together...
Several books mention this and suggest workarounds, like "Flash Hacks" by Sham
Bhangal. Also you can read this thread that goes into bloating problem:
http://www.markme.com/mesh/archives/002039.cfm
What I was able to do, however, was to open my Mac file on a trial version for
Windows, and go through and delete scenes, Save and Compact, then Save and
Compact AGAIN to get rid of anything that was unused. That's when I had the
breakthrough. One of the scenes kept causing the memory error to come up, no
matter what I did to correct the issue. When I looked on the stage, one of the
PNGs that I had imported was mysteriously blank. After I deleted it from the
library, the file saved just fine.
I then thought, what if I delete only that item from the huge file? Holy crap,
it worked. Sure, I have to go back and fix fonts and stuff, but that's better
than losing a week's worth of work. Hopefully my experience will be of some
assistance.