Not-a-deal FL-Studio 21 Released

[Brian Lawler]

https://www.image-line.com/

There is a sale running until Jan 1

 

[projectm]

I was told I don’t need it…

 

Very good product video, tho?

[chris.r]

took them loooong to cook up some clip envelopes

but as usual (with other DAWs coming late), once they've done it, it looks and seems to work so much better than what we have in cakewalk

Edited December 7, 2022 by chris.r

[Brian Lawler]

Every time they do a new release I install and look it over again (gotta love the free update policy).  There are a ton of great features, but am I the only person that is completely put-off by the MIDI routing?  Assigning & tracking MIDI device numbers instead of using alpha tags? In version 21? MIDI hardware won't pass cc until you customize the settings.  Harrumph.  Or, in keeping with the season, Bah Humbug.

[kitekrazy]

1 hour ago, Brian Lawler said:

Every time they do a new release I install and look it over again (gotta love the free update policy).  There are a ton of great features, but am I the only person that is completely put-off by the MIDI routing?  Assigning & tracking MIDI device numbers instead of using alpha tags? In version 21? MIDI hardware won't pass cc until you customize the settings.  Harrumph.  Or, in keeping with the season, Bah Humbug.

I can't stand it.  Patcher is another way of doing it. I remember how difficult it was in Reaper at one time.

[kitekrazy]

They also give you the new stuff for free if you have the elite packages.

I'm finding some DAW developers are making quality proprietary plugins that equal many 3rd party plugins.

I also like to look at their demo song in a new release to see what is used. 

[Lee D]

Every release I get hyped about it, reinstall it and convince myself now I'll use it, then decide everything is so much more convoluted than other DAWs why am I bothering with the hassle and delete it

[Fleer]

Every release I consider reinstalling but don’t. 

[aidan o driscoll]

The one constant issue I find in flstudio is location of VST3 plugins CANNOT be anywhere else other than the default folder C:\Program Files\Common Files\VST3

If you have your VST3s anywhere else .. even if you add the alt folder to the plugin manager paths .. it wont find your VST3s 

Anyone find a solution to this? 

[kitekrazy]

1 minute ago, aidan o driscoll said:

The one constant issue I find in flstudio is location of VST3 plugins CANNOT be anywhere else other than the default folder C:\Program Files\Common Files\VST3

If you have your VST3s anywhere else .. even if you add the alt folder to the plugin manager paths .. it wont find your VST3s 

Anyone find a solution to this? 

Install VST3 to the default folder.   Plus you can get help on their forum.  

[TheSteven]

4 hours ago, aidan o driscoll said:

The one constant issue I find in flstudio is location of VST3 plugins CANNOT be anywhere else other than the default folder C:\Program Files\Common Files\VST3

If you have your VST3s anywhere else .. even if you add the alt folder to the plugin manager paths .. it wont find your VST3s 

Anyone find a solution to this? 

Put the alt folders in  C:\Program Files\Common Files\VST3
Such as...
C:\Program Files\Common Files\VST3\AAS
C:\Program Files\Common Files\VST3\Softube
C:\Program Files\Common Files\VST3\FabFilter
etc.
Don't have to add any folders to your scan paths and works across all Windows DAWs

Edited December 8, 2022 by TheSteven