OPEN-1 Promises To Be One Synth For Every Firmware

Portland electronic music producer Alexander Gaddis (RedtailWorks) shared these videos, documenting his concept designs for OPEN-1, an open, entry-level synthesizer that can run multiple firmware options.

Unlike the M-Vave FM-1, though, the OPEN-1 is designed intentionally to run multiple firmware options and would let you swap them on the fly.

In this concept video, the OPEN-1 runs a simulated HYP-1, in time with a real HYP-1 live take.

Open-1 Synthesizer Specs (preliminary):

480 MHz Cortex-M7 (STM32H750), open toolchain (the FM-1 runs at 240 MHz)
32 MB of working memory for long delays, loops and samples (the FM-1 has about 432 KB)
16 MB of firmware flash plus a microSD library: keep several firmwares installed, swap from the menu
24-bit stereo audio in AND out, so it can be an effects box too
MIDI in and out (3.5 mm TRS), USB-C device and USB-C host
37 RGB-lit silicone keys, 8 velocity pads, 8 endless encoders, a thumbstick and 2 spring levers
4″ 480×320 IPS screen, built-in speaker, headphone out, 3000 mAh battery
Wired only, no Bluetooth: lower latency, simpler to build
Target price: under $200

Open Synthesizer Design

The platform would include an open SDK and a browser emulator, so developers can build firmware before the hardware ships. Launch firmware would be ported from existing options for the FM-1 family: HYP-1, LOF-1, ECO-1 and GRAV-1.

Availability:

At this point, the OPEN-1 synthesizer is just a design concept. You can learn more about it at RedtailWorks’ Youtube page.

16 thoughts on “OPEN-1 Promises To Be One Synth For Every Firmware”

  1. This is a great idea. Even if it comes out at more than $200, I think it would be a good deal to have multiple OS that you can swap out at anytime. Is it asking too much for the ability to run 2 at the same time?

  2. I can see official FWs running for this thing, heck, even decompilations to build hybrid FWs so you can have say the elektron sequencer with Nord rom/bios and Arturia Freak engine all vibe coded into one firmware running on this thing. Very different from the Pi Synth project with all the overhead, just some FW running very close to metal.

    If anything an idea would be the ability to custom build your own synth as Ive sen you can already do somewhere, Put pads or keys, knobs or faders, all of them if you cant and build the thing in like quadrants. you pick SoC and screen size, touch or non touch for other uses like X/y fx… its gonna be a wild ride for the synth industry just like its happening in the video game industry.

  3. I am worried about the DAC specs as well as how good the analog part of the signal chain is, as well as the SNR (noise floor). And what about the amplifier?

    Lots of budget gear usually tend to have crappy sounding outs, making them a bad choice for pro users. No matter how good sounding the firmware and the different synth models could be, if the real signal coming out of the unit is bad, noisy or dull, …

  4. M-VAVE’s product line (with multiple different controller keyboards besdies the FM-1) already exists. They may not have expected the FM-1 to be embraced by the modding community, but they haven’t put any obstacles int eh way either and they’ve surely realized that versatility and hackability are turbocharging their sales. It’s very likely that htey’ll design their future gear the same way to keep satisfying the demand.

    I’m not sure what RedTailWorks is trying to achieve here, these are just slight panel variations on products that already exist and are already open to multiple different firmware configs. As for the internals (the STM32H750 etc), M5stack has a product like that in the pipeline, though I think it will be running an ESP32-P4 or similar.

    “Wired only, no Bluetooth: lower latency, simpler to build
    Target price: under $200”

    I don’t think RTW really understands the capabilities or economics of systems-on-a-chip these days. Bluetooth audio is showing up in synths not because the designers are salving over it but because there are so many bluetooth audio consumer products (speakers etc) that the cost of including is essentially $. The Bluetooth hardware is already built into the chip because it’s simpler to stamp out chips that have it than to reinvent the wheel by putting it on circuit boards.

    For context, the JieAi audio chip in the FM-1 and related product lines from M-VAVE is such a system-on-a-chip with BT built in. It was originally intended to go in things like portable speakers etc and the reason it has audio handling capabilities is so people could implement EQ, compression and loudness effects to make tiny portable speakers sound a bit heftier than the physical size of the speaker drivers would suggest. M-VAVE just decided to use it as a synth instead of as an effects/mastering unit. These JieAi chips cost about $1.50 each in bulk. Yes, one dollar and fifty cents.

  5. i’m not interested in little platforms. if someone comes out with a full size 5 octave box of knobs…. but just saying now, makes it seem so much more unlikely. oh well. i still have my health.

  6. Neat idea. I’d like to see some amount of marrying between the knobs/buttons and the screen. Like the newer Waldorf stuff (and tons of others).

    I’d rather it be a USB host than include 16 more drum pads I don’t need in my studio.

  7. So we’re all just going to embrace software synthesizers being loaded into hardware interfaces, without any consideration for how the hardware interface has a specific workflow?

    1990’s ROMplers were a pain in the ass to program because of a lack of physical controls. you got +1 / -1 buttons or maybe a jog-dial, but then layered behind a 2 row 16 character LCD there were pages and pages of menus. NO FUN FOR ANYONE.

    2020’s synths have some great interfaces. Look at Korg’s line of mid-priced synthesizers: Multi-Poly, Opsix 2, Wavestate 2, Modwave 2, Minilogue XD — so many tactile controls, super-important for noodling around designing sounds, setting envelopes and filters, so much fun.

    This Open-1 is a good concept, but it will limit interface design to v number of keys, x number of pads, y number of knobs, z number of buttons. EVERY software ROM will have to be designed to follow a similar layout. That could be limiting to how we invent new sounds.

    1. bang on. AI can’t “is it fun?”

      I haven’t on an mvave but my suspicion is you get a twit-tok video and back in the drawer.

      Best compliment I ever got on a firmware was “the knobs are more responsive”. That shit takes work.

  8. The open SDK and browser emulator before hardware ships is the smartest part of this concept. A multi-firmware synth lives or dies on how many developers write for it, and letting them start early solves the classic chicken-and-egg problem. Wired-only for lower latency also makes sense at that price.

  9. I like the idea.
    But it should be a smaller device. And it should have encoders.
    With pots you will not able to make smooth multi window interfaces.
    You want to see the values on screen and be able to directly twist a pot.

Leave a Reply

Your email address will not be published. Required fields are marked *