nvm

[El°HYM]

nvm

[Held]

How would CLAP improve the Melda plugins?

[operator]

How would CLAP improve the Melda plugins?

Just to name one:

Loaded Audio-Files (resources) inside the Sampler could be saved within the DAW-Project... Therefore Sampler could be used like a "native/quick" Sampler without the need of everytime assigning a Samplebank and saving it in the project directory to have all used Audio-Files saved inside the Project-Folder. All loaded Samples/resources would just be saved within the Project as long as they are present in the Sampler or the Project.

This would transform THE best Sampler on the market to a "workflow-powerhouse". This would save immense time on my side... despite the circumstances I use it as "native" Sampler --> but my mind is slowly getting mad doing this "assigining Samplebank" process with every single file I insert/resample in my project.

I often use the function "delete unused files from project" in my DAW and this often deletes resampled files from inside my project which I then only had stored in the Sampler --> why keep a copy in my project if I have it in the Sampler?

I sometimes forget to assign Samplebank during being creative... and therefore loosing my whole process after "delete unsused files from project"... I am not a

[Boone777]

How would CLAP improve the Melda plugins?

On Linux currently I cant use MDrummer or MSoundfactory extensively (Via MXXX). It crashes.
All other plugins in MXXX work great under wine but, I much much prefer staying native to linux for stability and frankly, MXXX is all I need.

[Held]

How would CLAP improve the Melda plugins?

Just to name one:

Loaded Audio-Files (resources) inside the Sampler could be saved within the DAW-Project... Therefore Sampler could be used like a "native/quick" Sampler without the need of everytime assigning a Samplebank and saving it in the project directory to have all used Audio-Files saved inside the Project-Folder. All loaded Samples/resources would just be saved within the Project as long as they are present in the Sampler or the Project.

VST2/3 can do this as well. Atlas offers the option to save sample files in the project file, for example.

On Linux currently I cant use MDrummer or MSoundfactory extensively (Via MXXX). It crashes.
All other plugins in MXXX work great under wine but, I much much prefer staying native to linux for stability and frankly, MXXX is all I need.

CLAP doesn't automatically Linux support. There are already Windows only CLAP plugins available.

[Boone777]

I thought one of the point of CLAP was easy port, meaning it would make sense to have it available in every formats. Not so simple it seems...oh well.

[Held]

I thought one of the point of CLAP was easy port, meaning it would make sense to have it available in every formats. Not so simple it seems...oh well.

The most challenging part about multi-platform development is the GUI and CLAP doesn't help with that at all.

[MeldaProduction]

I thought one of the point of CLAP was easy port, meaning it would make sense to have it available in every formats. Not so simple it seems...oh well.

The most challenging part about multi-platform development is the GUI and CLAP doesn't help with that at all.

Very true.
Personally I don't get the reason for CLAP in the first place. So I'm definitely not going to allocate any dev time until important DAWs like FL, Reaper, Cubase, Logic... implement it.

[operator]

So I'm definitely not going to allocate any dev time until important DAWs like FL, Reaper, Cubase, Logic... implement it.

Yes, put the time/focus where it`s needed/best rewarded.


BTW, Reaper will release CLAP support in the next days... it is already in the current ReleaseCandidate. UnrealEngine, AVID and FL are interested and probably are working on it rn...

Cubase, Ableton and Logic [the old farts] will join when they don´t have any other option. Luckily we are in a time where those 3 DAWs don´t have the last say...

[n9research]

Personally I don't get the reason for CLAP in the first place. So I'm definitely not going to allocate any dev time until important DAWs like FL, Reaper, Cubase, Logic... implement it.

direct polyphonic modulation of all automation parameters is a pretty compelling reason

which bitwig can control, polyphonically, with its plugin-attached modulation devices and, via 4 discrete channels, the piano roll

as it stands, with MSF as vst, one can only get 2 channels of poly-mod into it. so as a BWS user, and being very enthusiastic about the potential for better expression in sounds using these capabilities, MSF in CLAP format (implementing those modulation connections) would be great news for me.

I find I am reaching first for synths in that format (or the BWS internals) when I want to work on sounds that would benefit from per-note control (which is most of the time these days)

Surge XT is a much more interesting synth now it's been released in CLAP! Bazille has been released, Zebra 3 will (I think..) debut with it, and VCV Rack Pro has just been released in CLAP format too

granted, it's just bitwig, which is niche, but I find it likely that user demand will build up across the more widely used platforms to up their modulation game, and to support plugin standards that get it to the instruments

MIDI 2.0 is slowly emerging too, of course

[mabian]

Beside additional feature, CLAP is a cool way out from Steinby and Avidy monopoly. I know these can't be dismissed, but as more and more developers embrace it the pressure will increase on those proprietary (fakely open since they can close anytime) formats.
And, as mentioned earlier, at least another big DAW is getting it quite soon.
Not amazed at all about the Melda reaction "Personally I don't get the reason for CLAP in the first place.".

- Mario

[chk071]

I thought one of the point of CLAP was easy port, meaning it would make sense to have it available in every formats. Not so simple it seems...oh well.

The most challenging part about multi-platform development is the GUI and CLAP doesn't help with that at all.

Very true.
Personally I don't get the reason for CLAP in the first place. So I'm definitely not going to allocate any dev time until important DAWs like FL, Reaper, Cubase, Logic... implement it.

That's the thing, innit? Another format to support, more work for the devs. That's basically what these new formats achieve.

Cubase and Nuendo (and probably Wavelab as well, when they decide to drop VST2 in it, and that has an even bigger market share on the audio editor market) are going nowhere. They have one of the biggest market share of the DAW's, and devs will have to support them in the future to have a piece of that market, so, CLAP or not, VST3 will still have to be supported, which simply means that devs will have to suppoort another format, IF all the mainstream DAW's adopt it.

[El°HYM]

nvm

[chk071]

The transition from 32- to 64-bit was absolutely essential, like the transition from VST2 to VST3, when DAW's stop to support VST2, as it is foreseeable. Unlike the transition to CLAP.

But, hey. Let's see who will adopt CLAP in the future. So far it's Bitwig only, and Reaper supports it in a developer version.

If you want my guess: It will be a long until most developers will release CLAP versions of their plugins. And it will never replace VST or any other format. It's funny how the guys behind it think they can conquer the world, when they know so well how slow things are developing in the audio software industry.

Urs once posted something about how new standards just lead to yet another standard to support. Did you know that? Obviously he forgot about it, or changed his mind in the meantime.

[El°HYM]

nvm