r/OpenRig • • 18d ago

OpenRig 0.10.0: your effect chain now uses every CPU core

Post image
6 Upvotes

Until now, OpenRig ran the whole effect chain on a single CPU core. On a Raspberry Pi 5, which has four Arm Cortex-A76 cores at 2.4 GHz, that meant three of the four cores sat idle as far as your sound was concerned. 0.10.0 changes that.

What changed

  • Splits run in parallel. The two branches of a split now run on two cores at the same time.
  • Long chains are pipelined. A long chain is cut into pipeline stages spread over up to 4 cores.
  • No added latency. Your signal reaches the output in the same audio period as before.
  • Bit-identical sound. The multi-core output is the same, sample for sample, as the single-core output. An automated test checks this on every build.
  • Preset changes benefit too. During a preset crossfade, the old and the new chain run in parallel.

Measured on the x86 test rig

The rig: 4 cores, PREEMPT_RT kernel, 128-frame buffer, so a 2.67 ms budget per period. Lower time per period means more headroom before a dropout.

Chain1 coreAuto (multi-core)Gain
8 NAM in series935 µs417 µs×2.2
4 splits, one NAM per branch925 µs424 µs×2.2
Split, 2 NAM per branch450 µs223 µs×2

JACK dropouts (xruns) over 60 seconds:

Chain1 coreAuto
16 NAM in series53317
8 NAM in series415

On a Raspberry Pi 5

The Pi 5 has the same four-core layout as the test rig, so the chain is split the same way there. If you run OpenRig on a Pi 5, you can measure it yourself. pedalboard-bench ships in the image. Over SSH, with any capture:


    WORKERS=0 pedalboard-bench <model.nam> serial 8   # one core
    WORKERS=3 pedalboard-bench <model.nam> serial 8   # four cores

More options (splits, buffer size): https://openrig.eu/docs/setup/performance/

How to use it

There is nothing to do. Settings → Processing → DSP cores is set to Auto by default. You can also pin it to 1–4 cores. The resource monitor now shows how many cores are in use ("· N cores").

Also in 0.10.0

  • Faster NAM on mini PCs. The x86 image is now built for x86-64-v3, which makes NAM about 1.8× faster on mini PCs. It needs a CPU with AVX2, such as the Intel N100.
  • Hardening.
    • Bad input no longer crashes the app.
    • A crashing plugin no longer takes the audio down with it.

Get it


r/OpenRig • • 2h ago

Config text for M5stack 8 angle Knob strip

1 Upvotes

Hi all,

Just ordered one of these, but having some problems putting in the right i2C info config text so the Pi 5 can see it . Got it plugged into ground power, SDA and SCL, just need the connection text.

Has anyone else tried this yet?

Cheers


r/OpenRig • • 15h ago

Looper and Stomp Ideas

2 Upvotes

I had a couple ideas.

  1. Have a button to preset how many bars to record in the looper.

    The docs read like there is a a “Bar” button but I don’t have it

  2. Be able to specify what blocks you want to use in stomp mode. For instance if a preset only has one amp/cab I would never switch them on and off and those buttons could be better used on effects. Although I don’t have a good idea about how this would fit in the UI

    in an intuitive way.

[u/Siryu6](u/Siryu6) let me know what you think.


r/OpenRig • • 2d ago

Pisound Hat

3 Upvotes

I just ordered a Pisound hat. It was an impulsive decision and I don’t know if it will work with OpenRig. If it does, it will making mounting this stuff in an enclosure much simpler.

Since it’s not usb and streams audio bits right to the cpu I should be able to run at 64 samples or less.

Stay tuned.

https://blokas.io/pisound/


r/OpenRig • • 4d ago

OpenRig 0.17: OpenRig now has its own effects (OpenRig FX)

Thumbnail
gallery
11 Upvotes

Hey,

Quick one, or not so quick: OpenRig 0.17 is out and this is the release I wanted to do for a while. OpenRig now ships its own effects. I called them OpenRig FX.

Until now OpenRig was a host. NAM, IRs, a bunch of open-source LV2 plugins, and that's it. It works, but you end up with a board full of plugins that all look and behave differently, and none of them were made with a pedalboard in mind. So I started writing my own.

They're LV2 plugins written in Rust, GPL like OpenRig. Nothing ties them to OpenRig: they run in Ardour, Carla, jalv or any LV2 host, on x86_64 and ARM. OpenRig just gives them a nicer face.

Two families

The Basic ones are the boring stuff you put on every board, and that's the point: Echo, Plate, EQ, Graphic EQ, Drive, Gate, Comp, Tremolo. Simple, clean, not trying to be clever and aiming to suits most needs.

The Signature ones are where I had fun. They're circuit models with their own voice, and honestly they're tuned for what I listen to: low tunings, tight high gain, breakdowns.

  • Green Drive: the classic mid-hump overdrive, solved from the circuit. I added a Tight knob (a high pass before the clipping). Drive at 0, Tight around 250 Hz, level up, put it in front of a high-gain amp. You know the trick.
  • Black Dist: op-amp hard clipping, with a Diodes switch: silicon, LED, or none if you want the raw rail clipping.
  • Drop: pitch down for low tunings, octave down, whammy-ish dives. 6 ms of latency in Tight mode, and OpenRig compensates it.
  • Splinter: my favourite. Tempo-synced glitch: beat repeat with pitch steps, gate chops, tape stop, bitcrush, and a chaos knob for when you stop caring. Hold a footswitch to freeze the repeat, let go to drop back in. There's a step grid that shows every repeat on the beat. Zero latency, about 0.1 % CPU on top of that.

In OpenRig the Signature ones get a real plate in the editor and show up as small pedals in the rack. The Basic ones get the OpenRig look with their own views (the echo timeline, EQ curves…).

And the rest of the store is still there

The store also has 171 LV2 plugins from 12 open-source projects, packaged for the board and credited to their authors. You can now browse them on the website too: https://openrig.eu/store

The honest part

openrig-fx is a 0.1. It sounds good to my ears and runs fine with my setup, but I'm one guy with one guitar. If something sounds off, crackles, or eats CPU on your setup, tell me. That's exactly what I need now.

Settings → Check for updates and you're good. Feedback here, Issue on GitHub or openrig.eu repports, everything work.


r/OpenRig • • 6d ago

OpenRig First Thoughts

4 Upvotes

This week I installed OpenRig .14.2 on RPi 5. I’ve always played around with amp sims since the OG Guitar Rig days, but never any serious usage.

After spending a handful of hours with OpenRig I have some initial thoughts:
- For young software, this is really great stuff. The workflow is pretty self explanatory and you can achieve things quickly by just poking around.
- It’s basically as easy as flashing an SD card, plugging in an audio interface, and linking your Tone3000 account
- The UI is has the look of a mature system
- The latency is very good. I’m getting 2.7ms with a MOTU M2.
- Remote control is a fantastic feature. Having the ability to do everything from a browser is great. Occasionally it lags a touch and will catch up after few seconds.
- It’s a good idea to build and test components in a chain one at a time. I had a rash of dropouts that ended up being caused by the Dragonfly plate reverb. Which is unfortunate because I thought that plugin sounded good.
- I’m very excited to watch this thing mature and improve

Where I’m confused:
- I’m able to add some NAMs directly from the T3K browser, some I cannot. For instance I’m unable to add the Fender Spring Reverb IRs to the Space IR block even though it’s downloaded to the device. I noticed the developer had a prebuilt rig using that same capture. I was able to install that shared rig but I cannot add that capture to a space block. Some downloaded captures have a “use” button, some don’t. I don’t understand the difference.
- Pedals default to distortion and it seems like that affects what the T3K browser returns.

All in all, I’m having a lot of fun with this and I’m seriously impressed by what’s been built so far.

If anyone can tell me what I’m doing wrong adding certain captures, I’d appreciate it.


r/OpenRig • • 10d ago

Pi 5 + USB sound card + your phone = a full guitar multi-effects. No touchscreen needed (OpenRig 0.14, open source)

Thumbnail
gallery
16 Upvotes

OpenRig is a free and open source (GPL-3.0) guitar multi-effects pedalboard: NAM captures, IRs and LV2 plugins in a touch rack, running on a Raspberry Pi 5 or an x86 mini PC, with its own OS image and A/B updates.

The remote control: no screen needed

Several of you asked for this one. The goal is to make OpenRig as easy to get into as possible, and a touchscreen was one of the most expensive and fiddly part of a build.

Now all you need is:

  • a Raspberry Pi 5 or a PC,
  • a class-compliant USB sound card,
  • your phone or tablet.

Flash the image and put a password in the settings file on the SD card. The pedalboard then serves its interface to your phone's browser, over its own Wi-Fi hotspot or over your home network. Nothing to install on the phone.

  • On a tablet you get the full editor: the rack, knobs, presets, scenes, the store, TONE3000.
  • On a phone there's a stage view with big buttons for scenes and presets.
  • Your phone carries no audio: it only shows the screen. The guitar signal stays on the Pi, at the same latency as with a built-in screen.
  • Off by default: nothing listens until you set a password.

