u-he

electro · Post by **electro** » Fri Sep 30, 2016 6:54 pm

Satin VST2 and Satin VST3 don't seem to be able to Gange controls to the same group. Is this intended?

Urs · Post by **Urs** » Sat Oct 01, 2016 9:30 am

electro wrote:Satin VST2 and Satin VST3 don't seem to be able to Gange controls to the same group. Is this intended?

They can't. The grouping feature only works for instances of the same plug-in format.

Is there a reason to use different plug-in formats for the same plug-in within a project?

electro · Post by **electro** » Sat Oct 01, 2016 12:17 pm

Good to know. Is the VST3 version now recommended over VST2?

EvilDragon · Post by **EvilDragon** » Sat Oct 01, 2016 12:27 pm

I think VST2 will continue to be recommended for quite some time to come...

Urs · Post by **Urs** » Sat Oct 01, 2016 2:42 pm

EvilDragon wrote:I think VST2 will continue to be recommended for quite some time to come...

Not necessarily. We consider the VST3 support of Satin and Presswerk very stable. The sluggishness of the previous implementation is gone, as far as we know. Only MIDI learn does not work yet, which is due to our "strictly-to-the-books" implementation of VST3.

u-he

KVR Audio

Satin Gange Bug?