FL Studio 12.4 Released

[EnGee]

I have the same processor i5-4570! Anyway, I have not many plugins installed now and most of them are CPU friendly (Retrologue2, Hive, Predator, ...etc). Today I'll start my first project in it and I'll use also Reaktor instruments, ACE and LuSH 101 (Those are the heaviest I have).

What ASIO driver you use?

[Orbit-50]

Still, it currently is the most CPU hungry DAW I worked with!

I thought it was just me. Now I feel better. I'm using an Intel i7-6700HQ and it handles a lot. The FL Studio higher cpu usage thing is not a show stopper for me though. I actually find it a challenge to use which is not a bad thing. Once I render stuff, it uses nothing.

[Orbit-50]

Today I'll start my first project in it and I'll use also Reaktor instruments, ACE and LuSH 101...

You are so looking for trouble now.

[ls1xxx]

Hey Image Line I just wanted to say congratulations. You guys have created the best damn Piano Roll out of any DAW I have ever used and I'm sure others will agree. It keeps just getting better and better. I just love it! Well done guys! Thanks so much!

[3ee]

I have the same processor i5-4570! Anyway, I have not many plugins installed now and most of them are CPU friendly (Retrologue2, Hive, Predator, ...etc). Today I'll start my first project in it and I'll use also Reaktor instruments, ACE and LuSH 101 (Those are the heaviest I have).

What ASIO driver you use?

doesn't matter what ASIO driver/settings I have because I was talking about the CPU usage relative to the other DAWs I've tried... they feature the same driver with the same settings... as well as the same 3rd party plugins.

Some of the other DAWS are: Reason, Ableton Live and Studio One .... FL Studio usually tops CPU about 15-20% earlier then the others... that's significant if you ask me!

If I lower the PPQ setting (usually I NEED to increase it) in FL, I'll get almost on par with the others.
If I increase the PPQ it's a ridiculous amount of CPU usage!!! ... The other DAWs seem to have the great resolution but use less CPU, this makes me think that the way FL is handling PPQ really needs to be redesigned, if not impossible to do that is...

[keel]

FL Studio use so much more CPU than all my other DAWS. If I build a song in Live. CPU meter doesn't even reach 40%. In S1 meter is around 50%, but in FL, it is 80-99% al the time. Crackling and stuttering..

What they should do:

- Proper PDC
- Improve CPU usage a lot
- Bring back blocks, you killed my + so many other peep's workflow.
- Don't remove features, old school users actually use them..
- Change the gui look, at least on mixer. Old was 1000x better. New is complex and busy look

Thousands of people still use FL 10 and 11 and there is a good reason for that. I keep using FL 11, probably long time.. Or I just move to some other DAW.

[nostradamoose]

I think your perception here is slightly skewed. I have witnessed over the years the fact that Image Line for some weird reason is a magnet for trolls and malcontents who have this strange sense of entitlement for some unknown reason. I can see it getting really tired on their end. You also mention "the real world" as opposed to the fanboy users that are happy using FL? What are the issues that you are having with FL Studio that need tending to? Have you been told to go screw yourself after asking for technical support? Does FL studio not work properly? Is it broken? Are there missing parts? Just ask and I'm sure someone will help fix your problem. It always works out. Give it a shot. I know I have. No one will write you off. Trust me.

Now if you're a fanboy or a long time user, it's only obvious there will be 100% support for the company, no matter what they do. But this is the real world and problems and issues exist that need tending to, whether a company likes to admit it or not. Let's not write everyone off for disagreeing and being undeserving of their opinion or worse a bully.

or "trolls and malcontents".

[crimsonhawk47]

FL Studio use so much more CPU than all my other DAWS. If I build a song in Live. CPU meter doesn't even reach 40%. In S1 meter is around 50%, but in FL, it is 80-99% al the time. Crackling and stuttering..

What they should do:

- Proper PDC
- Improve CPU usage a lot
- Bring back blocks, you killed my + so many other peep's workflow.
- Don't remove features, old school users actually use them..
- Change the gui look, at least on mixer. Old was 1000x better. New is complex and busy look

Thousands of people still use FL 10 and 11 and there is a good reason for that. I keep using FL 11, probably long time.. Or I just move to some other DAW.

That's weird. My PC vomited if Pro Tools even tried to open. FL was the only thing that was stable for me.

