this is a follow up to our experiments at 3e…
here is what @keymanpal and I thought we had discovered after testing EigenD on both his MacBook and Duncan’s.
if has pico has just been plugged in (so fresh power cycle), then EigenD will not fully connect to it.
(so that if we look in workbench, we will NOT see pico keyboard)
if we then restart EigenD, then the pico will then be seen.
also we noted, that EigenD will not reconnect if you unplug the pico, and plug it in again.
the working assumption for the issue…
when the pico is first connected, we download the firmware to it (pico.ihx), it then reboots, and reappears as a new usb device.
we can see the firmware update/reboot has been done when you first start EigenD.
however, it does not reconnect as it should (after its ‘reboot’)
we don’t know why… perhaps its not retrying, or perhaps there is a timing issue and it ‘gives up’.
but it appeared to be consistent, and also the not reconnecting, also was consistent.
also, EigenLite (thru ECMapper works correctly, so we know it not a hardware issue )
now the problem…
I’ve just tried the same thing with EigenD on my Mac (mini m1) and my pico, and none of this happens… it connects first time with EigenD, and I can unplug it and plug it back in , and it happily reconnects everytime.
arghhhh… I can’t fix whats not broken
I tried two different Mac mini m1s using different power hubs, and also straight into the mini (no hub), and it works every time as you’d expect.
ok, so we are a bit back to square one…
I wonder if others could test, and see if they can get some more info
there are two tests to try… though they are kind of the same.
first setup…
lets be consistent …
you can try with or without a powered hub… do not use a non-powered hub, or any adapters.
make sure ECMapper is NOT running, and has not run previously.
start with Pico unconnected
start EigenD and set it to have ‘blank’ preset as default start up ,
(exit EigenD once you have done this)
ok now the test… (which you can repeat)
TEST 1 - using simple setup
plug in pico
start EigenD (so we have blank)
load experimental/pico/midi basic
what should happen:
some LEDS come on
what happened for some at 3e:
leds would not come on
here it would be useful to grab eigend.0.log !!
if it failed, exit EigenD , but leave pico connected
start EigenD (so we have blank)
load experimental/pico/midi basic
we would now expect it to work, for everyone
so, leds come on.
now unplug pico, and plug it back in
what should happen:
some LEDS come on
what happened for some at 3e:
leds would not come on
TEST 2 - use workbench
very similar test, but will produce a smaller log file
disconnect pico,
start EigenD (blank preset)
start Workbench
create pico manager in workbench
(no pico keyboard yet, since we haven’t plugged in pico !)
connect pico
what should happen
pico keyboard will appear … (no LEDs is ok!)
if this does not happen, then grab the eigend.0.log
as I say, this test is pretty much the same as test 1, but eigend.0.log will be a bit smaller as we are not creating lots of other modules.
please do NOT send me logs when loading other setup, just the above tests. there is too much noise to make them of any use.
I should say in advance, when I checked at 3e, logs just appeared to say something like it couldn’t find the interface… which doesnt give me anything to go on, what I really want to see is if there are any other differences around the same time between non-working logs and mine… this is why its important we follow a very precise procedure.
I do have a MacBook that I can also test with, however, I dont really want to do that until we have eliminated any possible setup/install differences…
simply because its the only Mac I have that does not have EigenD installed on it, so once thats done… I’ll have no ‘fresh machines’ to attempt installs on.