For future reference:
After hours and hours the last weeks and another few hours today, I managed to get it working:
The problem is that the identifier for the Erae 2 is different from the one of the Erae Touch, but the API docs show only the one for the Erae Touch.
So for adressing the Erae 2 the first Bytes should be:
Please Embodme, update your API docs and add this information. :)
Thanks.
Hi Felix,
We apologize for the trouble and thank your very much for sharing this !
We updated our API doc in the manual for the Erae2, you can download the ERAE API V2 specification form our manual page:
https://www.embodme.com/manual/erae-manual#api-sysex
We also provided an example in Python to use it :)
Do not hesitate to reach out if you have any issues with it!
Thanks again !
Cheers
Felix
Hey there,
I'm working on a bitwig controller-script for my Erae 2.
The MIDI side already works fine. However my ultimate goal is a simple clip launcher controller for Bitwig (because sadly, there is no script for the Ableton Live widget).
For this I wanted to use the API-mode.
However, as dumb as I am, I cannot get this API mode to be enabled. I understand, I'm supposed to send a specific Sysex-Message to enter API mode and get some data in, namely this:
F0 00 21 50 00 01 00 01 01 01 04 01 RECEIVER PREFIX BYTES F7
I tried to get this to work in Bitwig and Pure data for hours now, without success. Any hints on this, or simple working examples?
Are the Receiver Prefix Bytes free to define or need they to be some specific bytes?
I'm sure I'm just missing something simple here, am I?
1 person has this question