Eigenharp Pico need help!

Hello there,

I just recently acquired a Pico and I’m trying to get it running with the EigenD software, on a Windows 7 PC.

I’ve downloaded the driver and run time application, then I installed the most recent version of EigenD (2.1.0)

When I try to run the program I’m getting two different errors. One says ‘the program can’t start because pic.dll is missing from your computer. Try reinstalling the program to fix this problem,’ which I have done to no avail.

The second says the same but with MSVCR110.dll in its place.

Can anybody help me get it working please? Thanks In advance,

Leigh

1 Like

Hi there! I would recommend to install the latest community edition with many fixes and extensions from @thetechnobear : How to install and run EigenD in 2023+ [wiki]

I guess nobody else(?) has tested EigenD on Win7 in the last years. But I am at least not aware that it doesn’t work, so it’s worth a try.

Also ensure that the driver was successfully loaded in the device manager. This can be a matter of installing/uninstalling and finding the right USB port initially on Windows. Fortunately, as soon as it works it usually keeps working.

If you have access to a Mac (a cheap used one should be sufficient) it might also be worth to look into Meta Morph (which is Mac-only atm.), This is a collection of Eigenharp modules for the virtual modular environment VCV. It offers access to the entire VCV plugin ecosystem while still maintaining (close to) audio-rate modulations that EigenD was made for.

1 Like

Sounds like you need to install the Visual C++ Redistributable. (It’s quite a common thing; often gone through this. If you Google the .dll you’ll find notes about it; simple to fix.)

edit

Welcome to the forum Leigh, just realised that was my Pico you bought. :grin:

The Redistributable will certainly sort MSVCR out…not sure about the other one, but we can tackle that if it persists.

2 Likes

Oh, hey there! Small world. Thanks very much for the Pico :pray:

Just to be clear, I should Google the specific .dll file I’m missing?

Thanks,

Leigh

1 Like

Thanks for your response!

I thought I was installing the latest version but I will double check

Is there any way to tell if the driver installed properly?

1 Like

…just asked ChatGPT which version of the Visual C++ Redistributable would work with Windows 7 and contain MSVCR110.dll, and it suggested 2012.

vcredist_x86.exe for 32bit Windows, or vcredist_x64.exe for 64bit.

I’m not sure which you’d need for the 64bit OS…does it depend on whether the application is 32bit or 64bit? But you could try both. Won’t do any harm. Just checked my PC and it has about a dozen mixed versions.

On my machine, pic.dll is in:

C:\Program Files (x86)\Eigenlabs\release-2.1.0-experimental\bin

The installed version is EigenD-2.1.0-experimental. This is the machine I used for the demo with your Pico.

It’s available as a download here:

…also see the other recommended downloads from this page; the runtime and the drivers. (I have driver version 1.0.10.)

Given that the main program files are in:

“C:\Program Files (x86)”

I’m evidently using the 32bit versions of everything, though the PC is Windows 10 64bit.

I used this patch…

image

Other steps were:

  • Install loopMidi

https://www.tobias-erichsen.de/software/loopmidi.html

  • Edit the patch in the Workbench section of the EigenD software to redirect MIDI output to the input of a virtual MIDI port

  • Run a virtual synth in a DAW and point the output of the virtual MIDI port at it

There might have been more to it, and you’ll need to figure out the device’s own button menu too, but that’s as much as I remember. (I did say it was complicated.) :grin:

2 Likes

I installed the file you suggested and I’m still getting the same message

I actually noticed something strange, the files in ‘bin’ seen to be showing up as properties of other applications I have (please see attached picture )

Is this normal? I’ve found, for instance, pic dl, but it’s showing up as being a file from another program

Going to try a reinstall now

1 Like

that doesn’t matter the whole file extension mapping on windows is primitive, and doesn’t mean anything.

there is no EigenD 64bit build for windows, so this is to be expected.

im confused, how do you get the two different errors? what are you trying to run?

missing pic.dll would be odd, as its clearly present.

the msvcr100.dll is indeed the vc++ runtime, which could install if missing. Im slightly surprised, as I dont remember having to install this when Ive previously installed eigend on windows, it was already present.

