LuSH-101

[Echoes in the Attic]

Why aren't parameters automatable? Is there a setting to enable them somewhere?

A demo limitation I think...

I don't think this is a demo limitation. I have a copy and all I get for parameter automation is parameter 1 - 100. No labels. Furthermore they don't seem to do anything.

Then there must be a way to assign automation parameters. Nobody would take seriously a synth that can't automate anything.

[Keef Baker]

Why aren't parameters automatable? Is there a setting to enable them somewhere?

A demo limitation I think...

I don't think this is a demo limitation. I have a copy and all I get for parameter automation is parameter 1 - 100. No labels. Furthermore they don't seem to do anything.

I wish I had the time to play some more presets. When you have more than 15 minutes (and it took me a good few weeks to really get used to it) you can come up with some really nice sounds.

You have to select the ones you want to automate in options. Because there's a limit to the amount of parameters in a vst and with 8 layers there can be way waaaay over the amount the vst standard can handle.

[metrosonic]

Why aren't parameters automatable? Is there a setting to enable them somewhere?

A demo limitation I think...

I don't think this is a demo limitation. I have a copy and all I get for parameter automation is parameter 1 - 100. No labels. Furthermore they don't seem to do anything.

I wish I had the time to play some more presets. When you have more than 15 minutes (and it took me a good few weeks to really get used to it) you can come up with some really nice sounds.

The automation system works in much the same way as NI's Kontakt. You need to allocate a a function to one of the paramater slots on the paramaters page within settings - ie layer 1 VCF Frequency to paramater slot 1. The paramater will then publish to your host and will be fully automatable. It may at first seem a PITA but with an instrument with so many potential automatable paramaters this is a very slick solution - it certainly tames the way I work with Kontakt.

JM
------------
https://soundcloud.com/leftside-wobble

[satak]

Oh... One thing I don't like... Multiple notes of the same note with no break means it doesn't trigger the envelope.

That needs fixing, or at least being made optional.

It took me a while to figure that one out, but actually you can have the envelopes retrigger on every note. Next to the envelopes you'll find a bunch of LEDs under Reset, select "trig" instead of the default "gate" and you're good to go.

It is not working in FL Studio when you have polyphony 1.

[KBSoundSmith]

Oh... One thing I don't like... Multiple notes of the same note with no break means it doesn't trigger the envelope.

That needs fixing, or at least being made optional.

It took me a while to figure that one out, but actually you can have the envelopes retrigger on every note. Next to the envelopes you'll find a bunch of LEDs under Reset, select "trig" instead of the default "gate" and you're good to go.

It is not working in FL Studio when you have polyphony 1.

Under the section "Amp" next to Env1, select the trigger LED.

[BDeep]

Oh... One thing I don't like... Multiple notes of the same note with no break means it doesn't trigger the envelope.

That needs fixing, or at least being made optional.

It took me a while to figure that one out, but actually you can have the envelopes retrigger on every note. Next to the envelopes you'll find a bunch of LEDs under Reset, select "trig" instead of the default "gate" and you're good to go.

It is not working in FL Studio when you have polyphony 1.

In the options you can set the retrig behaviour to normal or sh101. Maybe changing that works, mine is set to normal.

[pdxindy]

Why aren't parameters automatable? Is there a setting to enable them somewhere?

A demo limitation I think...

I don't think this is a demo limitation. I have a copy and all I get for parameter automation is parameter 1 - 100. No labels. Furthermore they don't seem to do anything.

I wish I had the time to play some more presets. When you have more than 15 minutes (and it took me a good few weeks to really get used to it) you can come up with some really nice sounds.

The automation system works in much the same way as NI's Kontakt. You need to allocate a a function to one of the paramater slots on the paramaters page within settings - ie layer 1 VCF Frequency to paramater slot 1. The paramater will then publish to your host and will be fully automatable. It may at first seem a PITA but with an instrument with so many potential automatable paramaters this is a very slick solution - it certainly tames the way I work with Kontakt.

That does not seem slick to me... All my other synths I simply move a control while recording and done... here I have to go set up each and every parameter I might want to move while recording?? That is a big big downer... no spontaneity possible


edit: and I doubt that Lush with its 8 layers has appreciably more automatable parameters than Zebra

[metrosonic]

The automation system works in much the same way as NI's Kontakt. You need to allocate a a function to one of the paramater slots on the paramaters page within settings - ie layer 1 VCF Frequency to paramater slot 1. The paramater will then publish to your host and will be fully automatable. It may at first seem a PITA but with an instrument with so many potential automatable paramaters this is a very slick solution - it certainly tames the way I work with Kontakt.

That does not seem slick to me... All my other synths I simply move a control while recording and done... here I have to go set up each and every parameter I might want to move while recording?? That is a big big downer... no spontaneity possible

