May 2022 update - I have installed the Patchbox Bullseye image but have not had success with Eyesy yet. I tried the git checkout patchbox command before running deploy.sh, which helped with ‘no pi user’ errors on a patchbox image. However, the install fails with the same “python… is not available” errors as in reply 65… can anyone help? *My working Eyesy with Buster has Python 2.7.16… I’d love to get Eyesy running on a Bullseye Pisound:
I had gone through these steps here and I’m having some issues that hopefully someone else has had and resolved or can duplicate.
Hardware: Raspi4 8gb with pisound add on
OS: Raspian Buster (per other comments as Bullseye gave issues)
A) when I follow the pisound installation it is looking for installation candidates blokas-telemetry and does not install
B) I managed to get everything else installed and EyeSY web service running, however LUA visuals do not load
When I select the visuals from the web site, all python visuals are the same blueish/greyish lines with dots (that DO react to audio so that works) but no other visuals load
When I select LUA visuals it will crash and return to the Raspi Desktop with login prompts
I’ve been working on this for a few hours so I’m beat. Thanks for your insights!
I know it was already a year ago. I don’t know whether you fix this problem, but I meet this same issue that the eyesy-python service cannot start correctly because of this:
Traceback (most recent call last):
File "main.py", line 36, in
sound.init(etc, AOUT_JACK)
File "/home/pi/Eyesy/engines/python/sound.py", line 41, in init
inp = alsaaudio.PCM(alsaaudio.PCM_CAPTURE,alsaaudio.PCM_NONBLOCK)
alsaaudio.ALSAAudioError: Device or resource busy [default]
eyesy-python.service: Main process exited, code=exited, status=1/FAILURE
eyesy-python.service: Failed with result 'exit-code'.
One dirty solution is to run all other services first and then manually run:
cd /home/patch/Eyesy/engines/python
python main.py
Also, I think the problem is related to the root user or something. Because if I run:
cd /home/patch/Eyesy/engines/python
sudo python main.py
I get the exact same error:
alsaaudio.ALSAAudioError: Device or resource busy [default]
If you are having trouble finding the specific Raspi Distro, the fantastic Andrei Jay Waaave_Pool image works flawless with Eyesy installed. https://andreijaycreativecoding.com/
Hi, first message here, as @jqrsound advised
It’s my second attempt to run eyesy on raspberry.
It kinda worked the first time but i was missing a spare soundcard.
I recently bought a pisound and thought i’d give it an other go.
On today’s attempt : lauching run.sh (or pushing the “button”') or starting the python video engine via webeditor gives me a black screen and nothing else. (at best with oflua engine, i have eyesy logo, but it stops there). Python issue?
I’m a linux beginner, can anyone help?
Thank you!
What output do you get in the terminal after running run.sh?
Hi @Giedrius, Thanks for taking a minute.
I can’t tell you the output of the terminal since i formated it all and started it all from scratch.
I skipped the raspi update and it kinda worked. I guess i kept all my downloads from 2021, and they seem to get along.
Tho, if i lauch eyesy via ssh from my computer eyesy’s web service, it’s fine.
If i launch it via raspberry eyesy’s folder : start.sh : It can’t see my usb controller (?)
If i launch via “the button” nothing happens. (i did the pisound button config)
The quest continues.
1 Like
Hello @okyeron
Thanks for the guide. Worked like a charm. I am in the midst of building an arduino based stomp box/controller for my diy eyesy and I had a couple questions.
I was wondering if you can elaborate on what midi values are being sent for the CC26 and beyond. For example CC29 is mode select. Would and increment up be 65 and decrement down 0? That is what I presumed but eyesy is not understanding that consistently.
Also autoclear toggle. I presumed that would be a latching function. you hit it once and its CC28:127 hit it again and its CC28:0 and that toggles it off. But that is not the case.
You shooting 127s at it or 0s? I think its 127 but I cannot get the arduino library to play right to test one way or the other.
Heya… unfortunately I barely remember what I did with all this way back when.
But looking at the docs, CCs above 25 are not used?
Scene select (and Mode select if theres no saved scenes) is via Program Change.
Auto clear is Note Number 127, not a CC
https://www.critterandguitari.com/manual?m=EYESY_Manual#3-eyesys-midi-configuration
I got everything working except incrementing up in mode or scene. I can go down without issue. I think I am pushing up against the arduino library I am using. Going to keep monkeying around with it but thanks for the guidance. Love the stuff you develop. Keep it up.
Hi everyone,
I seem not to be the only one : who knows the reason why ofLua crashes ?
Can you provide a link or idea of where to find the image? I browsed the site below but don’t see any Pi images yet. Thanks!
If you are having trouble finding the specific Raspi Distro, the fantastic Andrei Jay Waaave_Pool image works flawless with Eyesy installed. https://andreijaycreativecoding.com/
VSERPI hardware and images - andrei_jay_creative_coding (andreijaycreativecoding.com)
scroll down, try the wave pool image
I know this is an old thread, but I just got a Pisound and wanted to give this a shot. I managed to install everything on a Pi 3 board using the Buster lite image here (Index of /raspios_lite_armhf/images/raspios_lite_armhf-2021-05-28), and I got no errors during the installation.
I’m able to boot the Pisound, and hold the button for 1 second to start Eyesy. Then when I head over to the web editor and hit “start python”, I get the Eyesy logo, it runs through a list of modes that it’s loading, and then…just a blank screen. I’m connected via HDMI to a monitor, and I’ve tried multiple resolutions. I was expecting some visuals, but there’s nothing.
I also installed TouchOSC on my laptop, set the host on the OSC connection to my Pi’s IP address, 4000 as the send port and 4001 as the receive port, but running that and tweaking the controls does nothing.
Any help would be much appreciated. I feel like I’ve hit a brick wall. Thanks!
1 Like
I followed the OP directions with a Pisound and Rpi4. It took me a few tries but I got everything working as intended, I am guessing human error or my not noticing errors on install was my initial problem.
I have never attempted to connect to it via webpage, only with IPAD/OSC and provided template. I was able to follow seperate guide made by the original poster and get THE BUTTON to open other apps, wavepooole, spectral mesh, orac/modep.
maybe back up that image that is almost there and try , try again.
2 Likes
Thanks for the moral support and advice @Don_Fonzy. I figured something was up since I was trying on an RPi3, and the timing worked out where I had an RPi4 that I wasn’t using, so I went ahead and tried it on the 4, and everything seemed work. (Although, this was weeks ago and now that I’m thinking of it, I recall my synth input would affect the visuals, but I couldn’t get any sound to output, so I’ll need to find some time to figure that out.)
Haven’t had much time to play around with it, but I hooked up a Korg NanoKontrol2, and it worked to change things up, but I have to get my head wrapped around what each midi signal is supposed to do and assign my buttons and sliders and knobs accordingly (think I assigned some things to buttons that should be sliders and vice-versa).
Anyway, super cool to be able to have my weird synth sounds translate automatically into weird visuals, so I’m very appreciative of the OP and all the rest of this thread. Gonna have to look into that thing you mention, @Don_Fonzy about using the button to open other apps, too. That seems way cool.
1 Like