CC-BY-NC-SA: OK. In my understanding, the ZynthianOS licensed under GPL-3 independently from the commercial kit being sold, is a non-commercial undertake.
All correct. My question is, is there any desire for Zynthian to be subsumed into a commercial product? For example, say someone made a Zyn-like box but with Hammond drawbars and sold it for profit with Zynthian pre-loaded, they’d have to delete any NC samplesets. (Note that Zynthian’s GPL license allows such a product, as long as they provide the software and any changes they make publicly availble, IIUC.)
Personally, I like the idea, and so I’d rather avoid having any NC samples included. I think they’d be better off as “secondary,” loadable by the user but not included by default.
So, I’m curious what the Z community thinks about this.
I’d say that is a problem they would need to solve.
I have also a license question: what about libraries hosted on Pianobook with their permissive EULA, but containing a license file stating they are cc-by?
IMHO, we should honor the most restrictive license found at a given site.
In any case, I think we should always credit sources wherever possible regardless of license, and that’s all that CC BY requires.
IMHO, we should have an “About” screen somewhere (probably from Admin → System) that lists all attributions. I’d be surprised if we don’t have some software attributions we need to show but don’t.
I did some further additions here. There is more to Versilians VCSO and VCSL as well as from Karoryfer alone that can serve us very much and all being in CC-0.
Generally yes. But this case I find very interesting, because Pianobook is a site which encourages people to share sample libraries made at home freely, and then there are people who do this and even upload their license agreements, but the EULA of Pianobook says the libraries may not be redistributed, which is somehow contradictory.
I think either they expect samplists not to upload permissive license or their EULA is unsuitable distributing samples in a more prohibitive way the creator intended (and stated)
Where can I find in zynthian repos where we build the soundfonts/sfz files? I’d really like to get started on hunting down the existing samplesets to check licenses etc., but I just can’t find where we pull it all together.
BTW I noticed that the Stereo Rhodes is Jeff Glatz’s rework of my jRhodes3c. (Although he mentions Alexander Holm as a source too, at Loading... but I suspect that was a mistake.) Not that it matters.
I’d like to work on the sampleset reorg, but I just can’t seem to find the repo where they’re all copied to /zynthian/zynthian-data. Any clues would be greatly appreciated.
What you ask for doesn’t exist currently. It must be created from scratch. As i’ve already explained, the current soundfont collection has been collected and maintained “by hand”.
Improving this situation is one of the goals of recent discussion about reorganizing soundfont collection.
Please, avoid splitting more threads for the same topic. I will “join” this to the existing ones.
I think I tried to answer the question to my best knowledge before:
The location you’re searching for is yet to be created. The location @cfausto suggests would be the natural location where it might be located in the future.
We need to get some questions solved together now about how we want to continue with this. I must confess that my motivation suffered a bit recently about us not advancing in answering some design questions in the first place. My very personal attempt was obviously to create some very zynthian suitable patches, and others opted more towards assembling a set of upstream pulled “pure original” soundfonts.
Meanwhile I did create some unified patches from some VSCO/VCSL patches. I think we at least need to find answers to where to create the library and how to submit to it.
I don’t know how it’s done, but I assume the image is build on @jofemodo’s local machine. So having it on a publically available repository can be seen as the goal of the undertake above.
So, we need to get forward, and still there are several design choices so solve.
P.S.: Also take a look at the other answer to the same question: