Page MenuHomeSolus

helm open source synthesizer
Open, NormalPublic

Description

helm is an open source synthesizer available as standalone , vst and lv2 available for all platforms ( linux, windows, macos)
helm home page
is it very easy to use and fun, the gui is very nice, easiest to use than zynaddsubfx for a beginner like me
you can download it as a debian package helm download deb

or with git
helm git

i tried to compile it for solus but got an error : make[1]: * [Makefile:430: build/intermediate/Release/border_bounds_constrainer_b5a34af8.o] Error 1,make: * [Makefile:85: vst] Error 2
thank you

Related Objects

pizux created this task.May 8 2018, 2:57 PM
pizux updated the task description. (Show Details)
pizux added a comment.May 13 2018, 7:27 PM

binary debian package works very well

Need to look into this deeper. JUCE sub-license is weird about redistribution if I remember right.

DataDrake triaged this task as Needs More Info priority.Jul 21 2018, 12:22 AM
DataDrake closed this task as Wontfix.Aug 31 2018, 5:34 PM

Let it be known that anything requiring JUCE is off-limits. It's license and EULA are unenforceable by us and frankly, make me uncomfortable from a legal standpoint. Therefore, this is ineligible for inclusion.

mtytel reopened this task as Open.Jan 13 2019, 10:41 PM
mtytel added a subscriber: mtytel.

Hey @DataDrake
I'm the developer of Helm. Hopefully I can clear up some of the JUCE worries.

JUCE has dual license setup where you can either use JUCE under the GPLv3 *or* if you're making a proprietary app you can pay for an exception and follow their proprietary license and EULA.
This is strangely hidden if you go through their main site (I think so they can boost sales), but you can find the info in the file headers and in their source code.

Here's a header from one of the files (look for the 'Or section):

/*
==============================================================================

 This file is part of the JUCE library.
 Copyright (c) 2017 - ROLI Ltd.

 JUCE is an open source library subject to commercial or open-source
 licensing.

 By using JUCE, you agree to the terms of both the JUCE 5 End-User License
 Agreement and JUCE 5 Privacy Policy (both updated and effective as of the
 27th April 2017).

 End User License Agreement: www.juce.com/juce-5-licence
 Privacy Policy: www.juce.com/juce-5-privacy-policy

 Or: You may also use this code under the terms of the GPL v3 (see
 www.gnu.org/licenses).

 JUCE IS PROVIDED "AS IS" WITHOUT ANY WARRANTY, AND ALL WARRANTIES, WHETHER
 EXPRESSED OR IMPLIED, INCLUDING MERCHANTABILITY AND FITNESS FOR PURPOSE, ARE
 DISCLAIMED.

==============================================================================
*/

I'm obviously choosing to license JUCE under the GPLv3 (which doesn't require following the EULA) so that should make Helm eligible.
Let me know if you have any questions. There has been some push on the JUCE forums to make the dual licensing language more clear but I guess they haven't followed through with anything.

DataDrake raised the priority of this task from Needs More Info to Normal.Jan 13 2019, 11:58 PM
DataDrake moved this task from Backlog to Accepted For Inclusion on the Package Requests board.

Thank you for taking the time to reach out and clarify. Any time I tried to find this license I would get thrown into the EULA, which is annoyingly vague and in no way points out this exemption. I will take this under advisement.

css459 added a subscriber: css459.Jan 14 2019, 4:29 AM
This comment was removed by eeshugerman.
css459 added a comment.EditedJan 14 2019, 7:58 AM

I have a working package.yml (with pspec_x86_64.xml) that creates an eopkg successfully. How exactly would I submit this with arc since the following link looks like it walks through modifying an existing package? I might be misunderstanding, however.

https://getsol.us/articles/packaging/submitting-a-package/en/

Of course, if the original creator prefers to be the package maintainer for this program, I'll gladly turn the files over.

Jacalz added a subscriber: Jacalz.Jan 14 2019, 9:20 AM
Skyeun added a subscriber: Skyeun.Jan 14 2019, 9:41 AM

I have a working package.yml (with pspec_x86_64.xml) that creates an eopkg successfully. How exactly would I submit this with arc since the following link looks like it walks through modifying an existing package? I might be misunderstanding, however.

https://getsol.us/articles/packaging/submitting-a-package/en/

Of course, if the original creator prefers to be the package maintainer for this program, I'll gladly turn the files over.

You have to init a git repo with git init in the folder where your package.yml is located. Then git add . to add your files (make sure to run make clean before in order to only have the necessary files). After that you have to tell what you have done with git commit -m "What you have done". The final step is to follow the part Submitting to review. Make sure to fill a proper test plan.