EigenD 3.0 - Beta-2

Eigenharp
1

as announced in this topic EigenD has undergone major changes.
before release it will need extensive testing which I’m hoping the community can help me out with :slight_smile:

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
4 Likes
2

Tips

1. Important error in EigenD log

look for these in EigenD.0.log

igend: <rig1>: Traceback (most recent call last):
eigend: <rig1>:  File "/Users/kodiak/projects/EigenD/tmp/modules/pi/agent.py", line 146, in rpcserver_invoke
    r = func(arg)
eigend: <rig1>:  File "/Users/kodiak/projects/EigenD/tmp/modules/pi/collection.py", line 47, in rpc_listinstances
    i = self.listinstances()
eigend: <rig1>:  File "/Users/kodiak/projects/EigenD/tmp/modules/pi/collection.py", line 37, in listinstances
    return [ self[i].get_property_long('ordinal',0) for i in self ]
                                                             ^^^^
eigend: <rig1>:  TypeError: iter() returned non-iterator of type 'list'
eigend: <rig1>:  end traceback:

the important bit is

details WILL vary, as will file location.

search for this :
Traceback (most recent call last):
end traceback:

you can copy the bits, including these lines, and post in bug.
they tell me exactly where the error is.
so I dont need the whole log!

IF you have multiple, likely, look at the file, and line numbers
(eg. here its agent.py, line 145; collection.py", line 47; ollection.py", line 37)
if they are the same… I only need one

IF they don’t occur then save the log file, so you have it for later if I need it.

1 Like
3

Out of Scope

  • other platforms (Mac Intel, Windows Linus)
  • new features
  • pre-existing bugs ( * )
  • release notes
  • dev notes
  • dev environment

don’t worry, these will all open up soon, this this phase is focused to get the most obvious bugs, on ‘my’ dev platform so I can fix quickly.
( * ) please report bugs you find whilst testing, I just don’t want a ton of bugs you already knew about from EigenLabs days to litter the reporting system now… and pre-existing bugs will be a lower priority.

Status Tracking Details:

-when you submit it will be open, a few seconds later you will see your issue automatically have labels assigned to it according to your form filling.

once I pick I up, you’ll see it assigned and get a status that I track it with.
it will end up with a status:fixed label - this means Ive fixed it, so will be in next release.

WHEN there is a (beta) release, please check bugs that you raised and are marked status:fixed - and re-test.
once you are happy its fixed change label to status:verified
( its best if original report verifies, but anyone can do it - as long as they clear what the bug was)

once it’s been verified, either you or I will close it.

Testing Strategy / Reporting

  • Test on released version of EigenD, if there, use that version number.
    I will fix existing bugs, but it helps a lot to know if its new to 3.0.0 or not.
    if you don’t test it I will have to , and that slows me down a lot !
  • Simplest reproducible steps possible
    telling me it ‘crashed’ doesn’t help much
  • Log files
    try to grab the relevant bit, rather than posting the whole log.
    remember if you ware testing workbench, it may be the error is either in eigend.0.log or workbench.0.log, see tips above
  • Quote snippets from logs, using the <> in toolbar.
    some errors are ‘code’, so need this to be formatted properly.
  • See tips above
    If I see things that will help you find relevant info in logs I will included below
  • Feel free to discuss here
    Im just using the GitHub issues as a tracker, discuss how its going here with me and others.
  • This topic is a WIKI
    this is because testing of Agents is going to need some coordinating, because there so many - so mark off those that you have tested.
2 Likes
4

and, we are go, go, go :slight_smile:

1 Like
5

WoW just wowoooo it’s alive !!

Just some screens as proof :wink: (and you can have a :beer: on me!)

Screenshot 2025-11-13 at 19.48.07
Screenshot 2025-11-13 at 19.48.07624×791 50.1 KB

Installer asked for python - after that- all went smooth
Screenshot 2025-11-13 at 19.31.48

  • Asked for location of plugins scan
  • I used a PICO for this initial proof
  • I can see MIDI being generated
  • Audio is OK also
    … simply awesome !!
2 Likes
6

cool, always good to hear the first one works :slight_smile:

