Id need to see more of the log file… in particular where the pico manager loads the ihx file.
the most common issue (but covered in the install instructions) are not finding the modules OR udev not being done, so your user cannot access the usb device.
apart from that :
look at dmesg for errors from pico
use lsusb to see if you can see usb device
try with and without a powered usb hub ( * )
( * ) Ive mentioned this before, the usb support on the rPI is pretty flakey - I’ve seen various kernel versions which break the usb support, then later ones fix it, then break it again.
I think its generally getting better, but really I cant keep track of when its working and not
I know I tried the pico on the rPI4, but honestly I can’t remember if and how I got it to work!
I did run the udev command after moving and renaming the rules file.
This got my pico to work on an Organelle M with Orac. I did rename the scanner script so it would not run. That would not break the pico manager, would it? It’s just for VSTs and AUs right?
I’m gonna try plugging my tau in and see what happens.
I’ll figure out dmesg, lsusb and try a good powered hub. Thanks for the leads.
Speaking of power, and speed I read in a thread getting a pico to work on a linux box involved plugging into the usb 3.0 port… will try that too just in case.
Thanks for your patience with me trying to beat my “Dead Horse PIco”.
From being an old biologist & oboist
I feel that anything worth doing is hard; Plus I’ve learned sooo much linux!
I’ve tried your suggestions Mark with little more info.
pico manager seems to still fail to load pico.itx
My powered hub (2.5 amps) does not make a difference.
I am not sure where the log between the pico manager ans pico.itx is on an Rpi4.
There is no log under var/logs for eigenD or in 2.1.7 community folder.
I did get this from the console when I loaded a blank file in EigenD & tried to add the pico manager…
seems like something is wrong with the libpico_decoder_arm7_1_0_0.so file bolded below. Not sure this helps.
workspace: stateChanged
eigend: main:interpreter1 slow going active 6760
eigend: main:eigend1 slow going active 287
eigend: main:interpreter1 fast going active
eigend: main:eigend1 fast going active
eigend-garbage: starting gc pass 0
eigend-garbage: finished gc pass 0
eigend-garbage: starting gc pass 0
eigend-garbage: gc collected 11
eigend-garbage: finished gc pass 0
eigend-garbage: starting gc pass 0
eigend-garbage: finished gc pass 0
eigend: main:eigend1 fast going passive
eigend: main:interpreter1 fast going passive
eigend-backend: assigned cordinal 1 to pico_manager
eigend-backend: loading a(’<pico_manager1>’,pico_manager,‘2.1.7-community’,‘1.0.1’,1) into enclosure None
eigend-backend: relation: create(cnc("<pico_manager1>"),role(by,[cnc(~a)]))
eigend-backend: ignored:
eigend-backend: Traceback (most recent call last):
eigend-backend: File “pi/utils.py”, line 84, in __do_nothrow
eigend-backend: File “pisession/workspace.py”, line 207, in load
eigend-backend: File “pisession/registry.py”, line 60, in import_module
eigend-backend: File “plg_pkbd/pico_manager_plg.py”, line 25, in
eigend-backend: File “lib_pico/init.py”, line 21, in
eigend-backend: ImportError: /usr/local/pi/release-2.1.7-community/modules/…/bin/…/bin/libpico_decoder_arm7_1_0_0.so: invalid ELF header
eigend-garbage: starting gc pass 0
eigend-garbage: gc collected 11
eigend-garbage: finished gc pass 0
Id guess this is something to do with the rPI4 build eg. expecting a 64 bit build
whats confusing me slightly, is it appears to be loading all the other shared libraries correctly and they were all built together.
(or are there lots of other errors if you load other eigend modules?)
as you say the tau woud not required this…so perhaps this indicates the so are not loading at all - and would require a 64 bit arm build
