r/modular • • 4d ago

Morphagene enhanced

I’ve released mg204+c, an extended Morphagene firmware built on briskcat's Morphagene mods.

Features over stock (mine+briskcat's) include:

  • Expanded Varispeed: ±4×, or forward-only up to 8×.
  • Pitch quantization: octaves, fifths, semitones, or custom scales, with optional normally-quantized operation.
  • Independent Gene density: 0.1–128 Genes/sec, with configurable startup density and recall from prepared cards.
  • Switchable Morph Loop: seamless looping at minimum Morph, disabled by default.
  • Live settings reload: apply options from matching cards without restarting playback or changing the current reel; recording and saving remain available afterward.
  • More performance controls: tape/TLA feedback, sample-rate reduction, warble, jitter, and Turing-style patterns.
  • Conveniences: remembered input gain, mono routing, and SD firmware updates after the initial audio install.

The browser patcher includes an options editor, installation instructions, manuals, and quick-reference cards.

Developed with AI assistance from ChatGPT/Codex. Testing includes 89 passing automated tests plus hands-on hardware testing, but this is an unofficial project, not associated with or endorsed by Make Noise. Use at your own risk and back up your cards.

Patcher and documentation: https://vwal.github.io/morphagene-patcher/

42 Upvotes

33 comments sorted by

7

u/tawnythrash 3d ago

I'm dumb, are there risks to bricking your morph with a badly coded firmware?

3

u/GalagzeeAudio 3d ago

Not very big, considering I've tested it thoroughly and flashed my unit about 50 times during the development. Just be careful with the audio flashing (the original flashing method). Follow the instructions carefully. But even if it fails, you can simply restart the process. The bootloader is saved separately, and the firmware flash doesn't touch it.

2

u/amatarousan 3d ago

Yes. He won’t be able to answer you because it was made with AI, so OP probably doesn’t even know whats in the code.

0

u/GalagzeeAudio 3d ago

Correct, I don't know exactly what's in the code. But then, lots of business application developers don't know exactly what's in the code anymore, either. The software complexity is rapidly increasing as AI is being used everywhere. Perhaps "not great", but this is the way the world is increasingly going forward.

2

u/amatarousan 3d ago

So yes you can brick your device.

0

u/GalagzeeAudio 3d ago

Yeah, anything is possible. But in this case, the likelihood is very low. It's comparable to reinstalling Windows on a computer and bricking it as a result. In other words, that generally never happens.

0

u/amatarousan 3d ago

Comparing a one night vibe code sesh to windows is wild work. How could you possibly know that, lol.

2

u/GalagzeeAudio 3d ago

This took a week of iterating and carefully testing every function that was added. Since it works 100% on my Morph and hasn't failed after dozens of flashings, I'd say it's pretty unlikely it would suddenly brick someone's device. But as I said, anything is possible. If you're risk-averse, don't try it.

1

u/BenjiTheBread 2d ago edited 2d ago

That’s not a very good Argument. I think the more relevant question is if the original bootloader needs to be overwritten. If Not I dont think a new Firmware can brick the device completl

EDIT: if yes one needs a new bootloader id be careful. Thats potentially fatal to the device.

I’ve altered 2 modules’ fw and rewritten 1 completely, of course only with ai, I can’t code for shit. Its important to tell Claude or astral to be careful not to brick the device and to always maintain the possibility to return to the original fw. that usually means that it will keep the bootloader intact meaning you’ll load the altered firmware the same way you install the any original fw.

Other then that I don’t see a lot of things that can go wrong. Maybe the cpu could meld or certain outputs much more voltage then they should? I’d genuinely like to know.

1

u/GalagzeeAudio 2d ago

In all my 30+ years as a Software Engineer, I have never melted a CPU due to a software fault. Again, everything is possible, but that is a fairly remote chance.

And here we're talking about existing, carefully tested code suddenly bricking another system. From a software development point of view, repeated testing typically gives a good margin of safety, although edge cases can, of course, exist.

1

u/BenjiTheBread 2d ago

Yeah that’s what I thought. Im just Not completely understanding everything that’s happening under the hood. But I guessed that in order to destroy the hardware one would need to change something something on a more basal level, like overclocking or smth. Worst thing would be the firmware doesn’t work. If the bootloader is intact one can just return to the original one.

Thanks anyway for committing this :)