whilst I try to keep my ‘for music’ Mac, fairly clean,
it, inevitably, ends up with dev tools and various pre release dev builds on it.
so, I ended up cleaning it for ‘clean room testing’, but it’s easy for something artefact to get left behind… so yeah, glad it worked!

yup, we don’t ship python, rather the installers now will you that you need to do … good to see it working.

1 Like
7

Yay, it starts! :slight_smile:
Have to remember how this Alpha standard setup worked. Does anybody still have the description from the Eigenlabs website?
Found a setting that makes sounds over MIDI. (Fourths top mode-key from the right when first pressing the first mode key from the left in the second lowest row).
One odd thing: When playing keys from top to bottom and back the key pitches were somehow randomized. Sometimes the distance between two vertically adjacent keys is a semitone as expected, then a much larger interval, then sometimes when pressing the same key again it suddenly had another pitch. Sometimes also happens when pressing the same key repeatedly that it changes pitch.
Particularly after pressing the transpose keys. (So, pressing some key - constant pitch. Pressing a transpose key once. Now the pitch of that key changes several times until it settles on some constant pitch again).
Don’t have any other Eigenharp software on this particular Mac yet, will have to test with e.g. old EigenD to see whether it’s the same behavior. If yes perhaps some keys (particularly the transpose keys) are decalibrated - which would be sad). Or it is the new EigenD. Will check. Has anybody else the same observation?
Edit: The “Modular Synth” experimental setup seems to work without problems. So it is not the Alpha (phew) but “1 Split Standard Setup”. Probably one of the most complex setups in existence :slight_smile:

1 Like
8

