If I buy a song on Bandcamp, can I then use that song in my audio streaming website project accessible by the public? I want to replicate this site here (note I am not a non-profit like freeCodeCamp): https://coderadio.freecodecamp.org/ I'd like to repurpose it to feature a different genre of music. To accomplish this, I must build a new playlist. Since my site will be accessible to the public, I'd like to use songs that will not violate copyright. From my basic understanding, Bandcamp music is DRM-free when purchased. I'm vaguely familiar with what DRM is, but unsure if that qualifies me to use the purchased songs in my new project or not. https://get.bandcamp.help/hc/en-us/articles/360013673153-Are-Bandcamp-s-download-formats-DRM-free- https://bandcamp.com/#discover If Bandcamp is a no-go, are there alternative music platforms that you could recommend?
DRM-free is not license free. DRM is just an attempt to enforce copyright licenses via software. DRM will theoretically prevent you from playing the music unless you have a license that allows you to play it. The lack of DRM it doesn't mean you can do whatever you want with the recording. It just means that any violation of copyright rules will have to be settled using the legal system. If the copyright holder finds you offering their music for replay without a license to do so, they can take you to court to make you stop. Bandcamp and other distributors have negotiated a contract with the musical artists and other copyright holders to offer their music for replay on their site. If you want to legally offer music to which you don't hold the copyright for replay on your site, you too will have to negotiate a license with the copyright holders.
As far as I can tell, whenever GitHub redistributes code, it adheres to all of the requirements of the GPL/BSD etc. For example, it never gives away code without including the license text, and it doesn't claim to add unpermitted restrictions to the code. The section you're concerned about is this: That means you're giving us the right to do things like reproduce your content (so we can do things like copy it to our database and make backups); display it (so we can do things like show it to you and other users); modify it (so our server can do things like parse it into a search index); distribute it (so we can do things like share it with other users); and perform it (in case your content is something like music or video). That section isn't worded very precisely, but I understand this to mean they want to reproduce your content in full, not just the code without the license text attached. They want to display your content in full, as you provided it. They want to modify it internally (i.e. they are not redistributing this modified form) in order to allow searching. To the extent that they display code-snippets as search results, that is likely defensible as fair use (search engines are frequently cited as examples of successful fair use defenses). GitHub appears to be acting consistently with the GPL when it reproduces, displays, modifies, and distributes code that you upload. If I'm correct about these facts then nothing that GitHub does with the code goes beyond what the many contributors to a GPL project have explicitly permitted, or what is otherwise permitted by fair use law. If you had some code with a more restrictive license, you might not be able to simultaneously comply with that restrictive license and GitHub's License Grant. Consider the scenario where you have some code that is licensed exclusively to you, and you are not given permission to reproduce or distribute it. In that scenario, the code's license prevents you from agreeing to GitHub's request for a license grant.
Yes Playing recorded music in public is unlawful without permission (licence) from the copyright holder. Many jurisdictions allow automatic licensing by signing up with and paying for it through the authorised music organisation.
Using it without permission is copyright infringement and illegal. Legally, you can try offering money to the company for the copyright or for a suitable license. For example offer them $1000 for a copy of the code licensed under the GPL license. If they accept, you are fine.
Any adapted work derived from a work used under a CC-BY-SA licnese must be distributed, if at all, under a compatible license. The question is whether a large work incorporating a much smaller work is said to be "based on" that work. The CC-BY-SA 4.0 legal text does not use "include" or "incorporate" or any similar term to define an adapted work, instead it says: Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. If including a single work makes your book Adapted Materiel, than you must either release the book under the same license, or else not rely on the CC license. I am not at all sure if such use would make the book Adapted Materiel. If the content could be quoted (perhaps only in part) based on fair use or fair dealing or a similar theory, you would not be relaying on the license. But whether such use is legitimate is always a very fact-bound question, which will depend on various specific facts. See Is this copyright infringement? Is it fair use? What if I don&#39;t make any money off it? for a summary of US fair use principles. If the materiel you want to use would not qualify under fair use (or whatever similar principle applies in your jurisdiction), and the book would be considered Adapted Material, then you would have to omit it or put the book under the CC license. I see in The CC case law page the statement that: The atlas was a compilation not a derivative work, so did not need to be licensed under the SA term, Which might apply to your book. If it does, you would not need to place the book under a CC license. Update: On reading CC's detailed wiki page on Drauglis v. Kappa Map Group, LLC I find the statement that Use of a whole work is suggestive of a "compilation" rather than a derivative work subject to the ND/SA terms. attributed to the US District court (DC district) that decided this case in 2014. If that decision were followed, it would seem that the book would not be considered a derivative work and while proper attribution must be provided, and the applicable license must be indicated, the book itself need not be released under CC-BY-SA.
It is not "perfectly legal" to transcribe music for personal use. It is pretty likely that you can get away with it. The first thing to understand is that the act of transcribing is the creation of a derivative work (see the definitions part of Title 17). The core protection is section 106, which states that the owner of copyright has the exclusive right to prepare derivative works based upon the copyrighted work. So it is not permitted to prepare derivative works, e.g. transcriptions, without permission from the copyright owner. There is a big however: section 107 provides a possible loophole, "fair use". If you were to be sued for violation of copyright in making an unauthorized derivative work, your attorney might well advise you to set forth a fair use defense. This question and answer summarizes the basics of the fair use defense. Probably the most important factor would be the 4th factor, the effect on market -- in the circumstance that you describe, the effect is likely to be low. If you do this as a paid service for others and not just for personal amusement, then a fair use defense becomes a stretch.
What are exactly the legal consequences of "All rights reserved"? Almost none. You have to explicitly grant copyright rights. You don't even need the Copyright notice for them to apply. My "almost" is because the notice makes it harder for somebody to argue "they didn't realize". Do I still need an additional SW License Agreement or is the Copyright notice above + a Disclaimer of liability sufficient? If this is free software (I know you said it isn't), do yourself (and everyone else) a favour by picking a license you like. Preferably either GPL or MIT (depending on your taste). There are far too many free licenses already. Please don't add another. (It also makes it much easier for any user of your software: "Oh yeah, GPL v2. We understand that. We can use it." as opposed to "What are the implications of using this one??" As this is not free software, I think you need a paid-for lawyer (who understands IPR in your juridiction.) Edit: In principle, I believe you don't need anything. The code is copyright, so the customer can't do anything with it (without explicit permissions that you haven't granted). However if the customer doesn't realize that or thinks you won't mind, you then have to go to court to enforce your rights (and probably end up with a disgruntled customer). A short, clear, license will make it clear to the customer what they are allowed to do, and save all that aggravation.
I know that some of this may be covered by either the Creative Commons license or the OGL it was published under, but it's not clear to me how far those freedoms extend. It was all published as materials under copyright to the original authors, TSR, WotC, &amp;c. and if things had been left like that hszmv's answer would've been completely correct: stay vague and allow users to enter those names and descriptions, talk to WotC's lawyers and sales department about license fees, or just keep it to yourself and your friends. You're right, though: WotC went whole-hog, dumped their partial OGL idea, and relicensed some things as Creative Commons. There are different Creative Commons licenses, though, some restricting commercial use that would still keep your app to yourself and friends without a specific licensing agreement. Go find out exactly what WotC put under CC. If it's only the Player's Handbook, then you can only use names and descriptions that are from the Player's Handbook and you're still facing a cease-&amp;-desist if you start adding in Monster Manual info.If it's everything, it's everything they have but still won't include any older modules that they don't have the right to change the copyright status of. It'll still be under copyright, usually until 70 years after the death of the original creator. For Gary Gygax, that'll be 2078. Expect that length to extend during your lifetime though. US copyright usually extends every time Mickey &amp; friends come close to entering the public domain. [Edit: The comments below suggest it might only have been the Systems Reference Document (I assume for 5e). It's 403 pages of not nothing but it's not much given the universe we're talking about. The spell and monster lists are generic. Bigby is nowhere to be found and the only mention of a beholder is a reminder not to use the name beholder without their written approval.] Go find out exactly which CC WotC used. The article above says &quot;all use&quot; but you need to find out the exact number of the Creative Commons license for each thing you're using and make sure all of your uses fall within its terms. Some are basically free use but still insist you mention the copyright holder prominently or in every use. Go ahead and do that if you have to. [Edit: The comments below say it is probably CC 4.0. The SRD download page says you can use CC 4.0 or their own OGL. In both cases, yes, you must acknowledge WotC by name in a way prominent enough to satisfy the license you choose.] And of course, Don't trust legal advice from internet randos or ChatGPT. If this is a serious thing you're going to be spending a good chunk of your life working on or expect to make significant money from, go talk to an actual lawyer. Bonus points for one specialized in IP with a knowledge of roleplaying and the way it's been (partially) opening up lately.If you start off just by talking to WotC's lawyers, just do that somewhere where you get their explanations and permissions in writing. Then keep that somewhere safe in electronic and hard copy. Then still take that with you when you go talk to your own lawyer.