2 Likes
Post from henner, Nov 7
“Context is experimenting with compiling Befaco Oneiroi which will have to remain closed source, and which I’ll have to distribute as a .mmplugin eventually, so it gets a bit awkward debugging as built-in, copying out, building in SDK etc.”
3 Likes
Woow, let’s hope this one will come to the MM….
1 Like
(still loads to debug, optimise, fix etc but it’s making the right kind of noises, so hopefully on the right track. It’s been a busy 2024 and I need a wee break though so definitely nothing released until the new year)
10 Likes
You rule, @hemmer.
Just curious: Will the Meta Module version be paid (as the VCV version is)? I think it might be good for the Meta ecosystem for there to be a high-profile paid module.
1 Like
This is cool! I had one on pre-order but after hearing all the issues people had with the first batches I pulled my order and got something else instead.
Mm good question - I’m honestly not sure, will discuss with others involved and get back.
1 Like
This is so nice 
woow.
Good work man!
Looking forwards to seeing this one.
Hi Hemmer nice site and projects you are doing,
do you know if the Bastl Pizza is coming to the Meta module?
2 Likes
I asked and it’s not a short term priority for them I think but let’s see. (It’s a bit of a trade off, do we spend time releasing new modules for VCV which benefits a larger group or existing modules for MM, which undeniably benefits a much smaller group. Hopefully both in the end, and MM porting process is getting easier!)
1 Like
Probably not technically feasible, but it would be great if a mechanism could be implemented that would pass a token from VCV to the MM via the .yml file (or some other mechanism) that would verify the purchase and ownership of premium plug-ins. I realize that such an approach would not be satisfactory for those who build their patches exclusively on the MM, but you can’t accommodate everyone’s workflows. I’d gladly pay the $35 asking price for the Oneiroi plug-in to use it in my MM.
DannGreen’s a super smart guy. I’m fully confident he can code some kind of cryptographic unique identifier for our Meta’s. Maybe even before breakfast.
1 Like
hard to have a ‘protection system’ in place as the firmware for MM is open source (and so is the hub) , and so public. meaning someone could easily ‘circumvent’ the system.
note: the project being open source was an important part of my purchasing decision, so any move away from that, Id be pretty unhappy about. (not that I think 4ms would do this)
given this ‘undeniably benefits a much smaller group’, I think the route chosen by Sapphire is a good one to follow.
the module is premium on desktop, and so you get a benefit to purchasing that even if you use on the MM (and many of us create patches on vcv, so would want this)
but the few that just use on the MM , get it for free.
thats the simple way…and frankly, probably not going to loose much revenue for Befaco.
(personally, id buy in vcv just to support the project… as I think would others)
other than that, sell the mmplugin via your own shop… doesn’t really need protection.
Im sure the vast majority of MM owners are trustworthy, and want to support developers.
2 Likes
Sadly the MM port needs to remain closed source (VCV premium terms). But we don’t want to double charge and a closed source but free as in cost MM plugin is the most probable model at this point, as you describe.
3 Likes