Because Sylenth doesn't have a 64 bit version. Let's see how it turns out.Įdit: Now I know why I didn't use 64 bit before. I'm gonna work with 64 bit FL 12 and 64 bit plugins only this time. I'm keeping FL 11 on my PC and FL 12 on my laptop.
I re-installed my laptop anyway, put a new Windows 8.1 Pro on it because I think I already had virusses(haven't even used it for something other then producing, and I think 20 hours is the total time I have been on it).
Over here it's even weirder, only 32 bit works with 32 bit, and 64 bit with 64 bit. Can't seem to find the video right now, but I'm 100% sure it was in there. No not a lot of commercial plugins are still 32 bit-only.Hmmm raar. Yes a lot of old (and new) freeware (like synthedit stuff) is still 32 bit-only. Tell your teacher that "still a lot of plugins" is pretty vague.
No not a lot of commercial plugins are still 32 bit-only. If you like being a bit bridge tester, then go right ahead, use whatever. I got all kinds of weird problems which makes it nearly impossible to finish a project.How old is that video?Ħ4 bit plugins work fine in FL Studio x32 (at least in v11.1 & 12, I just tested it).īut if you want to be sure about best compatibility & performance, only use 32 in 32 and 64 in 64. I still don't get why my 32 bit Fabfilter pro-C doesn't work in FL 64 bit though. 32 bit plugins work fine anyway so why switch? Also, my teacher said that there are still a lot of plugins that don't have 64 bit, so it would be best to stick with 32 bit for the time being. The reason I didn't start using 64 bit plugins and 64 bit FL is because the 32 bit used to work just fine, but now that my projects are getting bigger I need more memory. I forgot that Fabfilter has these plugins in 64 bit, I even have them in my download folder 32 bit plugins with 64 bit FL however, does work. I will use the 64 Bit version from now on.Īccording to a video from Image-Line themselves at Youtube(Fl Studio Guru) 64 bit plugins don't work with 32-bit FL. But still, if the path was incorrect it should not open for instance Nexus or Sylenth, and it did. The path to plugins should be alright, but I'll check. Not the new FL12 because I still have FL11. I assume buffer size and buffer length are the same thing?ĭriver I use mostly is the asio4all, but because I was watching youtube today and switching between that and FL, I noticed the crackling but didn't realize I still had it set to primary sound driver.
When set to asio4all driver though.when I select 'Primary sound driver' the ASIO box disappears and I can only change'buffer length' which is at 4096smp (93 ms).
Is the path to your VST plugins set correctly in FL 64 bit? For future projects, if you want the full 8GB available to FL Studio, I recommend using the 64 bit version.My buffer size is at 2048 samples. So what driver are you using then? Primary audio? ASIO4ALL? The new FL12 ASIO wrapper? Better audio interfaces can use lower buffers relative to CPU usage (and thus better latency). Then you'll have to set your buffer higher when crackling starts. couldn't find a FL Studio subforum, so I put it in here) Also tried optimizing the settings(triple buffer and blabla) but also doesn't work. Why is it already cracking when I still have 600MB left?Īnd question 3, how can I fix this? How can I 'give' FL Studio memory from my RAM?Īlready tried bridging plugins(edit: I found out bridging the plugins even causes more cracking), but I have to do it over everytime I reload my project, and plus, it doesn't work because it still cracks. Why does my FL studio tell me I have only like 2000MB of memory available while my PC has 8GB RAM?Ģ.
I can right click this bar and click 'show available', and then it shows me I still have around 600MB left. My FL Studio 'Memory usage' bar at the top says I am using 1440MB right now. As if the PC can't handle it.īut there's a couple of weird things which don't make sense So now, it's reached the point where I can't finish my favorite and best projects so far, because when I play the whole song and it arrives at the chorus, things will start cracking like hell. Because my projects are getting larger, I'm using more plugins. Every day I am learning more, and expanding my projects.