FL Studio 2024.1 available... hehehe

[osiris]

The Browser is rearranged and I freaked because all my Sample folders were gone. I had to repoint the location and it was okay. I like the new plugins, but having to leap over to NI to get a code for their stuff was too much a PITA. And Ozone Basic is downloadable in the Browser, but not Ozone Elements. Also the ASIO4ALL had no choices for output to headphones, which is weird because it always had, but FL ASIO did. I like the new Chord Progression tool but I wish they'd link it with the Riff Machine. The sequences are quite plain or quite manic.

[Teksonik]

The notes are just automatically grouped so all you have to do is going into the PR menu to ungroup or hit ALT+G

Thanks that does the trick.

It would be nice if notes were not automatically grouped. Chords that are just stamped into the Piano Roll are very robotic. The individual notes need to be edited to give them a human feel.

[Teksonik]

If anyone would like to try and reproduce this issue it occurs on two systems here. I'm on Win 10.

1. Load a generator then open the Chord Progression Generator.
2. Go to the Performance Tab in the CPG and select a Pattern (I used Supersaw 1 as a test) then accept the progression and close the CPG.
3. Hit Play on the main FLS toolbar and while the progression is playing try to open the CPG again. 100% of the time the following error message appears:

EDIT: I just discovered that the pattern does not have to be playing. Even with audio stopped the error message will appear when trying to reopen the CPG.

FLS 062824-2.png

[osiris]

I haven't got that but was pleasantly surprised it with play along with the loop I was working on. Only thing different I've done is stick a chord I'm working on in the piano roll because I notice it depends on a Note Marker tab at the top of the Piano Roll. I don't really know how to stick one on there, but putting the chord on the PR works.

[Trancit]

It would be nice if notes were not automatically grouped. Chords that are just stamped into the Piano Roll are very robotic. The individual notes need to be edited to give them a human feel.

I am not a big fan of the grouping either...perhaps you should let them know...

For the robotic feel: I haven´t tried but there is this performance page which does have a humanize function... just in case you have overlooked it:

Performance.jpg

[sQeetz]

I really like that FL now uses the Mac Menu system. Led me to try again. But it's so overwhelmingly bloated right now.... it just feels like a DAW trying to do it all but does most of it pretty bad.
It's like no-one is really designing it. Just feature over feature all on top of each other

[Teksonik]

It would be nice if notes were not automatically grouped. Chords that are just stamped into the Piano Roll are very robotic. The individual notes need to be edited to give them a human feel.

I am not a big fan of the grouping either...perhaps you should let them know...

I've already made a detailed report of the Python errors and as usual the post has been ignored. I don't see any point in posting again.

For the robotic feel: I haven´t tried but there is this performance page which does have a humanize function... just in case you have overlooked it:

Yes but I prefer to make adjustments manually.

At any rate I got another one of these error messages this morning that was triggered by different steps than the ones I posted above.

FLS 063024-2.png

Judging by the numerous posts on the IL forum this is the sloppiest FLS release in recent memory. I think there should have been at least one or perhaps more RCs before it was declared an official release. I don't have time to beta test it especially if any reports I make are ignored so it's back to Waveform Pro until IL releases a less buggy version.

[Trancit]

...
Judging by the numerous posts on the IL forum this is the sloppiest FLS release in recent memory. I think there should have been at least one or perhaps more RCs before it was declared an official release....

I think that´s quite normal for what they are doing/ start to do...

They are changing many things under the hood, digging deep into the internal structures of the base code and at the same time attacking the programm with changes at multiple frontlines... so unexpected behaviour at least if not more serious problems are quite normal for such drastic treatment... for bigger changes I expect even more trouble...

That´s for some annoying (it´s luckily very stable on my side) but these are important and very necessary moves and cannot be avoided... so at some point they have to stop with beta testing and RC´s and call it a day to put out the official one as good as the programm allows it in this current state...

As said I have no bigger issues and the ones who do have sadly to adapt for the moment and go with an alternative like you for the time being...

[Teksonik]

so unexpected behaviour at least if not more serious problems are quite normal for such drastic treatment... for bigger changes I expect even more trouble...

Yes normal for Betas or even early RCs. Not for an official release. They went to RC 5, said an RC 6 may happen and it really should have and perhaps beyond that before calling it an official release. A simple check at the IL forums confirms that fact.

The number and depth of changes has nothing to do with it other than being an unacceptable excuse fabricated by a fan. This is a sloppy release no matter how you try to spin it. It should still be an RC....if the reputation of FL Studio's quality is of concern.

I only install official releases of FL on my studio system for exactly this reason. I don't want to bloat it with unfinished and buggy versions. I have this system for testing betas.

[MirkoVanHauten]

No issues on my side. Probably a first for me

[Teksonik]

The only issue I've encountered is the Python errors in the Chord Generator but then I've only been working with the Chord generator so.......

I've been an FL Studio user for over twenty years and I don't remember a release this sloppy. Alphas and Betas yes but not releases.

[iNNeRNoiZe]

...ince cloud integration and new browser the browser got laggy.

No problems here on MBP M2 Max, everything runs ultrasmooth.

[Trancit]

...
I've been an FL Studio user for over twenty years and I don't remember a release this sloppy. Alphas and Betas yes but not releases.

But perhaps you remember as well that previous FLS updates didn´t contain so many deep changes at so many places in the programm and an error message of the script in a special situation doesn´t really qualify to make the whole release "sloppy"...

Are there some problems... yes there are... but it will always stay like this in software ... the bigger the changes the more unexpected behaviour can happen and there is not a single company where it didn´t happen...

As you always refer how happy you are with Waveform you might perhaps remember how unuseable it was for at least 3 major versions (8-10 maybe even longer time) until they (probably...I never tested again) got it right...
This were about at least 4 years of constant crashes ... there I prefer what IL delivers especially when it´s on top of all for free!

[Teksonik]

But perhaps you remember as well that previous FLS updates didn´t contain so many deep changes at so many places in the programm and an error message of the script in a special situation doesn´t really qualify to make the whole release "sloppy".

I remember being on the Image-Line Alpha team. It exists to make sure FLS releases are not sloppy.

Perhaps you have chosen not to read the Image-Line forums. It's not about the report I made but about different reports by other users that causes me to call this release sloppy.

You can make all the excuses you want but they're just that....excuses. Of course there will always be issues with software. But there is a big difference between an Alpha or Beta version and a release version. Or at least there should be.

Bringing up another DAW is simply deflection. Just because Company B makes an error it does not absolve Company A from their mistakes.

Any any rate FL Studio 24 was rushed to release. There should have been more Release Candidates first. If you claim "deep changes" that simply reinforces this fact. More changes require more testing. That should be painfully obvious.

[Trancit]

...
Perhaps you have chosen not to read the Image-Line forums. It's not about the report I made but about different reports by other users that causes me to call this release sloppy.

...

I don´t know if you really read them...

about 60% of them are whining why their license name was now replaced by the license plate if they even have understood what that means, tons of errors about FL Cloud/cloud plugins misbehaviour which doesn´t interest me at all and a few problems with some plugins like Soundtoys which seems to be not IL´s fault...

Sorry, but I didn´t read anything what hasn´t happen with the releases before other than tons over tons of newbies seem to have discovered the IL forum and asking questions where I sometimes wonder if they know what a mouse or a computer keyboard is...

Again, the release is superstable on my side and was actually most of the time during beta (except beta 1 perhaps)...