The reason it works this way is that the VSTi spec only allows for a maximum of 128 automatable paramaters (a hangover from the ancient midi spec we're all still working with). With a synth as complicated as LuSH-101 (which is in effect 8 separate synths) you need a way to manage which of the multitude of available parameters get published to your DAW. D16 are not the only manufacturer to have to work in this manner. Once you get used to the workflow its a very simple, efficient & powerful way of working. Unfortunately it's a necessary workflow for an instrument with so vast a number of automatable paramaters.

And if your looking for spontaneity, simply map a selection of your preferred parameters to your midi controller and tweak away.

JM
------------
https://soundcloud.com/leftside-wobble

[Echoes in the Attic]

Because there's a limit to the amount of parameters in a vst and with 8 layers there can be way waaaay over the amount the vst standard can handle.

This isn't really true. There aren't that many parameters per layer. Even with all 8 layers, it would still fit in the allowable amount of VST parameters. Many VSTs have hundreds upon hundreds. The only reason a VST might limit it and have them assignable is in case of hosts that can only recognize a limited number of parameters. Ableton Live used to be like this, it only saw the first 128, but now you specify which parameters should be enabled from live itself. I'm not sure what other hosts might have a limitation like that, I didn't think any did anymore.

[metrosonic]

Because there's a limit to the amount of parameters in a vst and with 8 layers there can be way waaaay over the amount the vst standard can handle.

This isn't really true. There aren't that many parameters per layer. Even with all 8 layers, it would still fit in the allowable amount of VST parameters. Many VSTs have hundreds upon hundreds. The only reason a VST might limit it and have them assignable is in case of hosts that can only recognize a limited number of parameters. Ableton Live used to be like this, it only saw the first 128, but now you specify which parameters should be enabled from live itself. I'm not sure what other hosts might have a limitation like that, I didn't think any did anymore.

Ableton Live is one of the few DAW's to handle paramater automation in such a slick manner - hence it's my DAW of choice but instrument designers have to take into account all platforms/operating systems/DAW's etc.

JM
------------
https://soundcloud.com/leftside-wobble

[Aiynzahev]

Why aren't parameters automatable? Is there a setting to enable them somewhere?

A demo limitation I think...

I don't think this is a demo limitation. I have a copy and all I get for parameter automation is parameter 1 - 100. No labels. Furthermore they don't seem to do anything.

I wish I had the time to play some more presets. When you have more than 15 minutes (and it took me a good few weeks to really get used to it) you can come up with some really nice sounds.

You have to select the ones you want to automate in options. Because there's a limit to the amount of parameters in a vst and with 8 layers there can be way waaaay over the amount the vst standard can handle.

Oh yes sorry, I remember seeing that in the manual now.

[Echoes in the Attic]

The reason it works this way is that the VSTi spec only allows for a maximum of 128 automatable paramaters (a hangover from the ancient midi spec we're all still working with).

This simply is not true at all. Most of my synths have waaayyy more than 128 automatable parameters. Some have near to a thousand, like Zebra or FM8.

I don't know where you're getting this idea from. Ableton Live had a limitation of 128 because of it's own limitation, not VSTs. If VSTs had a limitation of 128 parameters, then Ableton never would have had to allow configuration to automate the parameters beyond the 128th would it? And yes many DAWs do not have this 128 limit that Ableton Live has. Most DAWs allow access to all a plug-ins parameters.

I have several VSTs with more automatable parameters than Lush-101 would have if it had all parameters automatable at once so that argument doesn't really make sense either.

[metrosonic]

The reason it works this way is that the VSTi spec only allows for a maximum of 128 automatable paramaters (a hangover from the ancient midi spec we're all still working with).

This simply is not true at all. Most of my synths have waaayyy more than 128 automatable parameters. Some have near to a thousand, like Zebra or FM8.

I don't know where you're getting this idea from. Ableton Live had a limitation of 128 because of it's own limitation, not VSTs. If VSTs had a limitation of 128 parameters, then Ableton never would have had to allow configuration to automate the parameters beyond the 128th would it? And yes many DAWs do not have this 128 limit that Ableton Live has. Most DAWs allow access to all a plug-ins parameters.

I have several VSTs with more automatable parameters than Lush-101 would have if it had all parameters automatable at once so that argument doesn't really make sense either.

Cool, you're right and I'm wrong lets leave it at that. I was only try to help somebody work out the automation system on LuSH-101 and thought it might be helpful to provide some background info but if want to turn it into a pissing contest so be it...

JM
------------
https://soundcloud.com/leftside-wobble

[Echoes in the Attic]

Cool, you're right and I'm wrong lets leave it at that. I was only try to help somebody work out the automation system on LuSH-101 and thought it might be helpful to provide some background info but if want to turn it into a pissing contest so be it...

Being helpful is good. Providing background info is good to, just not if it's made up.

[grymmjack]

This is a stunning product.

D16: Please allow a right click option on the control to map to the VST parameter, this would make it much easier/faster to map the controls, or at least give us a basic default map