are you running this from the Start menu?
as some of the excutables are not designed to be run directly from explorer… many are ‘advanced’ tools that users would not use.

(unfortunately, I dont have it installed on my Windows laptop at the moment, so can’t give more specific advice…)

1 Like

I get the pic dll message when trying to run EigenD from my desktop screen and the other when trying to run it from the start menu.

I installed the 64bit version of this, I will go back and install the 32bit one

1 Like

Eureka, I have it working now on my newer, Win 10 PC!

now to delve deep into EigenD…

5 Likes

Good to hear that it works on the Windows 10 PC! In case you still want to check the status of the driver at some point: Open the device manager and check whether there is an exclamation mark next to the (I think it is called) “Eigenharp Pico” entry. Or whether there is any such entry at all (or e.g. only something along the lines of “unknown usb-device”).
In the case of an exclamation mark it usually helped for me to uninstall and reinstall the driver, potentially plugging the Pico into another USB port, reinstalling again - until it suddently worked.
As far as I remember the driver hasn’t changed in ages, so I think I (and the other Windows users) also got it to work on Win7 back then.

1 Like

I didn’t get the Pico to light up or anything, should it automatically turn on at some point? I will check the driver is working tomorrow and hopefully, I can begin learning EigenD…

Thanks again

1 Like

You’ll need to run eigend and load a preset to get lights. There are no lights until then.

If you have issues look at device manger to see if the pico ia found. ( again after loading preset)

1 Like

@Medley most presets have light indications ( as mention by thethechinobear - run eigend +preset)

here is a preset that has all LED light up red

1 Like

For some reason, I can’t drag and drop this file into User Presets, the cursor becomes a circle with a cross through it, unless I’m missing something?

1 Like

Im pretty sure eigend does not support drag n’ drop…

anyway don’t bother with this, as I said, if you load the standard factory preset, then press some buttons leds will light up.
if they don’t then the driver is likely not working.

1 Like

Yesterday, I managed to get two green lights whilst playing around but I can’t seem to replicate that at all now or get any LEDs to light up. Control Panel says ‘the device is working properly’ is there something else I can try?

I’ve attached a screenshot, in case that helps

1 Like

unfortunately, none of this is enough info for me to go on :frowning:

can you show me the properties of that device - Id like to see the vendor/product id.

once the firmware is loaded it should be:
vendor : 0x2139
product : 0x0101

if its not loading properly it’ll be
vendor : 0x2139
product : 0x0001

next, we need some log files from EigenD.

so fire up eigend with pico connected (check usb status as above) to ensure pico is intialised then

EigenD->Tools->Open Library

you should find a log files directory (and remember name off top of my head)
inside you’ll find something like eigend.0.log

copy this to desktop , then upload to drop box (or other reputable) location.
and I can take a look


cables/usb hubs etc

there other thing to try, is different usb cables.
the pico is very sensitive to the correct cable.
I’ve got a number of cables that do not work with the pico, but are absolutely fine with other devices.
so try both long and short cables, even cables that are not suitable for use, just to test.
similarly test directly connected to the PC , and then without a powered usb hub, only usb 2, not usb 3.

and whilst, “I got it to work once’” usually, would prove its working, sometimes with the pico what happens is it’ll initialise ok, but then later fail… ie. ‘bad cable’ can just be unreliable that an complete fail.

basically, the pico ‘pushes’ some of the specs for the (early) usb specs and this can cause issues for some hardware/cables - this is problematic on PC (rather than Macs) as there is so much diversity in setups. so you need to try a few combos.

2 Likes

Apologies, but I am struggling to find what you requested within the file properties, could you please direct me using the two attached photos?

I noticed that somewhere within the properties, it says that my driver is for the Eigenharp Alpha, could this be an issue?

I believe I have located the log file but I’m not entirely sure, please have a look and advise if you would be so kind.

I will keep all of that cable information in mind. Im curently using a new cable, I will try some others asap
Big thanks

Log

https://www.dropbox.com/scl/fi/73r2mmxouie0gkeacneka/eigend.0.log?rlkey=a3724aei0he1ggygbjqvxfjpa&st=po66a9l9&dl=0

1 Like

1 Like