Splash screen for Personal JUCE 5 license?

OMG OMG OMG, what a lot of crazy over-reaction and panic!

Please ignore the FUD that the post title suggests - the splash screen is NOT “mandatory”!

It’s a new, additional option that some users may want to choose.

Up until now, if you didn’t want to use the GPL and you didn’t want to pay the license fee, then you simply couldn’t release a closed-source product with JUCE.

This just provides a new option that lets people do that. It does not replace or affect the GPL in any way. A GPL app does not need a splash screen, and it’s easy to disable it. And anyone who’s already a paying licensee won’t be affected by this at all.

But we get many emails from people who want to launch a closed-source product but have no budget, and this is a way for them to do that.

The rest of you, calm down and carry on!

7 Likes

So, users of the free model can release apps that are closed source, as long as they display the splash screen?

Perhaps a better planning of the newsletter and the overall communication will avoid this mess in the future.

A nice pinned post with all the details you want to disclose about the new version would have helped.

1 Like

There seems to be conflicting information, regarding AAX, between the newsletter and the website version (Apologies for the volume setting splash):

Fair enough, now that it’s clearer I’ve removed the word from the title.

The possibility of releasing closed source products even for developers with no budget is certainly welcome.

As mentioned by @Rory above, would you also consider slightly different means for showing the “Made with JUCE” claim? The observations and questions he made seem pretty reasonable to me.

I’ll add to that that, for someone not willing to display it in form of a splash screen, permanently adding a “badge” of specified minimum size to the GUI of the applicaton may be a more attractive alternative, possibly even more effective if said badge is a clickable “link” that launches the browser to “www.juce.com

The correct information is the one in the second table, with 4 columns, so AAX is included.

See: AAX support will be included in Indie for JUCE 5

I think the splash screen is better than a badge as it might encourage more users to buy an indie license to help contribute and fund further development… i think the ability to release products without releasing your source is a great way to encourage people to develop without any up front costs but they have to buy a license to stop annoying people once they’ve made a bit of cash…

just my thoughts

1 Like

Wow, so developers can release closed source apps just by displaying a splash screen? That’s quite generous. All the same, I’m more than happy to plug JUCE in my splash screens :wink:

2 Likes

Ah, fair enough. I think your point is correct and that a little bit of annoyance is needed to promote the upgrade to one of the paid licenses.

Still, it would be nice if ROLI could accept the merge of the information in their splash screen within another splash screen if the app already needs one, as @Rory proposed.

1 Like

That seems to be it, but only for developers or companies which make less than $50k per year.

How is this splash screen supposed to work? Each time the plugin gui is displayed or once per daw session / only first time the gui is openend?

So far, this sounds great:

  1. free live engine for all
  2. free closed source projects (with splash screen and under 50k)

Could we get some info on the “user interfaces” and maybe any improvements with components in the ProJucer?

i love you jules, sorry about that, btw i need your address want to send you a present

That addresses my last concern. I’ve considered it thoroughly and IMO these are fantastic licensing changes (after the AAX inclusion) that are really fair for all brackets of developers. I am more pumped than ever for the future of JUCE!

Though, I say that from the POV of a student who uses JUCE extensively for open source projects and shoves it on his co-workers, I haven’t shipped anything commercially…

The splash screen will only be displayed once per DAW session, per plug-in.

Since there seems to be a little bit of hysteria about this, let me reiterate what Jules has said: If you are a current JUCE customer you will not be affected by the splash screen.

  1. If you’re releasing open source JUCE software you can continue to release your open source software without a splash screen
  2. If you’re currently paying for JUCE to release a closed source product you can continue to pay for JUCE to release a closed source product without a splash screen

The splash screen only affects an exciting new free tier - If you want to release a closed source JUCE-based product, and your revenue/funding is less that $50k, you can do so for free using the Personal license, but you will need to display a splash screen.

7 Likes

@Jules @t0m - ok, so as I understand it, to use JUCE ‘free’ , either
a) I open source the code under GPL
b) have a personal license, with ‘made in juce’ splash screen

sounds fantastic to me :slight_smile:
(then for b… if its a success, I can move to an indie license)

how do I do set this up on a project by project basis?
I develop for a couple of existing open source projects which already use juce. (so (a)),
but I also on the same machine want to have a closed source project, under conditions of (b)

do I set something on the project? in projucer?

If you are using the GPLv3 or have an Indie or Pro license it’s configurable on a project-by-project basis in the Projucer; if you have a personal license then there’s no option to change it in the Projucer. You can use JUCE and the Projucer under the terms of the GPLv3 by changing the JUCER_ENABLE_GPL_MODE precompiler variable in Projucer’s AppConfig.h and building it yourself.

ok, so I can install as a personal license, then for GPL projects just change JUCER_ENABLE_GPL_MODE in AppConfig.h , sounds easy enough :slight_smile:

one other oddity, I assume the splash screen requirement, means we cannot release console based apps (Linux) under a personal license? (or does it have a console equivalent).

Ive a small non-gui Linux project, which ive been avoiding Juce due to the X11 dependency, and also I was undecided on GPL or not, Juce5 Personal looks like it possible solves both issues, but perhaps the splash screen is an issue.

If you have a console app then there’s a decent chance that all the modules you’re using are under the ISC license, which has no restrictions at all other than the usual disclaimer of all warranties…

The JUCE modules under the ISC license are juce_core, juce_events, juce_audio_basics, juce_audio_devices, juce_blocks_basics.

There have also been a lot of Linux improvements in JUCE 5, including removing the X11 dependency: X11, MIDI and other Linux improvements

1 Like

I have a personal license and am producing an open-source project. I don’t see the option to remove the splash screen for projects in Projucer 5.0.0. The only option I have for “Report JUCE app usage” and “Display the JUCE splash screen” is Required for closed source applications without an Indie or Pro JUCE license. What do I do to see the other options?

1 Like