Allocate more RAM?

[Chironyx]

I had some MAJOR issues this morning, which brought about them alot of mess, I'm not even going to go into them right now though, all of this was caused because it seems aseprite only uses 2GB of RAM...

My project had about.. 16 layers and 672 frames, when it gets that heavy, aseprite has a hard time exporting the project, especially in bigger %, which really sucks, since I spend hours upon hours on something and can't convert it to video in normal quality because I can't export it in anything above 200%

My computer has 16GB of RAM exactly for this purpose, it had 7GB to spare when all the memory problems occured
Is there a way I can launch Aseprite in advance with more memory used?
People say a software usually just uses as much RAM as it needs, but if this was the case, I shouldn't have had any problems when I tried exporting the project with 7 unused GB of RAM

TL;DR
Can I allocate more RAM for Aseprite to use?

[◢ k r i s ◤]

I'm not sure it's even being developed for 64-bit (Steam is distributing a 32-bit version of Aseprite). So 2GB is the technical cap until a 64-bit version of Aseprite becomes available.

You should look for way to split up your project in to smaller projects in order to reduce memory needs. Maybe also look into some compression techniques. Unfortunately that's probably the best you will get without an overhaul to 64-bit. Would be neat to find out if something like that were being made available.

[Enginya]

Actually I think exporter could be relatively easily fixed to allocate much less RAM by dropping converted parts (say frames) of data to disk drive instead of trying to do whole conversion in RAM and then saving result. It'll be optimal this way.

[dacap]

Actually I'm planning to add a x64 build soon to edit bigger sprites/animations. I hope it helps. Stay tuned for v1.2-beta10

[Chironyx]

Originally posted by ◢ k r i s ◤:

I'm not sure it's even being developed for 64-bit (Steam is distributing a 32-bit version of Aseprite). So 2GB is the technical cap until a 64-bit version of Aseprite becomes available.

You should look for way to split up your project in to smaller projects in order to reduce memory needs. Maybe also look into some compression techniques. Unfortunately that's probably the best you will get without an overhaul to 64-bit. Would be neat to find out if something like that were being made available.

Originally posted by EyeGem:

Actually I think exporter could be relatively easily fixed to allocate much less RAM by dropping converted parts (say frames) of data to disk drive instead of trying to do whole conversion in RAM and then saving result. It'll be optimal this way.

Thanks for the anaswers!
Splitting up my project can be pretty time-consuming and uncomfortable, especially when I have to copy and line up parts of a 16-layer animation and experiment with how much I can copy every export
I would then have to put all of them together on another software...

And yeah EyeGem, that does sound a little better, no idea what the technical side of that would take for Dacap to be able to implement such a thing though...

Originally posted by dacap:

Actually I'm planning to add a x64 build soon to edit bigger sprites/animations. I hope it helps. Stay tuned for v1.2-beta10

Waiting in anticipation, I love Aseprite so much and that is pretty much the only problem I had so far, thank you!

[Aeon]

Hi! I'm upping this thread because I'm having the same issue.
I'm working on x64 (W10) with 8gb of RAM and I'm having some trouble:
So the file got 145 frames with 5 layers. When exporting it I'm only using two of them.
Beside the save time that is getting annoyingly long, I can't export it. I got the "not enough ram" around 4/5%.

Have just missed the option to increase RAM usage? Am I forced to use another software for projects "that" big?