I have all sorts of info/notes etc…
Alpha 1 Description.txt (3.6 KB)
Alpha 2 Description.txt (3.7 KB)
Alpha 3 Description.txt (3.7 KB)
(this last one is the BIG one :wink:

I’ll play with Alpha later…

1 Like
9

the quick reference guides in the installs has details for setup for all the eigenharps.

dont think has the key layout, but should be the standard one,
but you can go into workbench to verify.

I checked my custom alpha setup and layout appeared correct there.

2 Likes
10

When using the Synth sound in the 1 Split Standard Setup then the transpose keys also work as expected. There seems to be an interaction with the MIDI out, will investigate/try to minimize the setup tomorrow.

11

Ive just tried with Split 1 Alpha - I see no issue.

Tried Audio Unit/ Midi Output both behaving as expected and using the usual Eigenharp default layout, and transpose seemed ok

transpose shouldn’t be different on modular synth to midi, its all done in the scaler, so same agent…

12

talking of midi…
can someone that uses midi a lot with existing eigend, so some tests on it.
as far I can tell its working fine, but Im getting some oddities.

however, testing on older version of eigend seems the same.
I get the feeling its just the usual midi stuff, likely message saturation etc.
or how Ive set things up.

if I look on midi monitor, all seems fine… and 3.0 is same as 2.2.1 for me.

also… embedded Audio Units are fine, which is basically same code, just missing Core Midi output.

also, probably importantly , Lydia has. given me flu/cold, and I feel crap, so frankly - I think I dont have the patience at the moment to deal with midi :wink:

edit:
playing with my pico / eagan matrix module seems fine…
so think just some weird oddity with osmose, or how I had things setup

13

Have tested it again.
Experiment:

  • Connect Alpha to Mac
  • Start EigenD, “1 Split Standard Setup” auto-loads (that is what we will use)
  • Go to Workbench, go to “midi output 1”, enable “Eigenlabs 1” as output
  • open Bitwig, load Repro 5 (init preset), enable channel All->All mapping
  • click on the mode key (second row first column from below left), enable midi out (sixth row, second column from below left) on Alpha
  • play some notes

Initially I get a somehow randomized diminished-like scale where note to key assignments sometimes change over time. This looks/sounds like this

  • Then I play some fast arpeggios (essentially sliding the finger up and down the keys two-three times).
  • Now the mapping works as expected: Chromatic keys up and down (now we finally see that the configured scale was actually chromatic from the start :slight_smile: ).
    Here an example of that.
  • Sometimes it seems to work correctly now until I restart EigenD. Sometimes it works for some time and then starts to “decalibrate” again. Here an example (first it takes quite some time until it works. Then it plays chromatic for a brief time (near the end), then it is back to random mode again)

Will be on the move over the weekend (so further Alpha experiments will have to wait). But I will take the Macbook and the Pico with me.

14

Oh! All the best! The Midis can wait.

15

next time, load up midi monitor and see what it thinks the output is…
are you using mpe?

it sounds like some oddities of midi output/ scrambling.

it works fine here, Ive not seen any evidence of keygroup or scaler acting up.

have you tried loading in as a vst/audio unit, see if it works there?

the fact that it fixes itself is odd… unless, the setup is not fully loaded when you start, though event then, the agent state is loaded before it gets connected… so can’t see that.

have you tried on an older eigend?

as I said, I saw some midi oddities on one Mac/setup with my osmose, but honestly, I think thats a setup issue… as I was getting weird

unfortunately, we would need to tie this down quite a lot, with midi theres so many possibilities outside of eigend that can screw it up its why I have midi :wink:

off topic… a bit…
btw: what previous version of eigend are you using? also @keymanpal ?

I noticed, Ive got 2.2.1 everywhere, but then noticed GitHub latest was 2.1.7… so Im a bit confused, I was sure 2.2.1 was released !

16

Will do some testing on Sunday when I’m back. On this Macbook: No EigenD, only VCV+Meta Morph (it is quite new - well, newly bought used from eBay :slight_smile: The old Macbook was using the latest (Intel) binary from Github. (I also had versions that were compiled from your master branch but I think the last one was just the official GitHub release, so it must have been 2.1.7).

1 Like
17

I have 2.2.1 on:
MBP2022 (Ventura) and MBP2017 (Mojave)
(only released via forum polyexpression?

below this if I remember correctly 2.1.7 was the last supporting 32bit? so stops at High Sierra 10.13.6
(that is my beloved Imac currently with a blown out GPU - AMD Radeon HD 6970M “plagued”)

18

cool thanks for that…

indeed…

it was just a hot fix due to an OS change…guess, as it was for Mac only, I decided not to put it up on GitHub, as 2.1.7 had all platforms.

I think 2.2.0 actually was likely never released ( a red herring in that post), as it just had some minor fixes in it - but Id put it on all my machines, so assumed Id released it :slight_smile:

this is why I want to get GitHub actions working, so I can automatically release all platforms, as its such a time consuming faff, doing builds on different machines etc.

3 Likes
19

So, installed on MBP M4 with Tahoe. No prior EigenD, but lots of developer stuff. Some notes:

  • I needed to install Python which the installer told me (nice!), but perhaps a tiny improvement to the instructions could be to tell the user to cancel the installation before installing Python, then start installer again. I tried to keep EigenD installer open just to see what would happen, and it didn’t detect that I now had installed Python.
  • I tested the Pico and the experimental modular synth setup which gave me audio out without ANY configuration - a good setup as a first test for complete EigenD beginners?
  • Plugin scanning worked without a hitch
  • Workbench looks nice and works, but is “sluggish”. E.g. I click to edit a text input and there is a delay until my change is visible.
  • The +/- keys and sliders next to value inputs doesn’t work properly. If I click +, say, it hangs for a bit and then might increase the value by 5-6 steps. The slider doesn’t seem to do anything.

I’ll create a GitHub issue for the sluggish workbench UI and sliders.

Also, I’ve just started testing agents doing the following: no Eigenharp connected, blank setup. Add single agent in workbench, connect some wires if possible, edit values (easy to miss some, is it important to edit every single one? Should I also rename every input/output?). Then delete agent, quit EigenD, check log for something suspicious and search for “Traceback (most recent call last)” as well. Sounds ok?

To the rest: I started on top of the agent list and will update it as I go along. The goal is to get to “G” today, just so that we don’t do the same agents. :slight_smile:

2 Likes
20

agree :wink: that is also my go to setup, (bypassing the need of plugins or via MIDI.

Testing Agents…
maybe we could spit the load between some users? as a way to test them all.

1 Like