Unfortunately I don't think that PDC thing is getting fixed. It's a problem with architecture of FL (the way the playlist and mixer aren't directly connected). It has been brought up by me and many others before. There are workarounds, mainly side-chaining the problem latency tracks to others to "force" the PDC further down the line. I only have a problem with it with more complex routing, but it's definitely a problem. I would like to do more Andrew Scheps esque mixing with many parallel compression sends, but that gets dicey in FL.

But I gotta say, a lot of people like the new features. Blocks were obnoxious to me, and the step sequencer wasn't integrated with the Piano Roll like it is now. The vectorial UI is amazing because everything takes up only as much space as I want it to. With the mixer, you couldn't move multiple mixer faders before. You couldn't even mute playlist tracks before (which may not seem important to people that haven't used FL a whole lot, but it's a godsend). I did eventually leave FL for a little bit, and FL12 is what brought me back.

Edit: Although now I'm trying to remember what I did to cause PDC issues so let me find that so I'm not just hurling accusations.

[camsr]

Yes PDC can break in some circumstances, the way to solve it is to create a new mixer track to "route" what had broken alignment.
http://www.kvraudio.com/forum/viewtopic.php?t=391008
I think sends to sidechain tracks might be ignored by the Auto PDC

[EnGee]

I have just spent few minutes testing so it is just a first impression for now. It seems FL likes the new u-he RePro-1!! It is definitely less than Cubase and other DAWs!
ACE is not bad, and LuSH has the same usage as the other DAWs (or very near). Retrologue 2 is great! between 2% and 4%! Excellent! But Reaktor seems problematic (a lot!!) I played little with the Blocks, and 'Drive', the synth, is already indicates in the red in Reaktor cpu measure! With usage more than 20%, weird!

Anyway, I didn't hear artificials and the FL Studio cpu measure didn't pass the 25%. I need to start make a new project and see it in a real use now.

[Image-Line]

Yes PDC can break in some circumstances, the way to solve it is to create a new mixer track to "route" what had broken alignment.
http://www.kvraudio.com/forum/viewtopic.php?t=391008
I think sends to sidechain tracks might be ignored by the Auto PDC

Sends are not PDC corrected. They will be in FL Studio 13.

However, problems are very easy to avoid with these two steps the manual explains:

https://www.image-line.com/support/FLHe ... #Mixer_PDC

No direct to master routing - Make sure all Channel Rack instruments are routed to Insert Mixer tracks and not directly to the Master.

Inter track routing - Where you want to route one Insert Mixer track to another, use 3 tracks. Starting with the original Insert Mixer track, deselect its Master Send. THEN route it to: 1. An Insert Mixer track that does go to the Master. 2. An Insert Mixer track with the send-to effects you want to add. This avoids the problem that Mixer sends are not delay compensated before arriving at the destination track.

[incubus]

FL and win7 didn't get along well for me.

But FL and win 10 (and I'm sure 8 according to one of the vids that showed the difference power settings made) it's now fine.

The only issue I still have is many of the older demo songs glitch a lot regardless of cpu use. Other than that it's mostly smooth sailing.

[tooneba]

These FL Studio threads look like a bullying contest. It's not that I pitty Scott, cause it's his job to do what he does, but it's really difficult to understand the attitude.
There is critique for all music software on KVR but FL gets an "special treat" for no obvious reason imo.

Yeah, I can guess why other companys marketing dep. scarcely respond in the forum even when they are online.

What you won't see are the devs from Studio One, Reason, Cubase, etc lashing back or trying to shut down communications by labeling people as half empty or worse.

I saw so many times Steinmod shutdown or doing sneaky "moved to off-topic" thread in their forum. In the S1 forum too. But I don't often see this in IL's even for "12 is garbage! I moved to ***!" thread in the main forum.

So I don't get the impression that IL is trying to hide something or suppress the freedom of speech.

[inkwarp]

These FL Studio threads look like a bullying contest. It's not that I pitty Scott, cause it's his job to do what he does, but it's really difficult to understand the attitude.
There is critique for all music software on KVR but FL gets an "special treat" for no obvious reason imo.

i'm lost on that : )
. i have never ever had probs with image line, in fact they are some of the most amicable and helpful people in comparison to some companies. the special treatment you speak of does not exist either, except in your addled mind. if anything it is derided, labeled a toy etc.. pejoratives claiming it's not a 'proper DAW'..
people who use it FL, who have invested some time to aquire it's workflow will tell you, if anything, that it is severely under-rated.
still if you can show me what you mean about the 'attitude'?
i am happy to hear it.

[nostradamoose]

FL and win7 didn't get along well for me.

There's been a lot of changes since Windows 7 architecture was first released nearly 8 years ago. The way the new generation of hardware, CPU, memory, BIOS, software and drivers all communicate and allocate system threads, settings and features has been vastly improved.

This is the same issues Studio One users are having, which requires BIOS settings to be enabled and disabled manually (Turbo, etc). Which probably has something to do with 3rd party plug-ins being coded 8 years or more ago and not performing as well on modern DAW source code design. Most companies have updated and adjusted for this already, but there's probably a lot still having issues. It took Softube a long time to get all their plug-ins to work well with all DAWS and Windows 10.