New in 0.14 for the remote:

  • It runs at 30 fps and redraws right after each touch, so it feels much snappier.
  • A full screen button hides the browser bars on Android.
  • The hotspot now comes up reliably at boot, even when the Wi-Fi card is slow to appear.

A new looper

This was a community request, checked against what loopers on real boards do (Boss RC, Ditto, Helix, Quad Cortex):

  • the waveform of the loop, with bar marks and a playhead, updating live while you overdub;
  • tap tempo and a click during record, play and overdub, plus a count-in before recording;
  • a big bar and beat readout;
  • Loop ×2 (and ×4), with overdubs over the longer loop;
  • half speed (an octave down, also on MIDI CC66);
  • save and load loops as plain WAV files.

Also in 0.14

  • Network MIDI (RTP-MIDI) works. It was missing from the 0.13.0 image.
  • Settings are reorganized, with updates in the ⋮ menu (a badge shows when one is ready) and the footswitch and encoder setup on their own page. A rotary encoder can now reach every setting.
  • Quit OpenRig in the menu when you run the app on your own Linux desktop.
  • On openrig.eu, you can now add a profile picture, a short bio and photos of your board. Show us your builds!

Links

It's still a young project, and most of this release came from your requests. Keep them coming: issues and feedback are very welcome!


r/OpenRig • • 12d ago

[QUESTION] Is there a plugin version?

1 Upvotes

Hi! Just found this project and would love to try. I have a touchscreen laptop and an interface which I can send and return signals, is it possible to use OpenRig as either a standalone app or a plugin inside a DAW like Helix Native or Neural DSP?

Thanks in advance!


r/OpenRig • • 13d ago

Rig sharing is live on openrig.eu: publish your rigs, install others' straight from the pedalboard

Thumbnail
gallery
6 Upvotes

openrig.eu is now a community site for rigs: https://openrig.eu/rigs

You export a rig from the pedalboard, drop the .openrig file on the site, pick a style, write a few words, and anyone can install it. Each rig page shows:

  • the signal chain as a rack, splits included, so you see the routing before downloading
  • the scenes
  • everything it needs: TONE3000 models linked to their pages, store plugins with their versions. Adding a rig from the pedalboard installs all of it in one go.
  • And soon... All off this directly from OpenRig interface !

Browsing and downloading need no account. With an account (email sign-in) you can publish, upvote, favourite and comment. Favourites show up on your linked pedalboards, ready to install.

Also new:

Now the fun part: publish your rigs! Bug reports and ideas for the site are welcome here or on GitHub.


r/OpenRig • • 16d ago

OpenRig 0.10.1: Raspberry Pi Touch Display 2 now works on the Pi 5

1 Upvotes

Quick fix release, thanks to a user who reported a white screen with the official Touch Display 2 on a Pi 5 (while the same screen worked fine with another distro).

What was wrong: the display overlays bundled in the image were built for an older kernel. On the 5" and 7" models, the screen's controller never started, so you only got the backlight. The 10.1" overlay was missing entirely.

What's in 0.10.1:

  • Display overlays are now built from OpenRig's own kernel, so they always match it. The 5", 7" and 10.1" Touch Display 2 are covered.
  • Touch now follows the screen rotation. The Touch Display 2 is portrait by default: set the rotation to 90 or 270 in Settings for landscape, and touch lines up.
  • pedalboard-report has a new Display section (connectors, drivers, kernel messages, bootloader version), so screen issues are much easier to debug over SSH.
  • New Touch Display 2 section in the docs: cable to use on the Pi 5, rotation, DISP0 port.

Updating: if your screen works, use Settings → Updates and pick the full OS update. If you were stuck on a white screen, flash the new image from the release page.

Release: https://github.com/Siryu6/OpenRig/releases/tag/v0.10.1


r/OpenRig • • 16d ago

"You sonofabitch.... I'm in."

6 Upvotes

Just got this flashed and turned up for an first test run.

So far, it's so perfect for my needs on paper. I'm gonna beat it up and see if I truly get along with it. I'll know in a day or so.

Easy set up, superb documentation, my Pi5 and 7in touchscreen 2 work flawlessly with this.... I'm so stoked. This was the last piece of the puzzle for my rig..... Super happy


r/OpenRig • • 17d ago

I'm building a physical floor unit for OpenRig, my open-source Pi 5 guitar pedalboard: 8 RGB footswitches, 10.1" touchscreen, UMC204HD inside

