On a Mac system, the buffer size is set in your DAW - usually in the Audio section of the Preferences page (DAWs may vary). On a PC system, the buffer size is set either in Focusrite Notifier, or the Audio Control Panel. I had a 15 hour struggle in the studio recently. All my Cubase 7 (64 Bit) projects refused to load without crashing. Even projects that I was working on the very day before. I re-installed, searched, cleaned, refreshed preferences, you name it, I tried it. The only software I'm using is fl studio on win7.I'm increasingly using logic on osx along with the adobe range for design etc etc. I don't see why you wouldn't do it if you have the option? At the end of the day you could use a Commodore 64 with a tape deck for all I care. This appears to be related to a plugin crash when more than 3 instances of the plugin are in use in a project. Solution: Update to Nexus 3.0.8 or later. Reveal Sound Spire. Problem: Spire not working properly in FL Studio, freezing and crashing. Solution: Use the recommended settings provided by Reveal Sound in ' Note For FL Studio Users! If you're experiencing issues with FL Studio crashing at startup we recommend that you: Try resetting your FL Studio settings. This will delete the FL Studio settings in the registry and reset them to the default installation configuration.
- How To Stop Fl Studio On Mac From Crashing Windows 10
- How To Stop Fl Studio On Mac From Crashing Using
A few ideas come to mind. WAREZ copies are bad. We all know we should not use that crap and I am not saying that you use that. Warez FL Studio got viruses, they are poorly patched, have memory leaks, crash a lot and should be avoided as a general message to everyone.
With you I suspect having two version of the same product can cause problems. FL12 could in theory call up an executable file or dll file with the same identical name in FL11 and vice versa. FL's VSTi's may also be at conflict in your VSTplugins location folder as well. Registry entries may also get misdirected.
So in summary what may have happened is something (dll, exe, or Reg, etc.) may have tried to access the same RAM (memory) location at the same time on your FL versions and are possibly competing with each other and then BANG, a crash! Although your two version arrangement worked for a while, it was just a matter of time, as other friendly programs do make silent changes along the way.
I would drop FL11, use something like CCleaner afterwards and then update to the newest REV of FL Studio 12 if you really want to be done with this problem.
I never liked that Bug/Crash Report screen. I understand its usefulness, but only if you intend to send your bug in to Ableton. Also, it can seriously slow down the reload times plus you have to manually close that screen.Thankfully I found the way to avoid it. All you'd need to do, is remove the 0 byte CrashDetection.cfg file.
On windows 7 it's located in
C:Users[username]AppDataRoamingAbletonLive[version]Preferences
How To Stop Fl Studio On Mac From Crashing Windows 10
On XP, that would be
How To Stop Fl Studio On Mac From Crashing Using
C:Documents and Settings[username]Application DataAbletonLive[version]Preferences
The way I do it, is to start Live from a DOS script that simply deletes this file and then starts Live.
I hope this is not considered too dirty a hack. If it is, please feel free to remove this post.
Also, if there is a cleaner way to do it, I would like to hear about that.
This may have been mentioned or requested before, but I think no one is going to send in a bug report the first time Live crashes on something. You're going to have to make sure the issue can be reproduced, so you'd have to start Live at least a second time, which would offer the opportunity to then choose to have the Crash Report be displayed the next time it crashes.