FL Studio memory problem

dafo93

SWITCH FUSION
VIP Junglist
Messages
701
Likes
2
#1
Hey guys, wondering if you could help me out...

I have one project on FL that crashes sometimes when I try to save the project or load up a preset to a synth. Also, when trying to export a stem or the whole track, it says that there "isn't enough memory to execute the command" and "Out of memory". It only happens on this particular project and I haven't a clue how. Could the file somehow be corrupted?

Cheers
 

kama

benkama.net
VIP Junglist
Messages
2,767
Likes
48
#2
It's a longshot, and takes a while, but you can try disabling the plugins one by one and try to export, sort of work out which plug is doing it.
 

logikz

I Am Not The King
Tribal Leader
VIP Junglist
Messages
11,117
Likes
2,984
#3
or! you could take it up with customer support at image-line? you got your receipt handy i take it
 

dafo93

SWITCH FUSION
VIP Junglist
Messages
701
Likes
2
#4
or! you could take it up with customer support at image-line? you got your receipt handy i take it
Just did, thanks for the suggestion.

I reckon it's due to the large number of Nexus synths I'm running in it, due to it being a CPU eater...however the CPU chart is nowhere near the red, so I dunno...
 

kama

benkama.net
VIP Junglist
Messages
2,767
Likes
48
#6
VST's dont occupy RAM, they use CPU power, so I doubt it. If you have a lot of audio in your project (project-long stems for example), that might become an issue, but as you use FL, it seems unlikely.

---------- Post added at 18:48 ---------- Previous post was at 18:46 ----------

BTW I've been getting trouble with the 'slices as regions' option or whatever it is, when you export a wav, it will include all the slice markers of every SliceX or fruity Slicer from the whole tune in the masterwav file. It's a problem with windows apparently, it can't read a wav with a huge amount of markers in it. It will just hang.
 

ARTFX

Artist, sound designer and tutor
VIP Junglist
Messages
1,372
Likes
58
#7
VST's dont occupy RAM, they use CPU power, so I doubt it.
That's not totally true, RAM is used to store all processed data.
Also in audio production.
For instance your softsynth patches that contain samples (Kontakt, Nexus, EastWest) that you load up will be loaded up in your RAM.
So when working with VSTi like for instance an Orchestral plugin which is sample based can really take up loads of RAM.
Next to that you also need a good CPU, for the non-sample based plugins.
 

TongueFlap

Flappin'
VIP Junglist
Messages
3,836
Likes
8
#8
That's not totally true, RAM is used to store all processed data.
Also in audio production.
For instance your softsynth patches that contain samples (Kontakt, Nexus, EastWest) that you load up will be loaded up in your RAM.
So when working with VSTi like for instance an Orchestral plugin which is sample based can really take up loads of RAM.
Next to that you also need a good CPU, for the non-sample based plugins.
I had this problem with logic on my macbook. I stuck in 4 gbs ram and never had the problem again
 

ARTFX

Artist, sound designer and tutor
VIP Junglist
Messages
1,372
Likes
58
#9
Yeah and because with the topic openers issue FL says 'out of memory' I think this might be the issue.
 
Messages
34
Likes
0
#11
Yeah and because with the topic openers issue FL says 'out of memory' I think this might be the issue.
This.

You either have to get moar ram or a better precessor. wun of the two, FL is a serious memory hog on its own. Not to mention using VST's, i have 4gb DDR2 hyperdrive and it still gets kinda funky when using two or moar gladiator plugs ins.
 

ARTFX

Artist, sound designer and tutor
VIP Junglist
Messages
1,372
Likes
58
#12
This.

You either have to get moar ram or a better precessor. wun of the two, FL is a serious memory hog on its own. Not to mention using VST's, i have 4gb DDR2 hyperdrive and it still gets kinda funky when using two or moar gladiator plugs ins.
I have 6 Gb of RAM and even my pc gets laggy in FL when using more than 20 sample-based plugins with effects on it.
Now that's fucked up since I kinda have about 20-30 sample-based VSTi patches layered up in a tune working on right now.
Why I do that, to create a really full and energetic sound, but since all layers require different effect settings and mixer channels it gets laggy.

Next to that, I don't have issue's when working in Reason.
Can open up to 100 patches without having problems.
 
Top