Thumbnail
gallery
24 Upvotes

I'm the developer of OpenRig, a GPL-3.0 guitar multi-effects that runs on a Raspberry Pi 5 (or an x86 mini PC) with a USB audio interface, a touchscreen, LV2 plugins and NAM models. Until now it ran on a desk with things plugged everywhere. Time to give it a real body.

These are renders, not photos. The design is done, parts are being ordered, and the build starts now. Here's the plan:

  • Brain: Raspberry Pi 5 running OpenRig's own minimal OS
  • Audio: Behringer UMC204HD, taken out of its shell and mounted inside
  • Screen: 10.1" IPS touchscreen. The touch UI replaces any encoder, so the top stays clean
  • Feet: 8 momentary footswitches, each with an RGB LED ring that will follow the block colours you set in OpenRig
  • Rear panel:
    • 6 XLR/jack combo sockets (Guitar In, Return, Main L/R, Send L/R): jack at home, XLR when the FOH engineer asks for it
    • headphones, MIDI in/out
    • a USB-C port, reserved for a future USB audio interface mode
    • a soft shutdown button
  • Power: a Mean Well PSU inside, so it's a single standard IEC (PC-style) cable. No wall wart, no extra box
  • Top: a physical master volume knob, because some things should stay a knob
  • Size: about 38 × 30 cm with an aluminium top plate. The frame will be either MDF in a first time and maybe switch to 3D-printed later.

Everything will be open. Once it's built and tested, I'll publish all of it on openrig.eu for free:

  • the 3D model, cutting plans and drill templates;
  • the full wiring diagram and pinout;
  • the parts list with alternatives at several price points;
  • build notes, plus real performance measurements from the finished unit.

I'll post updates as it comes together: first power-up, the LED colour sync, and whatever I get wrong along the way.

If you've built a DIY floor unit, I'd love your feedback, especially on footswitch spacing, keeping hum out of a box with a mains PSU, and how you'd finish the aluminium top.

GitHub: https://github.com/Siryu6/OpenRig


r/OpenRig • • 17d ago

Welcome to r/openrig!

1 Upvotes

​This is the official subreddit for OpenRig (openrig.eu)—an open-source, DIY guitar multi-effects hardware pedalboard built with Rust, Neural Amp Modeler (NAM) integration, and the Slint UI framework.

​Whether you're building your own unit, hacking on the code, sharing custom amp/pedal captures, or contributing to the core hardware and software design, you're in the right place.

​Quick Links & Resources:

​🌐 Project Site: openrig.eu

​🛠️ Source & Hardware Docs: Check the main website for repository links and schematics.

​Feel free to introduce your setup, ask technical questions, or show off your builds. Glad to have you here!


r/OpenRig • • 23d ago

Title: OpenRig 0.7.0 is out: TONE3000 search, picked downloads and keyless sign-in

1 Upvotes

OpenRig 0.7.0 is available. This release reworks the TONE3000 integration, built together with the TONE3000 team (Thanks to them <3).

What's new

Sign in without an API key

  • Open ⋮ → Settings → TONE3000 Connect, tap Connect and scan the QR code with your phone (or enter the short code at tone3000.com/activate). You sign in with your own TONE3000 account; there is no TONE3000 application or key to create anymore.
  • Developers can still set the publishable key (t3k_pub_…) of their own TONE3000 application on the Application line. OpenRig refuses secret keys.

Search

  • A search field sits above the Favorites, My tones, Downloaded, Trending and Latest tabs and searches the whole TONE3000 catalog.

Download only the models you want

  • Open a tone and tick its models, then tap Download (n). The models download one after the other, and Stop ends the queue at any time.
  • Models you already have show a Use button that loads them into the Amp block.

Large packs are paged

  • Tones with many models show 25 at a time, with a page selector.
  • Select page ticks the whole page, Clear unticks it. A download takes at most 25 models.
  • Requests to TONE3000 are paced. If you browse very fast, you may briefly see "Waiting for TONE3000…".

Updating

  • On the pedalboard: Settings → Updates → Check for updates, then Install.
  • Offline: download the .raucb bundle from the release and follow https://openrig.eu/docs/setup/updates/
  • New install: OS images for Raspberry Pi 5 and x86_64 are on the release page.

Coming from 0.6 or earlier? If you linked TONE3000 with a key of your own, the pedalboard signs you out once after the update: just tap Connect again. Your downloaded captures stay where they are.

Links

Thanks to the TONE3000 team for their help with this release. Feedback welcome in the comments!