d16 Group LUSH-2 coming in June 2023

[seangm]

I have several (untagged) 3rd party sound banks for L101 that I can import to L2 (which is great), but when they are imported and converted to the new format they are also dumped into the same folder as my own presets. Preset name clashes are now a thing, and it's messy af.

If you don't mind can you tell me how you are importing your 3rd party Lush V1 presets into V2? I have been trying to do that and getting nowhere with it, V2 doesn't recognize any of my V1 presets. Did you need to convert them somehow? Thanks.

[skyman88882002]

With windows I just found my old presets folder, I selected all the presents and drag and dropped them on top of the Lush-2 present browser. It then automatically converted them to v2 presets and made them available on the Lush-2 presets browser.

[seangm]

With windows I just found my old presets folder, I selected all the presents and drag and dropped them on top of the Lush-2 present browser. It then automatically converted them to v2 presets and made them available on the Lush-2 presets browser.

Awesome, thanks.

[DrGonzo]

6 months into 2023 you come around wanting me to spring $45 to be able to use it again. Not fair, bruh. Yeah I'm a little bitter about that. And how long until it breaks again?

From that perspective, it does suck. But D16 is not the only ones with this issue. Native Instruments, Waves etc are good examples of where you have to pay for an update to get to use the same version but on a different OS. At least D16 brings a new version with new presets.

[Daru925]

The new gui doesnt include that custom ultra rare fluo green with pink text sh 101 i saw in shibuya. My day is ruined.


Very happy with lush 2 so far.
Seriously right click -> Host auto on any param, spend 15 min creating a basic starter template that works for you, (and then some for more layers), save it, remember it as a little hassle and then the true fun begins.

[zvenx]

.......

I stopped using Lush in 2020 because it stopped working on my OS. Yes, my fault for using a Mac and updating my OS, blah blah, ........................and now 6 months into 2023 you come around wanting me to spring $45 to be able to use it again. Not fair, bruh. Yeah I'm a little bitter about that. And how long until it breaks again?

Hmmmm...
I am a also mac user but it is a given that part of the 'joy's of macs is that os updates will break software..
Is it that you have to pay for the upgrade or is it that it is $45 that is your bitter?
Surely it is a bit entitled to expect developers to keep updating to follow mac os's with them always having to bear the cost of that update.

rsp

[hurricaneaudiolab]

.......

I stopped using Lush in 2020 because it stopped working on my OS. Yes, my fault for using a Mac and updating my OS, blah blah, ........................and now 6 months into 2023 you come around wanting me to spring $45 to be able to use it again. Not fair, bruh. Yeah I'm a little bitter about that. And how long until it breaks again?

Hmmmm...
I am a also mac user but it is a given that part of the 'joy's of macs is that os updates will break software..
Is it that you have to pay for the upgrade or is it that it is $45 that is your bitter?
Surely it is a bit entitled to expect developers to keep updating to follow mac os's with them always having to bear the cost of that update.

rsp

Sure some OS updates break software, but I don't remember any of my other synths being out of commission for 2.6 years.

[Kokoala]

Demo:

[kunonagel]

Does anyone know that the upgrade price will stay the same even after the “intro price?”

[neverbeeninariot]

I have several (untagged) 3rd party sound banks for L101 that I can import to L2 (which is great), but when they are imported and converted to the new format they are also dumped into the same folder as my own presets. Preset name clashes are now a thing, and it's messy af.

If you don't mind can you tell me how you are importing your 3rd party Lush V1 presets into V2? I have been trying to do that and getting nowhere with it, V2 doesn't recognize any of my V1 presets. Did you need to convert them somehow? Thanks.

skyman8888200's earlier answer is correct, drag and drop from explorer/finder (or from your daw's media browser, which worked in reaper at least).

Bear in mind that they will all be dumped into the same folder, untagged - so might be worth either doing them in batches and tagging them after import, or renaming before importing, or a combination of both.

[pepelogu]

Lush2 doesn't remember the GUI settings it seems. A bug maybe?

[zvenx]

.......

I stopped using Lush in 2020 because it stopped working on my OS. Yes, my fault for using a Mac and updating my OS, blah blah, ........................and now 6 months into 2023 you come around wanting me to spring $45 to be able to use it again. Not fair, bruh. Yeah I'm a little bitter about that. And how long until it breaks again?

Hmmmm...
I am a also mac user but it is a given that part of the 'joy's of macs is that os updates will break software..
Is it that you have to pay for the upgrade or is it that it is $45 that is your bitter?
Surely it is a bit entitled to expect developers to keep updating to follow mac os's with them always having to bear the cost of that update.

rsp

Sure some OS updates break software, but I don't remember any of my other synths being out of commission for 2.6 years.

Ahh so it is the 2.6 years.. got ya.
(Lexicon had similar issues but not sure of the time frame between issue and fix).
rsp

[zvenx]

Lush2 doesn't remember the GUI settings it seems. A bug maybe?

After you choose your desired gui you have to do save current in the default state (it also saves I believe cpu usage, real vs offline)

rsp

[m00gie]

[Deleted]

[bld]

Lush2 doesn't remember the GUI settings it seems. A bug maybe?

After you choose your desired gui you have to do save current in the default state (it also saves I believe cpu usage, real vs offline)

rsp

Correct, it saves also all the parameters, automation, CC map - whole plugin's state. And this state is loaded with each new instance.