Welcome to the Eagan Matrix Dev category.
This category is primarily for discussions about developing for the Eagan Matrix, primarily for overlays but also other use-cases.
say hi in this topic, if you are going down this new fun route 
4 Likes
Thanks for setting this up!
- Is there a way of seeing who already has access to the group?
- Anyone from Haken Audio here?
3 Likes
Yes Iām here
Happy to see a community possibly growing here, and happy to help and contribute when useful
5 Likes
This is the newly stabilised and latest Eagan Matrix MIDI protocol definition. It will be made public at some point, but until then, please keep it strictly inside this private forum.
HakenMidi.txt (102.3 KB)
1 Like
Welcome Christophe! Glad to see you here.
I have ContMidi.h and the HE package as of 10.34. Whatās the best way to stay current with updates? I donāt want to be a bother and keep pinging Lippold. I know others have more recent versions, and I donāt think itās a great idea to be sending copies around privately. I donāt have any overlays or overlay presets.
If thereās a good way for the people in this group to stay current, we can avoid some confusion, and working together we can reduce the amount of redundant bug reporting.
1 Like
the file has ātagsā for 10.35 so its pretty easy to see changesā¦ and ofc, you can just diff it 
personally, what Id recommend isā¦
a) put ContMidi into private GitHub.
Haken can create a GitHub (for now) PRIVATE repo, and then can invite developers (aka contributors) to grant access, on release repo can be made public.
having it under version control, will also allow for comments/change log.
b) license.
for 3rd parties to use this file (which I think is to be encouraged.)
this file needs to have something like an MIT license associated with it.
I donāt personally see why this would be an issue, it is not an implementation its just a bunch of definitions, only useful to be used with haken products
the current ālicenseā , is incompatible with 3rd party GPL projects, and risky for commercial projects alike
// Haken Audio Midi Protocol by Lippold Haken, (C) Copyright 1999-2024.
c) ideally, itād be nice to have the header file also delivered with the firmware.
so that we know on release that the header file and firmware match
but hey, this kind of project organisation, vital once you get 3rd party devs involved, will take a little time to evolve - as its a broadening of interests from a select group
yesā¦
on left hand side, you can selects groups ā¦ and it the EaganMatrixDev group (unimaginative I know!)
hereās a shortcut - https://community.polyexpression.com/g/EaganMatrixDev
note: only mods/admins and members of the group can see itā¦ its top secret 
2 Likes
I vociferously concur on every point.
1 Like
I agree with you Mark, also these are things to done before final release, there is probably no real hurry for now.
Note that the ContMidi .h has been renamed HakenMidi.h - HakenMidi.txt
2 Likes
noted, and update , thanks
note 1 : Iāve added .h/.c as allowed extensions so you donāt have to rename now.
note 2: your mixing up your cr/lf convention within HakenMidi.h
1 Like
The firmware implementing the overlay protocol et getting more and more stable (and full feature). Here is a link to the 10.38 that you may use to test your developments. Of course, please keep it inside this group for now.
Haken Editor 1038.zip - Google Drive
4 Likes
Thank you, Christophe! ā Iāve been holding off further development until I get something newer than 10.34. Now that my Kitchen is nearly done, I can return to EM development.
Few random immediate thoughts:
-
Happy to see HakenMidi.h included in the package. Up to now Iāve had a newer header, but no firmware to go with it. Thank you!
-
Built-in Kenton support has been removed from the FW, so Iām curious why thereās a Kenton Firmware folder included in the distribution. The readme in that folder doesnāt seem to mention anything about the Kenton support level in the post-10.09 firmware.
-
ContinuuMini Summary Sheet.pdf says itās for 10.09. No idea if itās all still current. Iāve been meaning to invite RK here, though heās resisted to being in forums other than FB.
-
The Beatstep templates appear to be old ones. Itās likely that theyāll need updates for the new FW. The docs are powerpoint files, probably better off as PDF so that more people can access them.
-
Given all the videos Josh Madoff has made showing him using the NanoKontrol2, it might be nice if a good template for it were included. Josh told me he started with mine that I shared on the forums. Iāve made some improvements and Iāll be updating it for the new FW. If youāre interested in the contribution, Iād be happy to provide it along with documentation (just need a deadline :-).
1 Like
Hi Paul,
Thanks. This is still a work in progress and the doc and accompanying files are not updated yet.
Thanks for the NanoKontrol2. Iām not sure what is the best way to go, as you mentioned some support were dropped (but I know that there are discussions about the Kentonā¦), maybe we should share these type of files outside of the firmware distribution.
1 Like
I really like the idea of having a separate place for the 3rd party data/info.
The RK guides are essential across the EE/Haken ecosystem, but he doesnāt have a good distribution story for new docs/templates and updates.
1 Like
@Anckorage : Whatās the preferred way to report issues with the new FW/editor? support@hakenaudio.com?
Probably too easy for things to get lost in discussion here, and Lippold will see everything on support.
I need to do more investigation, but it seems that MIDI from external controllers are not getting routed to the device in the Haken Editor, despite being configured for input and the MIDI routing looking correct in HE.
1 Like
Reporting directly to Lippold is definitely NOT the best way to go
We need to have well ātestedā and repeatable bug and sort them by priority (Iām still not reporting minor issues for this firmware).
Not routed external controllers seams weird to me, since my Osmose is always routed to my Slim and EM ā¦
1 Like
Narrowed this down:
My NanoKontrol2 was configured to send on Channel 16. Ch 16 works fine when routed to the device using something other than the Haken Editor. Changing the NanoKontrol config to send on Ch 1 works with the 10.38 HE.
The changes from the controller are still not reflected on the dials in the Haken Editor. In 10.09, twisting the knob on the controller updates the knobs in the editor so you can see the exact values that the engine is using. The external MIDI is reflected to the device MIDI output (on ch 16). This reflection doesnāt happen with the new firmware, so the UI doesnāt update in both HE and my VCV Rack plugin. The lack of visual feedback makes it much harder to use the editor or my plugin with an external controller, especially when you want to dial in a setting by the numbers.
In 10.35, MIDI from my Keystep32 was seriously broken, but the Keystep32 is working just fine now with 10.38.
1 Like
are you talking about macros i-vi ? other macros ? any other CC and dialog ?
Also check the new MIDI log in the 10.38 editor, it is much much better than before and will help understanding the dialog
1 Like
Havenāt checked out the logging yet.
As for lack of MIDI reflection to ch16 from external controllers like the NanoKontrol sending on channel 1, itās the same for everything Iāve mapped on the controller: Macros i-vi, post level, pedal values, and the recirculator controls. I can observe the same behavior in the Haken Editor and using VCV Rack and my plugin. In my plugin, I do see the initial values of all the parameters when a preset is changed or requested using ch16 cc109, 16.
1 Like
Thanks for adding me to this group!
Currently discovering how to communicate with 10.38 macros from Max patches.
I notice the same thing about macro i to vi, they do not graphically update.
Regarding graphs, when I send a stream poke, they donāt graphically update either. However, if I switch on tab C1 (for example) and then switch back on graph, the 48 sliders are updated.
1 Like