EYESY on RasPi4 w/ Pisound (step-by-step guide)

idek · May 16, 2021, 10:52pm

Hi jqrsound, with ethernet, I’m plug straight into the junction box built into my home. It works totally fine with the mac only not the pi. I’ve check around and everyone says it a 0.01% that it’s a pi problem, since this is my 2nd pi4 I’ve tried on. But wlan works for now, so I’ll find out later what’s the problem.

ok noted on the amidiauto.

I went through all the steps in Mads Kjeldgaard tutorial except for the part of installing the real-time kernel. I’ve tried that but after that my interface is not recognized and doesn’t light up, so I skipped that step and did step 16 & 19 of your tutorial. I didn’t manage to even start eyesy on the webbrowser on my mac. Got stuck there. I’ll try again when I’ve time and report back.

Rafv · May 17, 2021, 1:50pm

So I managed to get my MIDI working. In PD i can see MIDI IN light up when testing MIDI and AUDIO. When starting the webbrowser for EYESY, I still get ther error I mentioned before.

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: No such file or directory [default]

These lines look most important to me. But I don’t know what to do with it.

okyeron · May 17, 2021, 11:50pm

Your sound card needs to be setup as “default”

I’ve done this with my sound card as follows:

# create asound.conf if it does not exist
sudo nano /etc/asound.conf

#add
pcm.!default  {
  type hw card 0
}

ctl.!default {
  type hw card 0
}

Rafv · May 18, 2021, 3:58pm

Do I need do edit that code?
When I entered this code: sudo nano /etc/asound.conf
It gave me the exact code you wrote.

#add
pcm.!default  {
  type hw card 0
}

ctl.!default {
  type hw card 0
}

Then just press ^X to exit? That didn’t work when I tried the webeditor again.

okyeron · May 18, 2021, 4:03pm

What do you get from aplay -l?

Rafv · May 18, 2021, 6:40pm

card 1: Series [TASCAM DR Series], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

The external sound card (fieldrecorder) I’m using. Set to 16bit.

okyeron · May 18, 2021, 6:55pm

So you would want to try changing asound.conf details from
type hw card 0
to
type hw card 1
(and reboot or restart alsa)

Rafv · May 18, 2021, 7:08pm

Where do I change that? Where can I find the .conf file?
I did find asound.conf in terminal, and it told me there was no file.

okyeron · May 18, 2021, 9:25pm

Do what you did above. Then control-o to save and control-x to exit

There are many many web resources on how to create/edit files in raspberry pi. So a search on how to use the nano editor.

Rafv · May 19, 2021, 11:06am

I saw the Football Scope mode for a second. Then it crashed again and gave me this (different) error:

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'.

Rafv · May 20, 2021, 6:19am

So I found out, that wen PureData is opened on the PI, the web editor does not start (hence the error before?). But when I close PD on the RPI, my MIDI does not stay connected to PD.
Also when I open the webeditor and start Python when PD is closed, it does not crash, but the football scope seems to be flipping out, even with no sound input.
It also seems like Aconnectgui (the ALSA Sequencer) has to be opened on the RPI, for Python not to crash.

Edit: Even with the ALSA opened, I get a different Error…:

Traceback (most recent call last):
  File "main.py", line 173, in 
    sound.recv()
  File "/home/pi/Eyesy/engines/python/sound.py", line 63, in recv
    ldata = audioop.tomono(data, 2, 1, 0)
audioop.error: not a whole number of frames
eyesy-python.service: Main process exited, code=exited, status=1/FAILURE
eyesy-python.service: Failed with result 'exit-code'.

thommyc · May 31, 2021, 8:07pm

Just finished the installation - thanks for the great guide and work @jqrsound and @okyeron.

I’m now failing at the last step

I have touchOSC on both iPad & iPhone and in both cases the latency is so bad as to make it unusable. Parameter knobs appear to work (with this delay) but mode/scene selection does not. I’ve followed everything in this guide to the letter… Are there maybe some parameters on touchOSC that I’m missing (never used it before)?

I guess I’m going to buy a MIDI controller anyway but it would be nice to figure out how to get this working.

okyeron · May 31, 2021, 9:46pm

This sounds a bit strange. I’ve never noticed any lag/delay with touchOSC in my setup.

Make sure both devices are on the same wifi network? Use IP address to avoid domain resolution issues. Be sure the ports in question are not blocked on your router. Etc. etc.

jqrsound · June 1, 2021, 2:17pm

Hi thommyc, I’m glad you found the guide useful.
I also don’t have any problem with touchOSC, no delays or such.

thommyc · June 1, 2021, 9:06pm

Thanks @okyeron - I tried again and it worked when I switched out raspberrypi.local for the actual IP address. All good now - thanks for the help

rtmusic · November 21, 2021, 3:12pm

Wow - Can’t wait to try this - would be great if you could put a short description of what EYESY is and a direct link. Googling EYESY got me nothing. After crawling the comments I found it - this is really cool and may simplify an exhibit I am building. Can’t wait to try it - Thanks for the guide!

jqrsound · November 22, 2021, 4:04pm

Hi RTMusic, thanks for your feedback.
I added a link to the Critter & Guitari’s website and a short description at the beginning of the topic.
Have fun with Eyesy!

chico · December 25, 2021, 9:30pm

Hello!

I have a normal Raspberry Pi (3). I’ve been able to install, connect and initialize Eyesy browser/editor as per your github instructions. However, when I try to run a script, nothing really happens – no window or pop up with the actual video graphics.

Any idea what could be happening?

Thank you and best regards,
Francisco

okyeron · December 26, 2021, 1:41am

“Run a script” how?

With my setup you would start the web server, then open the web interface and then launch either the python or oF version from the web editor.

You should see the Eyesy logo on launching the python version.

You really want to have sound configured and inputting something as some modes only really do anything with sound going.

chico · December 26, 2021, 2:06am

Hello,

Thanks so much for replying, really appreciate it! It’s already pretty late where I live and I’ was just about to go to sleep when I saw your reply. I can give better/clearer information tomorrow (sorry) and perhaps even a photo or two. But basically I think I correctly did everything you mentioned – I can get the web server to connect and I can see and load the python and/or oF versions – some lines of code appear on screen with different colours (sorry if I’m not using appropriate nomenclature, I’m not too knowledgeable with programming/coding) but no screen or graphics actually ‘launch’, so to speak.
I tried from the browser within raspberry as well as from my desktop without any differing results (I even tried turning off adblocker in case it was preventing something from opening). I did have some audio going into the Pi (I think all was connected properly).

I’ll send images tomorrow if that’s not being too invasive of your time.

Thank you again for replying and best regards,
Francisco