#6

Hi everyone, I recently adapted the Critter&Guitari video synth Eyesy code in order to run it on my Fates as a Sidekick app.

I thought I could share this here if anyone is interested :slight_smile:

12 Likes
Fates - a DIY norns DAC board for Raspberry Pi
#7

YES! 20 chars of your the best :smiley:

1 Like
#8

Iccy how do you clone this repo into ‘~/sidekick/patches’ ? i don’t know how.

edit again thanks to @eigen

cd /home/we/sidekick/patches
git clone https://github.com/Lcchy/Eyesy_for_fates
cd Eyesy_for_fates
./deploy.sh

3 Likes
#9

VERY interested, thank you so much!!!

#10

anyone got this working yet , me and @eigen (mostly eigen) have been trying to get this up and running.

#11

Yup, except:

git clone https://github.com/Lcchy/Eyesy_for_fates Eyesy
cd Eyesy

instead of

git clone https://github.com/Lcchy/Eyesy_for_fates
cd Eyesy_for_fates
3 Likes
#12

Wow amazing I can’t wait to try this!!! I’ll report back soon :slight_smile:

#13

Cool that it runs ! :slight_smile:

I just tidied the installation instructions up, thanks @eigen

#14

Should be cd /home/we/sidekick/patches, as in “there’s no place like”

1 Like
#15

cheers i should edit it , Eigen also brought that up thank you!

1 Like
#16

Hi there- I was unable to get this to run. I re-did my Fates image from scratch, went through the normal Fates & Sidekick install instructions, and then installed per the Eyesy for Fates repo. My Fates is up-to-date with Norns 201029, and Sidekick has been checked for updates as well.

I’ve confirmed my HDMI out is functioning; when the Pi boots, I get a square of color gradation, and if I launch Norns with the HDMI cable attached, it uses my monitor for the Norns screen (very tiny and mangled, it’s cute and hilarious :slight_smile:) I’m on a Pi 4.

Sidekick logs show this when trying to launch Eyesy:

Sidekick logs 
Nov 09 20:09:18 norns sidekick[109]: Sidekick launch
Nov 09 20:09:18 norns sidekick[109]: launch : Eyesy
Nov 09 20:09:18 norns sidekick[109]: exec : cd "./patches/Eyesy"; ./run.sh &
Nov 09 20:09:18 norns sidekick[109]: exec : "./post-patch.sh"
Nov 09 20:09:18 norns sidekick[109]: starting Eyesy
Nov 09 20:09:18 norns sidekick[109]: opened alsa client 129 in:1 out:1
Nov 09 20:09:18 norns sidekick[109]: using framebuffer /dev/fb1
Nov 09 20:09:19 norns sidekick[109]: setting up abl_link~
Nov 09 20:09:19 norns sidekick[109]: Created new Link instance with tempo 134.000000.
Nov 09 20:09:19 norns sidekick[109]: udpsend: connecting to port 4000
Nov 09 20:09:19 norns sidekick[109]: Connection failed (Invalid argument)
Nov 09 20:09:20 norns sidekick[109]: error: udpsend send: Connection refused (111)
Nov 09 20:09:20 norns sidekick[109]: verbose(4): ... you might be able to track this down from the Find menu.
Nov 09 20:09:20 norns sidekick[109]: udpsend: connecting to port 4000
Nov 09 20:09:21 norns sidekick[109]: error: udpsend send: Connection refused (111)
Nov 09 20:09:21 norns sidekick[109]: udpsend: connecting to port 4000
Nov 09 20:09:22 norns sidekick[109]: error: udpsend send: Connection refused (111)
Nov 09 20:09:22 norns sidekick[109]: udpsend: connecting to port 4000

Sidekick continues trying to connect to the port about once a second thereafter.

Happy to take this conversation private or to a Github issue if appropriate! Thanks for any response.

#17

So I think something is missing - psutil

Nov 10 01:34:15 fates systemd[1]: Started Python Pygame Video Engine.
Nov 10 01:34:15 fates nohup[800]: pygame 1.9.4.post1
Nov 10 01:34:15 fates nohup[800]: Hello from the pygame community. https://www.pygame.org/contribute.html
Nov 10 01:34:15 fates nohup[800]: Traceback (most recent call last):
Nov 10 01:34:15 fates nohup[800]:   File "main.py", line 6, in <module>
Nov 10 01:34:15 fates nohup[800]:     import psutil
Nov 10 01:34:15 fates nohup[800]: ImportError: No module named psutil
Nov 10 01:34:15 fates systemd[1]: eyesy-python.service: Main process exited, code=exited, status=1/FAILURE

But… I tried to manually install psutil and it did not change anything.

But then… I sudo installed psutil and it worked. Had to install pip first tho…

so it seems this is needed (FYI @lcchy):

sudo apt install python-pip
sudo pip install psutil
3 Likes
#18

Thanks a lot @okyeron, I must have installed at some point and did not remember :upside_down_face:
I added it to the installation instructions.

@xenus_dad sorry for the hassle! It probably is because of what okyeron just mentioned.
The connection error messages you are getting are from the pd patch that is trying to connect to the engine that is not responding.

FYI The python video engine runs as a systemd service, that means that if you want to see what errors it might be outputting, you can use the command journalctl -e while logged in via a second ssh session or, after having stopped the Sidekick app.

Edit: I just changed some small things in the way the knobs and the midi controls behave (made it relative). If you want to update your version you can do:
cd ~/sidekick/patches/Eyesy; git pull

1 Like
#19

@lcchy Fresh install rp3, blank screen on eyesy

#20

Check the install path

Should be ~/sidekick/patches/Eyesy and not Eyesy_for_fates

#21

Yes it is correct. How to open sidekick logs ?

#22

tried that git pull but still no midi control with the fates buttons/knobs on rpi 4 fates shield

#23

systemctl status eyesy-python.service
to see if the eyesy service is running

journalctl | grep sidekick for

@lcchy perhaps you could start a new Eyesy thread and we could take troubleshooting over there?

5 Likes
#24

Ok yes I think it is better to move to another thread indeed!

I just created it here : Critter&Guitari video synth Eyesy for Fates

It would be nice if an admin could move the posts, sorry for the mess

ps: @Zifor if you could run journalctl | grep sidekick like okyeron said and post it on the new thread, maybe I can find whats going on
edit: @LT6J also :wink:

1 Like
#25

FYI - some posts got merged into this thread from the fates thread, so they are slightly out of order above.

2 Likes