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.
The license file omission causes an inconsistent generation of the relative badge too:
You can easily set one using the GH's license wizard tool.
We also suggest you to keep in consideration to establish some kind of collaboration both with Python Audio Restoration Suite by @HENDRIX-ZT2 and DEVINYL by @matiaszanolli, that are the most interesting projects on the scene.
Last but not least, let us know how - in your opinion - we could improve our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
Hi there, thanks again for this cool work !
Since we've "doxed" it in our HyMPS project (under the AUDIO category \ Tools section \ Restoring subsection), can you please specify the license 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.
The license file omission causes an inconsistent generation of the relative badge too:
You can easily set one using the GH's license wizard tool.
We also suggest you to keep in consideration to establish some kind of collaboration both with Python Audio Restoration Suite by @HENDRIX-ZT2 and DEVINYL by @matiaszanolli, that are the most interesting projects on the scene.
Last but not least, let us know how - in your opinion - we could improve our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
Thanks in advance.