I thought this post from MrFang in the Mod Wiggler thread was interesting:
“Regarding Synthesis Technology, Paul said no to MM versions due to the exclusive nature of his agreement with VCV.”
I wonder if there are any other developers that have similar arrangements with VCV that would block their modules from being published for use on the MM?
Seems counter productive to make a restrictive clause that would otherwise drive more custom to both parties. If the quote is correct the actual reasoning may be something other than the stated agreement, and this quote may just serve to forstall any need to elaborate on that decision.
it could be to do with use of (certain) vcv code.
in some situations, using this (vcv) code means you can either: ( * )
(this is a simplification, there some topics somewhere on vcv forum about this for details)
but in terms of the OP, yes, there are situations where a developer might not be able to ‘just’ port the code to MM and release. at least without explicit (commercial) agreement from vcv.
ofc, the above statement is (very) vague so, in this specific case, there could be many other reasons that we are not aware of.
at the end of the day its up to individual developers to decide if they can/will port.
( * ) completely fair, if you are using vcv code in your module, then vcv get to choose how to license the derivative product.
anyway, its a bit more complicated that this, including exceptions… but thats the gist of it.
ofc, the dev can ‘get around’ this by rewriting thier code to not use vcv code that is under this agreement.
My quote above is based on a brief in-person conversation I had with Paul at KnobCon in September, but I don’t remember his exact wording and I don’t want to misrepresent his position. Anyone is welcome to contact Paul directly for further clarification.