-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQ] Add a (GH-compliant) license file #2
Comments
Bump (request updated). |
Bump. Happy new year, any news ? |
MIT License has been added to the repository to ensure clear usage and distribution terms for all contributors and users. You can now find the LICENSE file in the root directory. |
Happy New Year again, it works now thanks ! Hope you'll enjoy this interesting discussion I've opened @ OpenVINO™ AI Plugins for Audacity repo about audio recovering/enhancing: there are of course many different approaches but, as I explained in this issue at Audio Delossifier repo... FORART's - a nonprofit organization I'm member of - goal is to "enhance" (read: remaster) many old cameras' audio streams through a (specifically trained - we do have many recent live music multicam shootings and multitrack+mixed or stereo audio recordings from main mixer too) neural network. Thanks in advance for any knowledge/idea/code/etc. you'll contribute with. |
Hi there, 1st of all thanks for this awesome work !
Since we've 'doxed' it in our HyMPS project (under AUDIO section \ AI-based category \ Enhancers page \ Aligners), can you please add a GH-compliant license file for it ?
As you know, expliciting licensing terms is extremely important to let anyone better/faster understand how to reuse/adapt/modify sources (and not only) in other open projects and vice-versa.
Although it may sounds like a minor aspect, license file omission obviously causes an inconsistent generation of the relative badge too:
(badge-generator URL: https://badgen.net/github/license/yoongi43/music_audio_enhancement_conformer)
You can easily set a standardized one through the GH's license wizard tool.
Last but not least, let us know how we could improve - in your opinion - our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
Hope that helps/inspires !
The text was updated successfully, but these errors were encountered: