Are other DAWs updates/major updates also so buggy? FL Studio

[Caine123]

hi guys, no trolling here, still FL Studio user since day one, i dont have the long year experience with other DAWs as i started to use Ableton/Bitwig not very long ago.

Am glad that FL Studio gets finally crucial updates but checking the BETA topic i always see lots of bugs/crashes and also use sometimes new BETAs to test and wonder why it is so buggy until RC releases. so i wonder are other DAWs new versions a buggy process as well?

just checking people who follow Cubase, Logic and oter DAW processes.

[eLawnMust]

Sad to see so much of this nowadays but if you been a user since 'day one' then probably know that old fruity 2.XX best stability & great sound, no updates necessary...

In order to 'advance' you must 'retreat'...

[aMUSEd]

checking the BETA topic i always see lots of bugs/crashes and also use sometimes new BETAs to test and wonder why it is so buggy until RC releases. so i wonder are other DAWs new versions a buggy process as well?

You do know what a beta phase is?

[eLawnMust]

If it's so buggy/crashy it should be an alpha... boy the term 'beta' has changed alot during the years...

The problem is that DAW developers are doing the same as video game developers... Namely getting lazy... "Just get it out the door, we'll fix whatever problems as they arise & we get feedback"... This is the fault of MODERN internet fast speed & convenient downloading... Thus no matter what 'final' you are using it's always still a 'beta' to be fixed in modern times all you can buy is a beta...

This is why 25 year-old code is much better, back then they could not take this lazy attitude... Since most all offerings were mailed out on CDs or sent to software distributors it HAD to be right the FIRST time!... the First time otherwise they were 'done'

[Caine123]

checking the BETA topic i always see lots of bugs/crashes and also use sometimes new BETAs to test and wonder why it is so buggy until RC releases. so i wonder are other DAWs new versions a buggy process as well?

You do know what a beta phase is?

yes, i meant not the beta/alpha, i see a lot of reoccuring bugs and many new bugs with each new release, wondering if it might be the old code from FL Studio they are cleaning up to open up FL Studio to fundamental features causing this or if it is just normal like in other DAWs, nothing more.

[osiris]

It would also be great if Microsoft could get it together with the Midi 2.0 implementation.

[Yorrrrrr]

One of the (many) reasons I left FL Studio is how buggy and unreliable the software is (in my experience), especially on MacOS platform. I imagine what the situation would be, currently, with all those betas, and the many features and changes bolted in to that old Windows-centric codebase. That said, I haven't found as many bugs in Ableton betas as I found in the past in FL release versions (again, on MacOS).

[pough]

The more the software does, the more places there are in the code to have bugs. The more users you have, the more different configurations and use cases there are and with that more bugs will be found.

I don't recall seeing any perfect rollouts of anything, ever. If you install a new version of something and have no troubles, it's far more likely to be luck than competence. Note that I'm not presenting a binary condition; there can be some competence issues and there can be more comprehensive testing phases pre-rollout.

[Trancit]

This is a vicious cycle here you cannot compare to any other DAW atm...

Users want to have a "different" FL Studio than it is and was meant to be with millions of features the code never was made for.

This means a very deep dive into the basic code of the whole programm with a complete rewrite...
This means of cause a whole lot of unexpected behaviour during this phase as new code sections and still old remains of the programm must work together for this period of time which already goes that way since at least 5 years in a more intense way and will probably go on for another 5 years.

Every software running through such a process would be more unstable than everything else not being reconstructed... this is simply the price you have to pay in this situation...
It would be nice without but "unexpected" is by definition not foreseeable so it will always happen.

And I think the IL devs do already a very good job as after the beta phases the programm is already quite stable for such deep cuts they have made...

Participation at the beta phases is voluntary... so imho nobody has the right to claim a beta would be to buggy and actually more an alpha...
This is the devs decision when to put out what and when they do not progress without or it simply helps to put the version out in this state they will have their reasons...
You don´t like it... > don´t install it... period!

You want more features in FL Studio... be patient and live with what you got atm... and again... the offcial releases are far from being "unuseable" so many claim on a very high level...

I.e. Ableton has a very unstable years lasting phase at V9 too for example... it took a very very long time to come back to an acceptable level... so it´s nothing new in software world.

[Caine123]

This is a vicious cycle here you cannot compare to any other DAW atm...

Users want to have a "different" FL Studio than it is and was meant to be with millions of features the code never was made for.

This means a very deep dive into the basic code of the whole programm with a complete rewrite...
This means of cause a whole lot of unexpected behaviour during this phase as new code sections and still old remains of the programm must work together for this period of time which already goes that way since at least 5 years in a more intense way and will probably go on for another 5 years.

