[ARCHIVED] JUCE 8 EULA

We’ve seen a lot of progress in a week. It’s encouraging and thanks to Tom for his work during what has probably been a pretty stressful week getting it from all sides. A few more steps to go on some important topics but things are looking far better than they were a week ago in many respects.

17 Likes

yep. valiant effort from the team.

8 Likes

To the credit of the JUCE team, I think it can be said that they reacted quickly to the negative feedback, and promptly proposed viable solutions regarding at least some of the main points of concern.

Maybe, but as a beginner audio developer, I can’t justify $50/month in perpetuity or $1,000 up front given that I can’t expect my first plugin to give me any return on investment, and ‘the previous license agreement was deceptively written, so I never actually could’ is neither here nor there.

I feel like all the work I did so far was for nothing - a couple of years of my free time: it’s a sophisticated instrument, I bit off more than I could really chew, and I’ve gotten so far that I’m mostly implementing the UI and debugging at this point - I don’t really know what to do next.

1 Like

We will be introducing a new Starter tier:

Is your feedback still applicable to the Starter tier?

Is the EULA in the juce8 branch up-to-date? Can we use it to understand the currently intended terms?

2 Likes

Hi, what is the deadline for juce 7 licenses?

1 Like

No. We’re still back and forth with lawyers right now. We’ll post again on the forum when there is some confirmed changes.

It will be at least 30 days from the time we announce our revised EULA.

Thanks all for your feedback and patience. Despite it now appearing quiet on here, work on this continues internally as we make amendments following all the feedback we have received.

15 Likes

This thread has gotten so long that it has lost most of its usefulness. Please see information about a new version of the EULA here: