15 posts - 9 participants

Read full topic

It provides 5 api zone pages mapped to various common bitwig tools and workflows, keyboard, drum pad, clip launcher, Linnstrument style MPE play layout.

I needed something for bitwig, couldn’t find a preset or extension so rolled my own.

I hope it helps someone else.

Cheers!

1 post - 1 participant

Read full topic

a couple of important observations

• Erae Lab is not updated, remains at 1.6.3
• v1.1.3 seems to have been withdrawn (and no mention of 1.1.4)
  I’d take to mean there was an ‘issue’ so upgrading is likely a very good idea!

pretty extensive change log this time around !

CORRECTION: 1.1.5 change log is identical to 1.1.3
so indeed, seems like a replacement for some reason.

caveat : one line, for both, is “Other miscellaneous fixes and stability improvements”, so this could cover additional bug fixes, that were not in 1.1.3.
but there is no transparency, on what and why 1.1.5 fixed or was necessary

change log

V.1.1.5

New Features

Expanded Layout Capacity‍

Layouts now support a much larger number of elements. You can add up to 256 elements per layout (keyboards, drumpads, faders, etc.), enabling more complex and creative setups.‍

Element Retrigger on Slide

‍New ability to slide between multiple 1D Fader, Keygrid & Drumpad.

‍Arpeggiator Quantized Mode‍

New quantized mode for the arpeggiator:

• When enabled, the first note is quantized to the MIDI clock grid

• Ensures arpeggiator patterns start perfectly aligned with the beat

Auto-Load Last Project‍

The device automatically loads the last used project on startup.

Improved Project Saving

• Select which project slot to save to (instead of always overwriting the current slot)

• Current project is marked with " *" in the save menu

• Currently loaded project slot is highlighted

Element Selection Mode‍

Hold the Mapping button to enter selection mode:

• All LEDs dim except the currently selected element

• Touch an element to select it for editing without triggering it

• Helps you quickly identify element on the playing surface

Key Fadeout Animation

‍Keys now fade out gradually after release instead of instantly returning to their inactive state, for a smoother visual experience.‍

Scale Selection for SoloKey‍

Added LCD menu to select musical scales directly on SoloKey elements.

‍CC on Layout Change

‍New project setting to send MIDI Control Change messages when switching between layouts:

• When leaving a layout: sends CC with value 0

• When entering a layout: sends CC with value 127

• CC number corresponds to layout index: CC 102 for Layout 1, CC 103 for Layout 2, etc.

• Messages are sent on MIDI channel 16 via USB Device output

• Useful for triggering scene changes in your DAW or lighting software

Looper Improvement‍

Quickly double/halve loop length while editing loop length by clicking +/- button — no need to hold the click wheel anymore.

‍Layout Button Glow on Gesture Activity‍

Layout buttons (N1-N8) now glow dynamically when playing on non-visible layouts. Glow intensity is proportional to touch pressure and movement speed.‍

CV Output Support for Footswitches

‍Footswitch settings now support Control Voltage output configuration.

Bug Fixes

• Fixed arpeggiator parameters not being saved correctly

• Fixed multi-finger note tracking for solo keys and keyboard keys

• Fixed footswitches not responding

• Fixed duplicate footswitch press/release events

• • Fixed looper clearing last gesture on other layouts when using layout+Return to clear one or more patterns

• Other miscellaneous fixes and stability improvements

Performance Improvements

• Improved MIDI clock timing precision with reduced jitter

• Improved animations render speed

• Global performance improvements for smoother operation

Behavior Changes

• External MIDI clock messages now follow configured routing rules instead of automatic propagation

‍

2 posts - 1 participant

Read full topic

I’m now at a stage where I’m completely stuck. I need a completely new workbench preset written, where each of the rows transmits chromatically on its own unique midi channel, and where the scaling is reversed from the standard. I’ve tried to explain what I need in this short video - https://www.youtube.com/watch?v=0ilVb0NtFsA

I don’t need any menu options on the Tau itself, as I can transpose within Ableton Live itself. I just need the Tau to act as a simple midi controller. Is there anyone who can help me with this? Trying to understand Workbench just destroys my brain.

Thanks in advance x

22 posts - 3 participants

Read full topic

7 posts - 2 participants

Read full topic

Just got mine yesterday - fully enabled.

Transparent multi-client for existing Midi1 devices? yep. It just works. (as far as I can tell so far). Just connect your various software to the device, only you can now run them at the same time. Nothing special to do. It’s actually boring in the best way.

If you want to configure virtual cables and such, you need to download the SDK for the tools.

3 posts - 3 participants

Read full topic

It was a bit surreal to see as the proportions when mounted to the props are a bit wacky and mind-bending, oversized uncanny valley…

- YouTube

1 post - 1 participant

Read full topic

- YouTube

Video just got selected for public voting, final 12 videos.
https://forum.modartt.com/video_contest.php

1 post - 1 participant

Read full topic

Pedro Eustache I think does this in a daw with the sylphyo, but it’s only for mac OS - I don’t remember the name, but he binds it to elevation or the slider.

What I tried was using the insert piz here midichords plugin with a midi pedal, bind it to a CC when pressed, then bind that CC to Reaper actions to go from one track with a preset of chords, to another without, but the pedal I got from temu is not great. Three out of 4 buttons encounter some slight resistance when going down, and buttons 2 3 and 4 have increasing latency compared to the first (and that might be because it’s cheap), so I’m considering sending it back. I can literally hear it creak lol. Maybe someone could recommend me a better product from a reputable brand?

Still, I’m not completely convinced, because it’s tricky to synchronize the pedal button to trigger right before the start of the note and there might be some inherent latency…

Insert piz here midichords uses midi program change to swap presets, but midi program change causes an audible drop, and it’s not convenient to use on the sylphyo where you have to press the sylphyo button on the front above the sensors and do a combination of inputs…

Maybe there’s a more convenient way to do this by binding elevation or the slider to chord presets?

The tricky part would be to bind specific zones of the sylphyo slider (or degrees of elevation), which means some specific range number of CC75 for elevation or CC1 for the slider if I’m not wrong. Reaper can’t do that with actions. Maybe there’s some kind of harmonizer that can be controlled this way? So I can map different zones to different types of chords, and one zone is no chords.
Otherwise, binding the slider to activate chords/deactivate preset chords would work too, but that still requires a zone that acts as off switch and one that acts as on switch.

PS: chord preset means every note is set so play some specific pre-defined notes at the same time, if that’s not clear. You can do that with the ripchord or insert piz here midichords plugins.

I’m using an aodyo sylphyo, as a midi controller for the GS Strum 2 plugin.

3 posts - 2 participants

Read full topic

Ive not installed yet, will later today… seems some nice additions.

I wonder if the " * Improved MIDI connection reliability" of Erae Lab will solve the issues some had in 1.1.2/1.6.2?

EDIT - important note?

with the release of 1.1.5 (see separate post), it appears Embodme have withdrawn 1.1.3, - 1.1.5 is a replacement, with a very similar feature set.
Id say its likely (?) there were issues with 1.1.3 so was removed, so Id recommend upgrading

Erae 2 Firmware

V.1.1.3

New Features

Expanded Layout Capacity‍

Layouts now support a much larger number of elements. You can add up to 256 elements per layout(keyboards, drumpads, faders, etc.), enabling more complex and creative setups.‍

Element Retrigger on Slide

‍New ability to slide between multiple 1D Fader, Keygrid & Drumpad.

‍Arpeggiator Quantized Mode‍

New quantized mode for the arpeggiator:

• When enabled, the first note is quantized to the MIDI clock grid

• Ensures arpeggiator patterns start perfectly aligned with the beat

Auto-Load Last Project‍

The device automatically loads the last used project on startup.

Improved Project Saving

• Select which project slot to save to (instead of always overwriting the current slot)

• Current project is marked with " *" in the save menu

• Currently loaded project slot is highlighted

Element Selection Mode‍

Hold the Mapping button to enter selection mode:

• All LEDs dim except the currently selected element

• Touch an element to select it for editing without triggering it

• Helps you quickly identify element on the playing surface

Key Fadeout Animation

‍Keys now fade out gradually after release instead of instantly returning to their inactive state, for a smoother visual experience.‍

Scale Selection for SoloKey‍

Added LCD menu to select musical scales directly on SoloKey elements.

‍CC on Layout Change

‍New project setting to send MIDI Control Change messages when switching between layouts:

• When leaving a layout: sends CC with value 0

• When entering a layout: sends CC with value 127

• CC number corresponds to layout index: CC 102 for Layout 1, CC 103 for Layout 2, etc.

• Messages are sent on MIDI channel 16 via USB Device output

• Useful for triggering scene changes in your DAW or lighting software

Looper Improvement‍

Quickly double/halve loop length while editing loop length by clicking +/- button — no need to hold the click wheel anymore.