Every software running through such a process would be more unstable than everything else not being reconstructed... this is simply the price you have to pay in this situation...
It would be nice without but "unexpected" is by definition not foreseeable so it will always happen.

And I think the IL devs do already a very good job as after the beta phases the programm is already quite stable for such deep cuts they have made...

Participation at the beta phases is voluntary... so imho nobody has the right to claim a beta would be to buggy and actually more an alpha...
This is the devs decision when to put out what and when they do not progress without or it simply helps to put the version out in this state they will have their reasons...
You don´t like it... > don´t install it... period!

You want more features in FL Studio... be patient and live with what you got atm... and again... the offcial releases are far from being "unuseable" so many claim on a very high level...

I.e. Ableton has a very unstable years lasting phase at V9 too for example... it took a very very long time to come back to an acceptable level... so it´s nothing new in software world.

yeah this is also what i suspect for a very long time. and when checking adding more mixer tracks (of course more features too) there are a lot of reoccuring and new crashes/errors.
of course a beta should always be used for testing, whoever doesnt do it should read more carefully .

so yeah also IL seems to also have added many more people to their team and it seems all old code needs to get rewritten and puts more bugs up, so far FL24 is quite stable on me, maybe the most stable one.

as i said i only got longtime experience with FL Studio and see a great progress, but just was wondering if it is with other DAWs as well (nothing is bugfree and 100% stable i know).

cannot wait for the next beta, Warping (i guess!) seems to be the next big feature (for me!)

[pc2000]

One of the (many) reasons I left FL Studio is how buggy and unreliable the software is (in my experience), especially on MacOS platform. I imagine what the situation would be, currently, with all those betas, and the many features and changes bolted in to that old Windows-centric codebase. That said, I haven't found as many bugs in Ableton betas as I found in the past in FL release versions (again, on MacOS).

Nothing more buggy than waveform!

[Trancit]

...
as i said i only got longtime experience with FL Studio and see a great progress, but just was wondering if it is with other DAWs as well (nothing is bugfree and 100% stable i know).

...

From my experience aren´t any bigger problems with nearly any other DAW...

Where I am always very careful is Tracktion Waveform which was always for me a huge crash fest in conjunction with 3rd party plugins but the usual candidates like:
- Reaper
- Ableton
- Bitwig
- Cubase
- Studio One
(these are the ones I have worked with in the younger past)
- and most likely Logic
might have the one or the other (longtime) problem/shortcoming/bug (like i.e. Ableton´s latency compensation) but nothing showstopper alike and of course with a more tested code base...

If I would need to rely on a stable DAW because of a tight timeline or similar, most likely I would take atm FLS just for parts of the work which I really need from it and would settle for the moment on something like Bitwig or Ableton for the main work to wait until the biggest work on FLS´rewrite is done.
Afterwards I would decide if I go back to FLS once mainly done (depending how it works and offers then) or if I stay with my "alternative" DAW...

[andypryce]

Users want to have a "different" FL Studio than it is and was meant to be with millions of features the code never was made for.

This I do not understand. Some users find for example Cubase old, bloated and not cool(whatever that is) but at the same time most features they request in FL come from Cubase, or Logic etc. Go figure.
I once saw a long feature request list from a user that was basically describing Cubase. At that point why not just use Cubase? lol

[mjolnir]

hi guys, no trolling here, still FL Studio user since day one, i dont have the long year experience with other DAWs as i started to use Ableton/Bitwig not very long ago.

Am glad that FL Studio gets finally crucial updates but checking the BETA topic i always see lots of bugs/crashes and also use sometimes new BETAs to test and wonder why it is so buggy until RC releases. so i wonder are other DAWs new versions a buggy process as well?

just checking people who follow Cubase, Logic and oter DAW processes.

betas, in general, by definition, are buggy. They are pre-release editions. They are distributed in small quantities so the end users and other beta testers can find the bugs and report the bugs to get them fixed. alphas are worse, but hey, they're not meant for the general population yet (alphas or betas).

Reaper's forum has a pre-release section also, where people can download new editions to test them. It's constant bugs. That's not a problem for either FL Studio or for REAPER. Computer Science is just that way.

It's like a mechanic needs somebody to test the vehicle to see if the repairs worked. But it's not ready for the consumer to drive yet--that's beta testing, sorta kinda like. You can't safely drive on those, but it's not the mechanic's fault. It's not the designer's fault--it's just NOT DONE YET.

[jamcat]

Like everyone else, I just checked this thread to see which DAW was being talked about