If music creation is important to you, or is your job!, I suggest always holding back for a while until others have tested new software versions.
Saw a quote on AS somewhere: "There are two types of people in this world. Those that work on their computers, and those that update their system".

FL doesn't but IL do! S1 is alright, but why not go with a tried and tested 'elder' daw?
Another quote: "Get out of the paddling pool, and into the swimming pool".

 

You're right, but what people say is a huge upgrade is very subjective also. Many of the huge upgrades i sometimes think they should have had a long time ago. I cant lie though, i love the midi scripting update and it definitely gives developers something to work with for hardware

 

It's more like random crashes I get with these new updates. Every update its something else. ppq i currently have at 48 I believe. That's the sweet spot for me!

 

That's interesting.
Why not 960 PPQN as per most daws?.
Are you happy with how "48" PPQN sounds to you? (I guess you mean 480?)

 

send me them links

 

For UK peeps.
"Underwhelmed, overwhelmed, Fruity Loopy.
The Image Line Fruity Loops smelling of pee.
Making good use of the tune in my mind
impossible with the daw folks leave behind."

 

Here's a theory that might make me sound stupid: IL is purposefully ignoring some stuff so that they can release a huge, nay, humongous "bugfixes and patches" update that'll make 'em look great again. Call me a dunce if you want, I'm just stating just a dumb theory in my head

 

Wow so many frustrated users here. For me i never had any crash for fl studio since v12 and it works very smooth on my machine. Yeah but the new midi importing to flex is a bummer. I scratched my head when i dragged some midi files and it changed synth to piano preset in flex, rest is all good. Yeah and i also use FL on high performance graphics setting on GPU.

 

most likely. I believe/hope some REAL major update is on its way, one that is going to be better and more stable for production

 

Well, I am still wondering when they are finally going to implement unlimited mixer channels. I just don't get it why it's still not there and why this takes so long.

 

Sorry guys, maybe I should change the title to (EXCITING & MIND BLOW BLOWING BUG FIXES!!!)
On a serious note I don't consider bug fixes to be 'updates' as they're a standardized/expected feature of every patch. Updates are separate improvements or additions and bug fixes are their own part of the patch listed within their own subsection. Semantics R FUN!!

This has been a perplexing change indeed. IL are forcing flex down your throat whether you like it or not... On the user forums you get a good look into the kind of users excited about it as they actually requested a specific sub forum for sharing flex patches. Maybe I'm getting too old but LOL its not like you'll be making any meaningful changes to the patches anyway.
Anyone is free to think I'm being nasty but go ahead and open your favorite midi file using flex, take a listen and then compare it to what it sounds like playing out of anything capable of general midi playback. My opinion is irrelevant, just listen to the basic patches and if you hear no issue then I'm happy for you.

Not that I disagree with more channels but how often do you find yourself running out of mixer tracks? I tend to group multiple elements into channels instead of having each sound or sample being its own channel so with my 8 send setup I have 117 tracks left to use. Most I've ever hit was 82 and there was a lot of redundant stuff going on.

I'd say Logic 10.5 was a BIG update that expanded the functionality of the daw in a meaningful way. Good to hear that you're enjoying the midi scripting, I haven't been able to find much use for it as my only outboard synth is a virus ti. I'll have to dedicate more time into finding more uses for it.

PPQ is a baffling issue for me. I use 192 as the default but opening medium to large size projects with lots of audio clips causes big cpu jumps. Its not like getting a "better" cpu solves this either as 90% cpu in FL is equal to only a quarter of my cpu being used according to Activity Monitor.
I can't find the exact article but https://www.admiralbumblebee.com/ has discussed it a few times and explained how it really works.

 

This is all very interesting.
It sounds like you are using 1920, which is double the resolution of 960, which should be minimum imo. So that's good. I guess FL states it as 192. Anything less than 960 can sound just wrong, yet not always depending on style of music. I play a lot of live stuff in and don't quantize, so I really want the best res possible.
The cpu jumps sound like they're related to audio. MIDI tick resolution shouldn't affect that.
Most interesting: sounds like ram allocation for the daw isn't really aligned with the OS, and cpu allocation too.
Whilst Logic on macOS has done well on that front. Plus, we can still allocate ram seperately for Kontakt, bypassing Logic's limit and how it would dictate Kontakt's ram allocation.

 

great idea for a troll post

 

Are we talking about the same thing here? Haha FL studio by default starts every projects timebase at 96 PPQ

 

i.e. 960 PPQN.

 

I think you have to be more specific because FL has 96 and 960 as the last option which can be confusing when trying to explain to people. I actually thought you were using FL tbh

 

Do you? Okay. 960 is the minimum for smooth sequencing.

Haha. Must sound awful. Perhaps they were trying to hide the cpu flaws by making it default, or were appealing to people who only want the sound of an old drum machine.

Myself and @lancexx (the op) are. I have no idea what you are talking about though. Or why you are addressing me.

Don't be confused. I've been using MIDI since '86 and I happen to know a few things.
Timebase affects your MIDI recording, and your potential to move audio where you want it. It also affects your ability to be able to zoom in on a piece of audio.
I would suggest tracking up with the highest setting, bouncing all as audio (so we know everything is already in the right place), and then lowering the PPQN setting so that you FL people don't have cpu problems.
My daw and hardware are fine at 960, 24/7. I never change to lower. I can't imaging ever needing to.
It doesn't sound like FL is a good daw, due to these cpu problems in regards timebase settings.
With early drum machines, it didn't really matter that the highest was 48 PPQN before 96 came around, because it was for drums and not for capturing live MIDI piano or whatever! And a good groove can be made with 24 PPQN.
Modern daws are able to capture exactly what is played into them. But not with 96 PPQN!
Your 96 may be okay for simple MIDI rhythms, but imo that's all.
If your music starts to sound less stunted & mechanical, fresher, and more alive after inplementing what I've said, then you're welcome.
An analogy could be that it will be like going from a sequencer or old drum machine that can only quantize to 16th divisions, to a sequencer that records exactly what you played; as does tape or digital audio.
Admittedly, if your preferred genre is already a mechanical sounding one, none of this need concern you.
True: I thought 96 in FL must mean 960! Haha. Shocked and amused now.

This guy sounds like he is full of mucus, but I think you may still be able to understand him.

 

Don't have much to say about this topic, but for me since version 20.5 (maybe a little sooner or later) the cpu problems just got worse and worse. Never had CPU problems with FL Studio before Version 20, it really gets on my nerves. And my PC is quite decent. Maybe I should finally switch to my (legit) cubase completely... I planned to buy FL Studio too, but.. not now. This MIDI to Flex thing is a huge pain too.