‍Layout Button Glow on Gesture Activity‍

Layout buttons (N1-N8) now glow dynamically when playing on non-visible layouts. Glow intensity is proportional to touch pressure and movement speed.‍

CV Output Support for Footswitches

‍Footswitch settings now support Control Voltage output configuration.

Bug Fixes

• Fixed arpeggiator parameters not being saved correctly

• Fixed multi-finger note tracking for solo keys and keyboard keys

• Fixed footswitches not responding

• Fixed duplicate footswitch press/release events

• Fixed looper clearing last gesture on other layouts when using layout+Return to clear one or more patterns

• Other miscellaneous fixes and stability improvements

Performance Improvements

• Improved MIDI clock timing precision with reduced jitter

• Improved animations render speed

• Global performance improvements for smoother operation

Behavior Changes

• External MIDI clock messages now follow configured routing rules instead of automatic propagation

Erae Lab

V.1.6.3

New Features

- Drag and Copy: you can now drag and copy multiple elements at once by holding theOption (on MacOS) or Alt (on Windows/Linux) key

• Multi Elements Edit: you can now edit multiple elements at once. Selecting multipleelements will show the intersection of editable parameters.

‍

Improvements

• CC/CV values auto-increment whenpasting to the same layout, but are preserved when pasting to a differentlayout

• Program Change buttons withLayout/Project change preset now send on release

• A/B states of Program Change &Control Change Buttons/Footswitches renamed to ON/OFF

‍

Fixes

• Improved MIDI connectionreliability

• Fixed crash when loading layoutsfrom older versions

• Fixed arpeggiator parameters notapplying correctly on layout push

9 posts - 6 participants

Read full topic

9 posts - 4 participants

Read full topic

Open to selling person to person. (Or in person with cash if you happen to be close! → Loveland, CO)
Also selling through reverb → https://reverb.com/item/93483018-striso-board-2022

My mom made the case. The outside is made from sturdy cotton. The in-side is lined with a smooth polyester similar to tent making material. Means the pads on the striso don’t stick as you pull it out. The whole thing is padded with 4 layers of batting. Super cushy. There are two pockets inside: one with a little more padding for the striso, and the other for wires and such. Zips up nice and has a carrying loop for quick grabbing and carrying.

Updated the striso with the latest firmware as of 2026-01-16.

3 posts - 2 participants

Read full topic

quray.music

Quray — Air MIDI/CV Сontroller for Motion-Controlled Sound

Discover new possibilities in music with Quray. An intuitive MIDI controller that lets you control sound with motion.

The video makes me rather suppose that it is a multi beams controller, a little like the old Cristall Ball ? Crystall Ball by Naonext

2 posts - 2 participants

Read full topic

I’m trying to reconfigure the Striso to send cc1/cc2 as x/y keymovement. I at least try to get rid of pitchbend on the “iP1Mx” value. Pitch is just too hard for me to control this way.

However, if I set iP1Mx to “2” (breath control), and save the whole config to preset #1 that is selected as the preset to boot into, iP1Mx still sends pitchbend. Even if I load that preset explicitly. Same behavior when setting “127”, meaning “do nothing”.

If I reconnect the Striso as a drive, the web interface (which is very cool BTW) does show iP1Mx as sending cc2. But maybe the board still works from the older configuration? It does go into into “pythagorean” tuning.

I’d appreciate some help.

3 posts - 2 participants

Read full topic

The only thing is that a couple of keys might make a short squeaky noise, like a click, sometimes and especially when bending them horizontally for pitch bending – a main reason to get this keyboard. Nothing bad, nothing affecting the actual sound, nothing really disturbing, but it’s an irregularity and it’s there.

On the other hand, I understand that this keyboard is really complex and it has many moving pieces, so maybe it is somewhat “regular” to have this irregularities? This problem doesn’t bother me enough as to return the keyboard to be “fixed”, especially when I’m about to start my holidays and I will have more time than usual to play with this new toy. But still, I’m interested to hear from other Osmose owners whether this is normal or not, whether it is expected to stay like this, go away with the use or get worse…?

Probably quite subjective, I know, but I welcome any feedback and advice.

6 posts - 4 participants

Read full topic

3 posts - 2 participants

Read full topic

7 posts - 4 participants

Read full topic

This is the new editor rewritten in C/C++. Starts instantly, Overall performance is improved. On my Windows machines, the display is sharper and clearer. You can run two instances at the same time to control two EM devices, as long as no two instances have any connection to the other device, even as an input. This is pretty much expected on Windows, but if there were cross-instance communication, this could be solved.

With the release, Haken Audio is messaging a transition to a new generation of developers.

If you were looking for innovations in the metaphor to make it easier to program EM presets, this update is not that. It is a faithful re-creation of the old interface, down to the themes and fixed scaling steps. There are some little changes in the UI for pedal assignments and other features, but nothing ground-breaking. The new editor looks to be Unicode-aware, and shows indications of being able to be localized into multiple languages pretty easily.

For developers, the updated HakenMidi.h now documents the format of download data for Tuning grids and for Loris synthesis data. This opens up some new opportunities for third-party innovation in these areas.

25 posts - 10 participants

Read full topic

5 posts - 3 participants

Read full topic

3 posts - 2 participants

Read full topic

its latency is ok, but its easy to overwhelm the midi data stream (with an appropriate controller).

so I was testing a new version of the Eigenharp software, and notice if I ‘strummed’ the Alpha keyboard quickly, lots of notes, lots of mpe data.

after I finished the strum, the Osmose would be still playing 2 seconds later !
i.e. was taking 2 seconds to catch up.

ok, this was not ‘normal’ use, if you play then it seems to be ‘ok’ , though I could provoke latency if I really tried.

even throttling didn’t seem to help much…

naturally, I assumed it was my software, even though Id need no real evidence elsewhere…

so,
a) I plugged in my Eagan Matrix Module, exact same setup, works perfectly…
no latency or backing up what so ever !

b) I recorded the MPE notes in Ableton.
perhaps the Eigenharp was bottlenecking?
nope, looked fine in Ableton, and again send that MPE stream to Osmose, and it backs up…

I also tried direct connecting osmose to Mac… in case hub was overloading, no difference…I also tried via usb->din , same issue.
(runs on the osmose keys are fine… so it feels like an interfacing issue)

it truly looks like the Osmose has some kind of buffer / bottleneck between the EM within the Osmose and the ports usb/din, that is somehow throttling the input.

odd, thing is… Im sure I tried this when I first got the Osmose, and don’t remember it - so perhaps a change in Osmose FW?
or off, its possible I didn’t to this exact same test, but it does feel like it’d be pretty noticeable!

anyone else with a similar experience?
note: you’ll need very high density to provoke

edit: sent an email to expressivee , not sure if they will be interested… as more complex setups are hard to ‘trust’, and it may be considered an ‘extreme’ use case.

19 posts - 6 participants

Read full topic

Phase : Beta-2
Current Status : Beta 2 available
Beta Images :

Report Issues Here (link)

Current Scope

• Functional testing
• macOS - Apple Silicon
• Pico, Alpha, Tau
• EigenD, Workbench, Stage
• Installer
• Factory Setups (and your own)

(out of scope - see follow up post; tl;dr come back soon !)

Issue Reporting

discussions here, but report via GitHub issues.
(you can sign up for a free GitHub account if necessary)

Issue Reports : https://github.com/TheTechnobear/EigenD/issues

Search for existing first, add comments on those.
Fill in as best you can, it really helps esp. simple / quick reproducible steps.

Status Tracking

Overview :
User: open
Dev : open → confirmed, in-progress → fixed
OR
Dev : open → confirmed, in-progress → won’t fix (closed)
on next (beta) release:
User: fixed → verified (closed)

note: won’t fix - really mean “wont fix now” -
likely not reproducible, out of scope
(more details in follow up post)

Testing Strategy / Reporting

good testing and reporting will make my life a lot easier, and so get bugs fixed faster. (more details in follow up post)

Special Coverage - Agents.

below is all the agents we have, each needs testing.
Testing must include

• adding within Workbench
• editing in Workbench
• deleting in Workbench

preferably with wires attached, and editing whatever attributess the agent has.

why so detailed?
because each agent has its own python code.this code is NOT used when you are just using it in a setup, but is used when you modify it.

please marked ‘tested’ when done.
raise issue if you find any bugs (there is an agent field)

Agent List

