KVR Audio

Arashi · Post by **Arashi** » Thu Jul 28, 2022 4:20 am

DRMR wrote: Wed Jul 27, 2022 5:44 am
Arashi wrote: Wed Jul 27, 2022 4:23 am There's always MIT.
How is that relevant? You can't publish a project under MIT license if it uses the Steinberg-GPL license.

I was referring to "A free (as in freedom) format is needed."

DRMR · Post by **DRMR** » Fri Jul 29, 2022 3:52 pm

Arashi wrote: Thu Jul 28, 2022 4:20 am I was referring to "A free (as in freedom) format is needed."

A license does not a format make, but yes we have MIT and ISC licensed formats that are suitable for actual free usage. So lets use them!

EvilDragon · Post by **EvilDragon** » Sat Jul 30, 2022 12:12 pm

Quote from pottering in that JUCE issue seems to completely resolve the quandary.

Bombadil · Post by **Bombadil** » Sat Jul 30, 2022 12:44 pm

Tetracycline doesn't work anymore.
Or so I've read.

S0lo · Post by **S0lo** » Tue Aug 02, 2022 10:40 am

As poly modulation goes. Do users expect to also have manual control of parameters per voice (and consequently poly automation). I mean, we can do it. But it will complicate things even further for the user. May be border line confusing?

I don't know. Is it worth it? Does it make sense from a user perspective?

Urs · Post by **Urs** » Tue Aug 02, 2022 11:21 am

I don't think that's the case. If a host lets one draw individual automation-style regions per voice, that's what the host would do.

S0lo · Post by **S0lo** » Tue Aug 02, 2022 11:30 am

O, thats not really what I meant Urs. It does make sense from host side. Edit: and so for CLAP to provide it.

I mean do users expect the UI of the plugin it self to provide manual control of the parameters per voice.

Edit: my English is apparently terrible.

Tj Shredder · Post by **Tj Shredder** » Tue Aug 02, 2022 11:39 am

I don’t think so. As a user tinkering with parameters is more like on any other synth for all voices.
The only polyphonic synth in history and also as plugin that allows that, is the ancient Oberheim 8-voice. If you really need that, better load the amount of instances (like the hardware version of the OB8) and route your Midi channels accordingly. In Bitwig and in Unify that would be easy…
Per voice modulation is for the subtleties. My finger is too coarse for that…

Urs · Post by **Urs** » Tue Aug 02, 2022 11:45 am

S0lo wrote: Tue Aug 02, 2022 11:30 am O, thats not really what I meant Urs. It does make sense from host side.

I mean do users expect the UI of the plugin it self to provide manual control of the parameters per voice.

Edit: my English is apparently terrible.

Yes, that's what I meant, but I might have jumped one corner too many. Nobody expects that (manual control over parameters per voice) as it would generally be a terrible user experience.

That said, *some* control over voice differences can be a good thing, but one really needs to get a good balance between benefit and user experience.

S0lo · Post by **S0lo** » Tue Aug 02, 2022 12:04 pm

Urs wrote: Tue Aug 02, 2022 11:45 am That said, *some* control over voice differences can be a good thing, but one really needs to get a good balance between benefit and user experience.

Yeah, I was thinking of a hidden right click menu to select the voice for whoever happens to want this.

baconpaul · Post by **baconpaul** » Tue Aug 02, 2022 12:11 pm

S0lo wrote: Tue Aug 02, 2022 12:04 pm
Urs wrote: Tue Aug 02, 2022 11:45 am That said, *some* control over voice differences can be a good thing, but one really needs to get a good balance between benefit and user experience.
Yeah, I was thinking of a hidden right click menu to select the voice for whoever happens to want this.

So I think most polysynths represent voice level changes as modulation. For instance, surge has a lot of ways to control differences per voice - that's the whole mod matrix!

I have, though, thought about making voice level macros in surge in a future version. This would allow you to have voice-level items which can be shared entry points into the mod matrix and I think it would be super neat. But it's a moderate re-work.

I really think of automation as 'move the knob' though and there's only one knob (even though the spec supports voice level automation indeed).

Interesting discussion though. I'll ponder it.

moss · Post by **moss** » Tue Aug 02, 2022 12:13 pm

Reaper supports CLAP!
https://forum.cockos.com/showthread.php?t=269287

Tj Shredder · Post by **Tj Shredder** » Tue Aug 02, 2022 12:36 pm

How long did it take after the release of VST3 that the first host (excluding Cubase) appeared to support it, and how long did it take until the first 3rd party VST3s appeared?
Just wondering…
According to this thread in 2011 only Studio one and NTrack supported it…
https://gearspace.com/board/music-compu ... st3-2.html
Studio one started one year after the release of VST3 (2008). Did it support VST3 from the beginning…?

pdxindy · Post by **pdxindy** » Tue Aug 02, 2022 12:54 pm

S0lo wrote: Tue Aug 02, 2022 10:40 am As poly modulation goes. Do users expect to also have manual control of parameters per voice (and consequently poly automation). I mean, we can do it. But it will complicate things even further for the user. May be border line confusing?

I don't know. Is it worth it? Does it make sense from a user perspective?

That's what MPE is... As a user, I have manual control of parameters via Velocity, Pressure, Pitch (X axis), Timbre (Y axis) and Release Velocity on a per note basis.

rafa1981 · Post by **rafa1981** » Tue Aug 02, 2022 1:04 pm

moss wrote: Tue Aug 02, 2022 12:13 pm Reaper supports CLAP!
https://forum.cockos.com/showthread.php?t=269287

Nitpick. Reaper has added Clap to the pre-release builds. Some features are there for a few weeks before landing on the official build. Others take months.

Having said that this is cool

CLAP... thoughts?