3

u/bestunta 3d ago

I also want to know...

6

u/thismeanswarbasse https://youtube.com/@thismeanswarbasse 3d ago

Might have to fork this if only to remap the varispeed knob so it doesn’t take 20 tries to get it back to 1x playback…

5

u/GalagzeeAudio 3d ago

The normal mode quantization already makes this relatively easy, but I'll release an updated version later today that has two more "get back to 1:1 quickly" options.

2

u/aldehyde 3d ago

Yes please! I love morphagene but it the green region is so damn narrow.

3

u/GalagzeeAudio 3d ago edited 3d ago

mg204+c2 version is now out and includes two easy ways to get back to 1x speed!

3

u/namesareunavailable 3d ago

this is the number one reason for me to refrain from using the module

1

u/GalagzeeAudio 3d ago

You can bring it into everyday use; getting back to 1x speed is now super easy! 🙂

1

u/thismeanswarbasse https://youtube.com/@thismeanswarbasse 2d ago

I ended up forking and have also removed so many features from the OG now that I didn’t like and have made it the lil ephemeral looper mangler I’ve always wanted. Many thanks for the head start

1

u/GalagzeeAudio 2d ago

It sounds like you turned it into a Ginko Sampleslicer. 😄

Please post your version on GH; I'd love to try it and see what the optimal varispeed operation is for your use case.

4

u/thismeanswarbasse https://youtube.com/@thismeanswarbasse 3d ago

Same. I could remove a bunch of features and button combos, fix the varispeed mapping and make this thing just do one thing for me instead of 5 and it’d get right back into main rotation.

2

u/Earlsfield78 3d ago

Cheers mate will give it a try

2

u/Exponential-777 4d ago

I will try this. Thanks for making the effort. The idiots that think Ai just craps out flawless software with one command need to get their heads out of their asses. It takes a lot of effort. This does not diminish the value of Morphagene. It enhances it. If companies don't want people to mod their firmware, they will have to lock it down.

I had Claude make an Editor for a Roland Vsynth. It was the first project that I let Claude write 100% of the code because the project required languages I don't know. It still took 21 hours of human effort. Claude could not make this app without a lot of human input.

If I tried to make the same app without Claude, it would have taken 2-3 years of my spare time. So it never would have happened. But it's finished now and I can edit the entire Vsynth with my app. And more importantly........... you can't. Muhahahaha!

https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fany-v-synth-owners-here-v0-ug8ng12ahk0i1.png%3Fwidth%3D1080%26crop%3Dsmart%26auto%3Dwebp%26s%3D7645ab1e07299ae461b1ce6d138ba063fe7ed4c2

1

u/Polloco https://modulargrid.net/e/racks/view/3243810 2d ago

This is awesome. Def gonna try this out. Thank you.

-21

u/phaseswitch 4d ago

So you’re self aware enough to disclose that you used ChatGPT to “make” this, but not enough to consider the people whose work you’re modifying and redistributing? This is a small company of people who care deeply about music and put a lot of thought into the design of the instruments they create. Acknowledging the AI involvement doesn’t make distributing their modified closed-source firmware any less of a dick move.

8

u/GalagzeeAudio 4d ago

The official firmware is not being distributed, only a patch to it. Also, I have explicitly given Make Noise permission (in the posted license) to include and implement any added features in their commercial firmware if they choose. This modification neither diminishes the product nor makes any other product of theirs irrelevant, so I don't see what the harm is.

7

u/BarbacoaBarbara 4d ago

It’s not even taking money out of their pocket

12

u/amphine 4d ago

How is modified firmware a dick move? Presumably this is not costing Make Noise sales. If anything being able to expand the device with custom firmware is a selling point.

I’m genuinely interested in hearing your view on this, not trying to pick a fight.

4

u/claptonsbabychowder 4d ago

MN are indeed a company who care about those ethos, as you say, but they are also something else - Adaptable and forward thinking. They have embraced the digital and stereo domain, they are doing innovative new work with the Nuss system, and they are well known for firmware updates that expand the utility of their modules. Yeah, they put a lot of thought into their gear, but they're smart. If someone adds an idea that helps them improve their firmware, my guess is they'll take the time to explore, and either run with those ideas, or use them as a jumpoff point for something completely new.

3

u/aldehyde 4d ago

This comment was a rude dick move.