• ableton_push - OK (no description)
• ahdsr - OK
• alpha_manager - OK
• arranger - OK
• audio - OK (no default buffer size)
• audio_unit - OK (confirmed fixed in beta 2)
• blownstring - not in agent list
• cello - OK
• clarinet - OK
• clicker - OK (no description)
• clip_manager - OK (confirmed fixed in beta 2)
• conductor - OK (confirmed fixed in beta 2)
• console_mixer - OK
• continuum - OK
• controller - OK
• convolver - OK (no impulse found, could the “old” ones be included?)
• cycler - OK
• delay - OK
• drummer - OK (file browser not properly tested, didn’t have any Apple loops)
• envelope - OK
• finger -OK (confirmed fixed in beta 2)
• gain - OK
• illuminator - OK
• keyboard - not in agent list
• keyboard_controller - OK
• keygroup - OK
• labeler - OK
• ladder_filter - OK
• language - (if this is interpreter - OK apart from additional instance cause crash)
• latch - OK
• livepad - OK
• metronome - OK
• midi_clock - OK except tempo slider has extreme range
• midi_converter
• midi_device
• midi_input
• midi_monitor
• midi_output
• midi_pgm_chooser
• midi_processor
• osc_output
• orb
• panner
• panpipe
• pico_manager
• player
• polyphonic_summer
• ranger
• recorder
• rectangle_osc
• rig
• sampler
• sawtooth_osc
• scale_illuminator
• scale_manager
• scaler
• scheduler
• shaper
• sine_osc
• soundplane
• stringer
• strummer
• summer
• synth_filter
• t3d_device
• t3d_output
• tabulator
• talker
• triangle_osc

123 posts - 9 participants

Read full topic

It’s the 3rd attempt, over many years (6+?)

this time its for real…this time it works…
It may not look different, but under the hood, pretty much everything has been update.

what’s new

release scope undecided yet… but here is what is already done.

• Native Apple Silicon support.
• Python 3.14 - latest version
• Juce 8 - latest version
• Scons 4 - latest version
• C++17
• Convolver is back (using latest fftw)
• Improved build support
• Dev documentation !
• Improved Windows development environment (ongoing)

(the above has also required fixing some latent bugs )

Status

Tested only on Mac Apple Silicon.
Testing shows all setups loading and appear to work.
Testing with Alpha/Tau/Pico no issues.

however, I need decide on scope of ‘deliverable’
Ive so many ideas, but it might be better to get his out in the wild, to check stability, also a beta test has much more 'coverage e.g. testing plugins/ midi.

Next steps

Mac
Beta test?
a lot of code has changed, in pretty fundamental ways.
Im almost certain there will be issues… even if I haven’t found them yet

Windows
No testing yet, but the code etc is cross-platform so should be ok
Ive started improving build environment for it, so that needs testing and no doubt further work on…also installer has been tweaked.
I hope to get access to a window machine later this week to start on it.
Beta testing after that…

Linux
already improved, I need to test and frankly, its a lower priority, as Im not sure anyone is really using
It’s likely it’ll stay ‘experimental’ just because its not getting the usage for me to be really confident in it. - also, Ive no idea what platforms to release on.

for ‘real’ release, Im hoping to move to GitHub actions aka automated release.
If I do, that would make releasing to non Mac (M series) much easier for me, and so helpful improve release cycle…
another step in modernisation.

Why 3.0?

coincidence of Python 3, my 3rd attempt.

but also, because it feels like a major step forward, a modern toolset and environment.
frankly, 2.x felt like a dead-end - Id pretty much given up on its future, it would die when Python 2 dies.

Now actually feel more confident, and even motivated excited to develop for it - I have ideas for the future !

10 posts - 6 participants

Read full topic

- YouTube

Definitely an interesting development, and nice to know that there are still new MPE designs coming out.

I am curious if it somehow can do per-note pitch bend, which is a big part of MPE. I am guessing no…

9 posts - 5 participants

Read full topic

3 posts - 2 participants

Read full topic

The official reveal/launch data has clearly not arrived at the time of me writing this post, but Expressive E themselves have started teasing it on their own facebook page:

EDIT : add new promo (says available now - 12/11/25)

- YouTube

35 posts - 7 participants

Read full topic

Thanks in advance!

9 posts - 3 participants

Read full topic

I wonder if someone might take the time to measure one up, just to get the basic stats like length, width, thickness, and ideally things like where the keyboard starts and ends.

I’ve been Eigenless for a while, but I couldn’t resist a Pico that recently surfaced on Reverb. I guess features like the keys and buttons are the same size…?

(If I’d caught that inaccessible Utah one when they finally listed it on Reverb recently, I’d have snapped that up, though I wondered if that might be the one @Clarkalex picked up with a missing base station.)

Thanks,

Ben

4 posts - 3 participants

Read full topic

1 post - 1 participant

Read full topic

17 posts - 6 participants

Read full topic