You are misunderstanding the situation. When the copyright holder says you “have my permission to share manuals freely”, they are giving the permission to redistribute the material. Not transferring their copyright to someone else. Chill 
I am sure, too, that VCV would not like their board to be used for things that are technically illegal. It is absolutely 100% certain such a thing hasn’t happened here.
Anyway: wishing again all the best, and hopefully the Madness Suite can stay in the library, it’s cool.
Oh, I’m plenty chill. It’s just that I think the copyright law from Chapter 2 - Circular 92 | U.S. Copyright Office is probably accurate.
I’m not misunderstanding the situation. Magus had as copyright, by default. Even if they don’t want it, they have it. They are allowed to transfer it, which they seem to want to do. Which according to the law must by done a certain way, as I indicated above. And via email seems to not satisfy the law.
I’m certainly not planning to try to “get anyone in trouble”. Just pointing out what the law actually is.
I fully understand if you don’t want to use google to find out what the law actually is. As I freely admit - it’s clear no one is intending to do something bad. It’s fine.
You are just talking about a different thing, that’s all. Thank you for the info, and no thank you for the “I fully understand if you don’t want to use google to find out what the law actually is. As I freely admit - it’s clear no one is intending to do something bad. It’s fine” passive aggressive stuff 
Hey @ryanpage1989 - would you considering making these modules open source? Then VCV can take them over and port them to ARM?
VCV had never done this before, and they would at least need explicit permission to do this, as taking over abandoned open source plugins would otherwise violate their own written guidelines, which is here.
(Please think of analogous situations / precedents on these and other such forums, when transferring something like synth patches, images and so on - and also if there was some situation like, “oh, does someone still have those patches I made back then? Hey, feel free to attach those here”, and so forth. The way authorship and default copyrights work indeed grant copyright, by default, to any such creative output. The way situations like this are handled 1) do not transfer the author’s copyright, implicitly or explicitly and 2) can be demonstrated in numerous such precedents in which actually enforcing a signed permission in writing would be out of place. Conversely, if you can quote one actual precedent of an interaction like this where a signed permission in writing was required, and lack thereof was seriously and in good faith considered a bad thing ;), and there are court documents of this, please link such a precedent. Otherwise, this is just some weird forum power play.)
1 Like
sorry, I may indeed be incorrect on copyright law here. I was really trying to point out that it’s really unlikely that VCV would ever host other ppls manuals. Definitely not trying to “pull a power play” here. making everyone dislike me (more) would be an odd way to try to get power, I think 
1 Like
Hah okay, no hard feelings. Really
1 Like
Isn’t this happening with Frequency Domain? Not VCV specifically, but someone from the community could pick it up if it’s open source.
I don’t know the details of what’s going on with Frequency Domain, although I had heard they were coming back to the library.
Another thing I don’t know for a fact, just assuming, is that a module has never been adopted by someone else and put back in the library, other than the single case I do know about - @robert.kock quite generously adopted my Squinky Labs modules.
That assumption may be completely incorrect - there may be other cases of modules being adopted. For all I know VCV themselves may have adopted modules.
Unfortunately, I can’t make that call. I did the design of the modules, came up with the basic concepts, created manuals, decided on functionality, set ranges of values to use, basically the aesthetic and sound design stuff that didn’t involve DSP code. The code is David’s and it’s really his choice whether or not he wants to make it open source, some of these designs were adapted from things he’s been working on for over a decade and I just don’t know if that’s the path he wants to take with it.
As much as I would love for more people to have access to our stuff (and to have these maintained so that I could continue to use them), I have to respect the decisions of the people I worked with, especially when they’re close personal friends. Anything I did I am happy to have distributed freely. As I mentioned I didn’t copyright the manuals (you can check there is no copyright included in the documents). I also had some demo patches I’m going to try and find to post.
3 Likes
Nope, Eric has opensourced it and submitted it to VCV, so should be available in the library as arm64 compatible soon. I built it from source on my M1, works like a charm.
4 Likes
Noticed something weird with Shoggoth: upon being triggered, the rise portion of the slope starts abruptly:
This doesn’t happen in cycle mode. Please, can someone verify this? I’m on Windows 11. Thanks!
Damn official vendor site seems dead. https://magusinstrumentalis.com/ (But tnx for headup, seems interesting stuff)
Hello, any news on this?
Frequency Domain has been in the library for a while with arm-64 support
Ok I didn’t see it. I’ve been wondering what would happen with Ars Memorium. I bought it and it was a central module for many patches. I can’t use it anymore and was wondering if there was some options.
Sorry what mean ? I bought recently it too, and it still opens\works ok now. As i see it’s just not available for purchase anymore, but this is should be usable anyway ? Or you can’t download it ?
1 Like