Will Native Instruments release a JUCE framework alternative?

[discoDSP]

I was being facetious. NI hasn’t really demonstrated a pattern of benevolent open source code sharing. The few standards they’ve proposed and development frameworks they’ve released were always in the service of promoting their commercial offerings. The evolution of JUCE has been an entirely different path. Unless such an NI framework could be profitable enough to justify its release, or provided some other competitive advantage, I can’t imagine why they would do to it. Their internal development framework obviously represents a significant corporate asset, and investors probably wouldn’t be too happy if they decided to make it public.

I think NI is the Microsoft of audio industry and it would be a very smart move to embrace open source like MS did. JUCE is excellent however I bet NI has the best engineers or at least the highest paid ones. Getting an audio plugin development tool from them would be incredible for the whole dev community.

Sure, lots of reasons why that would be great for the dev community. Remind me again why it would be great for NI? Giving away their core IP sounds like something they’d jump at the opportunity to do!

Good karma. They are on a point where getting money isn't something to rely on.

[hibrasil]

Iplug2 is coming along nicely, not yet production ready though... https://github.com/iPlug2/iPlug2

[discoDSP]

Iplug2 is coming along nicely, not yet production ready though... https://github.com/iPlug2/iPlug2

Interesting. What's the viability to migrate a JUCE project to iPlug2? It doesn't support iOS from what I read.

[hibrasil]

How long’s a piece of string? juice has a more sophisticated observer pattern based widget system, where as iplug has quite simple classes for controls, which are easily linked to parameters. btw You can use juice ui on top of iplug 2 (instead of igraphics) if for some reason you don’t want to use Juces plugin wrappers

[hibrasil]

iOS is partly working but not public yet

[discoDSP]

Promising Can't wait to see what the public release brings.

[Topcheese]

I'm guessing it boils down to does JUCE make as much money as NI. and that answers your question.

[discoDSP]

I'm guessing it boils down to does JUCE make as much money as NI. and that answers your question.

That’s easy to compare

https://www.owler.com/company/native-instruments $100 million / year

https://www.owler.com/company/juce $7 million / year

[Youlean]

I think IPlug is really awesome, and Oli is doing a ton of work on it! IPlug is already a great alternative to Juce.

[wavesfactory]

I'm guessing it boils down to does JUCE make as much money as NI. and that answers your question.

That’s easy to compare

https://www.owler.com/company/native-instruments $100 million / year

https://www.owler.com/company/juce $7 million / year

That's not a reliable source. It says that Wavesfactory makes 3.8M per year
https://www.owler.com/company/wavesfactory

[Youlean]

I'm guessing it boils down to does JUCE make as much money as NI. and that answers your question.

That’s easy to compare

https://www.owler.com/company/native-instruments $100 million / year

https://www.owler.com/company/juce $7 million / year

That's not a reliable source. It says that Wavesfactory makes 3.8M per year
https://www.owler.com/company/wavesfactory

So, you are earning more?

[telecode]

I was being facetious. NI hasn’t really demonstrated a pattern of benevolent open source code sharing. The few standards they’ve proposed and development frameworks they’ve released were always in the service of promoting their commercial offerings. The evolution of JUCE has been an entirely different path. Unless such an NI framework could be profitable enough to justify its release, or provided some other competitive advantage, I can’t imagine why they would do to it. Their internal development framework obviously represents a significant corporate asset, and investors probably wouldn’t be too happy if they decided to make it public.

I think NI is the Microsoft of audio industry and it would be a very smart move to embrace open source like MS did. JUCE is excellent however I bet NI has the best engineers or at least the highest paid ones. Getting an audio plugin development tool from them would be incredible for the whole dev community.

Microsoft didn't "embrace" open source. They just jumped on the bandwagon to use the buzz word as a tool to sell other products under their product portfolio.

Anyways, so JUCE is a framework to build audio apps and VSTs? So is JUCE the quasi commercial equivalent of CLAM?

http://clam-project.org/

[Topcheese]

Anyways, so JUCE is a framework to build audio apps and VSTs? So is JUCE the quasi commercial equivalent of CLAM?

http://clam-project.org/

Seems like Chuck is probably closer is what it seems to me. I'm not sure how functional the VST bridge is for it.
http://chuck.cs.princeton.edu/

https://github.com/mtiid/chuck-racks

Edit: I'm not sure if this one counts, but you can at least create a vst plugins. Seems like this is closer to JUCE.
https://github.com/AuburnSounds/Dplug

[telecode]

Anyways, so JUCE is a framework to build audio apps and VSTs? So is JUCE the quasi commercial equivalent of CLAM?

http://clam-project.org/

Seems like Chuck is probably closer is what it seems to me. I'm not sure how functional the VST bridge is for it.
http://chuck.cs.princeton.edu/

https://github.com/mtiid/chuck-racks

Edit: I'm not sure if this one counts, but you can at least create a vst plugins. Seems like this is closer to JUCE.
https://github.com/AuburnSounds/Dplug

Really cool stuff. I wish I had the time to get into this kind of stuff.

[discoDSP]

Should NI framework be called Nektarin?