FL Studio 2024.1 available... hehehe

[satYatunes]

The EQ also does the same thing. Very annoying to be honest.

[Trancit]

Am I missing something, or is there no way in FLS for a built in plugin (like say Sytrus) to REMEMBER how you resized it, the next time you load it? Seems like a pretty basic feature to miss...

It´s quite annoying but somehow they didn´t (or couldn´t) touch the preset system to save user resizing...
Once a plugin is resized in a project it´s state get saved in the project file but sadly not on load of new instances...
Seems to be a shortcoming of the .fst format for native plugins... perhaps some day...
At least they implement a scaling option now for the native ones which gets always remembered but still no new for resizing.

[xbitz]

^^^ Yes, the Patcher also needs to be resized; I cried and wrote about it myself.

[MrJubbly]

Am I missing something, or is there no way in FLS for a built in plugin (like say Sytrus) to REMEMBER how you resized it, the next time you load it? Seems like a pretty basic feature to miss...

[EDIT] - Never mind. I see from other posts, you were specifically referring to "resizing" rather than the new "scaling" feature. I mistook your query as relating to the latter, since that is the new feature currently being implemented in the beta.

The set once per plugin Scaling setting works for me.
Using the new beta, I set scaling for Sytrus to 400% (as I use a 4K display).

That was once only. And FLS has remembered that setting ever since (as it has for all the other native FL plugins that I assigned a custom scaling setting to also).

Perhaps, there's a bug if that's not currently working for your specific setup?

[EvilDragon]

I'm indeed doing resizing and not this new scaling thing, I don't have the beta installed. Either way, resizing should absolutely be serialized...

[Caine123]

Am I missing something, or is there no way in FLS for a built in plugin (like say Sytrus) to REMEMBER how you resized it, the next time you load it? Seems like a pretty basic feature to miss...

It´s quite annoying but somehow they didn´t (or couldn´t) touch the preset system to save user resizing...
Once a plugin is resized in a project it´s state get saved in the project file but sadly not on load of new instances...
Seems to be a shortcoming of the .fst format for native plugins... perhaps some day...
At least they implement a scaling option now for the native ones which gets always remembered but still no new for resizing.

also wrote that on their forums, thats one of the big points how FL Studio feels still so incoherent, plugins not all resizable (coming it seems step by step), doesnt recall gui size and much more.... but well lets see, since FL21 the direction is very promising, i dunno if they can keep up with the competition where thse things are already given years.

[MrJubbly]

Am I missing something, or is there no way in FLS for a built in plugin (like say Sytrus) to REMEMBER how you resized it, the next time you load it? Seems like a pretty basic feature to miss...

It´s quite annoying but somehow they didn´t (or couldn´t) touch the preset system to save user resizing...
Once a plugin is resized in a project it´s state get saved in the project file but sadly not on load of new instances...
Seems to be a shortcoming of the .fst format for native plugins... perhaps some day...
At least they implement a scaling option now for the native ones which gets always remembered but still no new for resizing.

also wrote that on their forums, thats one of the big points how FL Studio feels still so incoherent, plugins not all resizable (coming it seems step by step), doesnt recall gui size and much more.... but well lets see, since FL21 the direction is very promising, i dunno if they can keep up with the competition where thse things are already given years.

I'd give Image-Line the benefit of the doubt regarding such matters right now. Considering they are currently implementing new Scaling features to all the native plugins. Currently available and working very well for all their recently "vectorized" plugins. No doubt the rest will follow.

There has also been some discussion on their forums regarding implementing some quick short cut click and drag mouse gesture to the new Scaling feature, that wouldn't clash with the existing "resizing" method (for those plugins who currently support that). If there is to be some method to also save the "resized" settings for the plugins, similar to how the "scaling" method has been implemented (i.e. set once and then recalled by subsequent instances), it may come after this feature has been decided upon.

It may be beneficial to remind the devs while this beta testing phase is happening. That's usually when I have managed to sneak a few accepted suggestions in, i.e. while such related features are actively being worked on, rather than years before or after, which tend to then get lost/forgotten about.

[sQeetz]

still hoping for the plugin version of the in Delphi written stuff to be released as plugins anytime soon...

[ChanceB]

I don’t really use FL Studio these days much but i think it’s actually pretty exciting that they are finally getting to the Maxx Claster plugins,it really helps to add some perceived value back to the all plugins edition for me at least. I’m not sure why they aren’t resizable with a corner drag though,like sytrus etc.,but neither is Kepler exo. They could also use some gain normalization,compared to Harmor they are very quiet. More uniformity across Al of Fl is needed but it seems they are working towards that

[Inversion Of Control]

so 2024 version will install separetely than FL studio 21, and in 2025 I will have to install another version separetly?

[MrJubbly]

so 2024 version will install separetely than FL studio 21, and in 2025 I will have to install another version separetly?

Only if you want them to. You can install them separately into their default installation folders and have them all co-exist, side-by-side, if you want.

However, if you prefer to install v2024.x or any future v2025.x version "over the top" of a previous FL Studio installation. Just manually rename that existing folder from (for example) either "FL Studio 21" to "FL Studio 2024" or to "FL Studio 2025", etc., prior to installing the newer update.

Maybe, Image-line will even provide an option to do so within future installers. But if not, the method mentioned above should still work.

[osiris]

All my sounds are still in 21. 24 still shows everything in the Browser but I guess I should move them.

[Trancit]

All my sounds are still in 21. 24 still shows everything in the Browser but I guess I should move them.

What shall you move??

If you are talking about presets and nearly everything you can save in FLS:
They are stored by default in the "user data folder" which is shared amongst all versions... you don´t have to change or move anything!

If the browser in FLS 24 can see them why would you want to move them??

[Trancit]

so 2024 version will install separetely than FL studio 21, and in 2025 I will have to install another version separetly?

It was never any different... FL 11 had by default it´s own directory as well as FL 20,21 and FL 24...
You can always change that and install/overwrite every version in a single directory if you wish so...
That´s why the installer asks for the install directory with just making a suggestion for the new directory just to be save and not accidentally overwriting a previous installation...

Nothing wrong with that behaviour...

I would dislike if they wouldn´t ask like many others do and dictate an install directory i.e. like Bitwig did with their latest ".msix" stunt...but this will never happen with IL products! They respect that the user has the final choice...

[osiris]

Loops, kits,midis and acapellas.