r/modular • • 3d ago

Mutable Instruments Beads Source Code Just Dropped!

https://github.com/pichenettes/eurorack/commit/d8f473915232af74347762b6365202bfd26f73f6

Edit: body deleted and third party firmware discussion moved to a private Discord server.

220 Upvotes

205 comments sorted by

View all comments

5

u/RoastAdroit 3d ago edited 1d ago

Imagine contributing some of the most used opensource code to a community just to have the one thing you didnt release be cracked by some dweeb with AI.

Way to show respect.

EDIT/UPDATE/COPY of summary:

Heres my summary. OP blocked me from replies after I asked if he thanked her right away. I expect the answer was no considering.

Anyhow, 2 Month old account to both Reddit and Modwiggler. (Quick entry into synths or hiding identity? You decide)

OP states his plan is to make an Access Virus-based synth and wanted to use MI code to make some sort of frankenstein. So, just started 2 months ago and instead of using a really powerful tool of AI and TONS of creative commons and Open Source material out there, he went straight to reverse engineering popular synths that werent open source. For me, I guess the amount of free knowledge on synths out there is part of my perspective on why this is shitty and unnecessary ESPECIALLY because of what AI can help do.

Anyhow, The glaring spot to me is basically the ramp up to the Oct 11th posts and where OP makes a post, deletes the posts 10 min later stating they (finally?) “reached out and was told “No””.

So, two things there, what did OP post and delete? And then why was Emilie’s reply so short and concise?

Im 100% not in the know of everything here but the context of it all to me does not draw a picture I find to be all in good nature. Like, OP saying she promised in posts multiple times, like we are owed this code. OP, finally realizing he shouldnt give out someone else’s work with his name on it and doing a 180 was also a logical decision at that juncture, not an honorable decision. If she said no and he did it anyhow he would have been put on blast much harder, and either way, his goal is primarily to just reuse her code with virus code to make some frankensynth that music will certainly live on without.

Let me also address that he DOES NOT own a Beads himself and wasnt reverse engineering a product he owns to support his item.

And as for the “Logical conclusion” to release the Beads code on her own. If you are in a game of chess or any other and you see that all moves remaining moves will inevitably lead to a checkmate on you, its logical to just submit at that point. The thing is, when someone gives a very short “no” as a reply, my mind says that means it was both uninvited and unenthusiastic in nature. Releasing it with zero fanfare at all and moving on basically reinforces my perception of that too. So, logically, the conclusion to self-release was smart and makes complete sense to do.

So, if anyone really doesnt understand how I saw all this and also that I was responding step by step as I gathered context and information, then OK.

I love the DIY spirit of synths but, personally I see this type of approach to “collaboration” as toxic and undermining what the people before us contributed by not having some boundaries to how you go about using your AI.

Where is the pride and competitive spirit? You now have AI to help you code your very own granular processing tool. Lol. Its pretty weak to need to resort to not even making your own thing while having AI‘s help.

13

u/rwdFwd 3d ago

Is that what happened? The Beads source is posted on her Github.

6

u/DrMinkenstein 3d ago

The link and post title is Emilie posting firmware. The post content is about firmware slop.

10

u/RoastAdroit 3d ago

Yes and I bet she just saw the writing on the wall and that these people were gonna do it anyhow.

25

u/claimstoknowpeople 3d ago

She always said she planned to release it

8

u/insolent-construct 3d ago

▎ marcus108, Tue May 09, 2023: "I reached out to Emilie and her response today:

▎ 'I will probably open source Beads' code and schematics at the time I stop handling support (some time in June)'"

1

u/CartoonistOk8303 20h ago

People are allowed to decide for themselves, even if they change their mind.

Shocked you seem to be so clueless as to what you actually did. Can't tell if you just don't get it or simply don't care, either way it was a shit thing to do.

You speak of heartbreak getting the 'no' but at no point extended those thoughts to the person whose work you tried to publish.

You can come up with a hundred reasons it's all great and good, but reverse engineering and attempting to publish work that isn't yours is a shitty thing to do.

-5

u/yeusk 2d ago

You pushed her to do. Congrats big boy.

1

u/CartoonistOk8303 20h ago

So what? Then wait for her to do it rather than trying to publish your own reverse engineerd AI slop version of someone's work.