Not sure this is the right place for this question, but there doesn't seem to be a right place.
You have said that fxobjects.h and .cpp are freely usable.Â Many of the plugins are Copyright by Tritone which is clear.Â Some code is marked for academic use only which is also clear.Â Many other code files have no restrictions noted in them.Â Are these code files with no restrictions noted freely usable as well?
You can use all of the fxobjects stuff as you like - there are no restrictions. However, if you want to redistribute the C++ files, you need to keep the copyright intact. That's all. Most people have no reason to redistribute it but that is part of the ASPiK license as well (the fundamental restriction is that you can't re-package it as your "own" plugin framework).Â
W Pirkle said
...Most people have no reason to redistribute it but that is part of the ASPiK license as well (the fundamental restriction is that you can't re-package it as your "own" plugin framework).Â
WillÂ Â Â
Apologies for what might be a silly question. If we extend the framework to include support for some other platform (VCV rack or maybe a DAW's native format; Rack extensions or what have you) How do we distribute that? Are we allowed to put that up on github? I know (well, "think with confidence") the license says not to call it ASPiK, and not to call it "your own" framework -- that's clear. But surely we're supposed to mention what it's derived from, or that it's an extension to ASPiK. right?
Mostly a hypothetical. 🙂 I don't think I'd be able to extend it beyond adding a new template for the format I want to support: and that's easily distributed as an extension that doesn't modify the framework itself.
Well, the bottom line has to do with packaging it and selling or distributing it as a plugin framework. For open source, the idea is that if you want to extend it in a way that would modify the underlying code, you would do that and issue a pull request, then I'd merge that into a new version for all to have. If you are just extending it but not modifying the SDK files, then yes that would be easily distributed as an extension, with a link to the GitHub page.Â
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Moderators: W Pirkle: 689