Hey, I get the exact same problem as you. mec and orac services are running and touchosc2midi as well…
The installation went well without any error and the orac-control-web is also running fine.
Tried with firefox and chrome : same result, the logo and “Looking for OSC Service…”
I still didn’t find time to try to make it work on my own. It seems to be a problem between sockets libraries compatibility
Will see how it goes. Definately a nice feature to have
Ok, so I tried reinstalling a fresh version of the Patchbox OS on my raspberry pi4 with a Pisound hat and I get the same error again… I unfortunately don’t understand enough Python and webserver to dig any further. Hope you find something @DrKoma or @murmeklis !
Blockquote
Jan 31 20:54:08 patchbox python3[4167]: The client is using an unsupported version of the Socket.IO or Engine.IO protocols (further occurrences of
Add “menu timeout” value to set the desired milliseconds. You must add a comma after the “6100” line so the json file is valid after new value is added. Here’s a full example of how it should look like:
orac-control-web.service - Orac Control Service
Loaded: loaded (/lib/systemd/system/orac-control-web.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Tue 2021-11-09 19:40:55 PST; 10s ago
Process: 1780 ExecStart=/usr/bin/python3 ./main.py (code=exited, status=1/FAILURE)
Main PID: 1780 (code=exited, status=1/FAILURE)
Nov 09 19:40:55 patchbox systemd[1]: orac-control-web.service: Service RestartSec=100ms expired, scheduling restart.
Nov 09 19:40:55 patchbox systemd[1]: orac-control-web.service: Scheduled restart job, restart counter is at 8.
Nov 09 19:40:55 patchbox systemd[1]: Stopped Orac Control Service.
Nov 09 19:40:55 patchbox systemd[1]: Dependency failed for Orac Control Service.
Nov 09 19:40:55 patchbox systemd[1]: orac-control-web.service: Job orac-control-web.service/start failed with result ‘dependency’.
~
Not sure which dependency is missing?
mec.service - Run MEC at boot
Loaded: loaded (/etc/systemd/system/mec.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-11-09 19:56:12 PST; 15h ago
Main PID: 895 (code=exited, status=255/EXCEPTION)
Nov 09 19:56:12 patchbox systemd[1]: mec.service: Service RestartSec=100ms expired, scheduling restart.
Nov 09 19:56:12 patchbox systemd[1]: mec.service: Scheduled restart job, restart counter is at 5.
Nov 09 19:56:12 patchbox systemd[1]: Stopped Run MEC at boot.
Nov 09 19:56:12 patchbox systemd[1]: mec.service: Start request repeated too quickly.
Nov 09 19:56:12 patchbox systemd[1]: mec.service: Failed with result ‘exit-code’.
Nov 09 19:56:12 patchbox systemd[1]: Failed to start Run MEC at boot.
Nov 09 19:56:12 patchbox systemd[1]: mec.service: Start request repeated too quickly.
Nov 09 19:56:12 patchbox systemd[1]: mec.service: Failed with result ‘exit-code’.
Nov 09 19:56:12 patchbox systemd[1]: Failed to start Run MEC at boot.
~
~
patch@patchbox:~ $ systemctl start mec
patch@patchbox:~ $ systemctl status mec
* mec.service - Run MEC at boot
Loaded: loaded (/etc/systemd/system/mec.service; disabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-10 13:16:49 PST; 6s ago
Main PID: 6329 (mec-app)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/mec.service
`-6329 /usr/local/MEC/mec-app osckontrol.json
Nov 10 13:16:49 patchbox mec-app[6329]: [RtMidiIn Client:TouchOSC Bridge 132:0]
Nov 10 13:16:49 patchbox mec-app[6329]: [pisound-ctl:pisound-ctl 134:0]
Nov 10 13:16:49 patchbox mec-app[6329]: MecMidiProcessor not open, so invalid forPure Data:0
Nov 10 13:16:49 patchbox mec-app[6329]: MecApi_Impl::init
Nov 10 13:16:49 patchbox mec-app[6329]: oscdisplay initialise
Nov 10 13:16:49 patchbox mec-app[6329]: listening for clients on 6100
Nov 10 13:16:49 patchbox mec-app[6329]: KontrolDevice initialise
Nov 10 13:16:49 patchbox mec-app[6329]: KontrolDevice::init
Nov 10 13:16:49 patchbox mec-app[6329]: kontrol device : listening on 6000
Nov 10 13:16:49 patchbox mec-app[6329]: KontrolDevice::init - complete
patch@patchbox:~ $
But restarting Orac from the module control of patchbox always wants to start mec after Orac; or not start it in which case mec is stopped. Either way, back to square 1.
Patchbox OS installed on PI4 2GO.
I’m struggling to run ORAC through the web client ( Ip :8080)
i’vce tried with the hotspot and intro the PI. Same thing.
Pyhton3 updated.
Status of ORAC and MEC seems ok (below). So, i’m stuck.
Any idead ?
patch@patchbox:~ $ sudo systemctl start orac-control-web.service
Failed to start orac-control-web.service: Unit orac-control-web.service not found.
patch@patchbox:~ $ sudo systemctl stop orac-control-web.service
Failed to stop orac-control-web.service: Unit orac-control-web.service not loaded.
patch@patchbox:~ $
patch@patchbox:~ $ sudo apt-get install python3-pip
Reading package lists… Done
Building dependency tree
Reading state information… Done
python3-pip is already the newest version (18.1-5+rpt1).
0 upgraded, 0 newly installed, 0 to remove and 220 not upgraded.
patch@patchbox:~ $
patch@patchbox:~ $ sudo systemctl status orac
● orac.service - Run Orac at boot
Loaded: loaded (/etc/systemd/system/orac.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2021-12-31 15:44:02 GMT; 24min ago
Main PID: 601 (pd)
Tasks: 14 (limit: 3861)
CGroup: /system.slice/orac.service
├─601 /usr/bin/pd -rt -alsamidi -nogui -audiobuf 4 mother.pd main.pd
├─624 sh -c /usr/lib/puredata/bin/pd-watchdog
└─625 /usr/lib/puredata/bin/pd-watchdog
Dec 31 15:44:03 patchbox pd[601]: mainDir : .
Dec 31 15:44:03 patchbox pd[601]: dataDir : /home/patch/data/orac
Dec 31 15:44:03 patchbox pd[601]: mediaDir : /home/patch/media
Dec 31 15:44:03 patchbox pd[601]: moduleDir : modules
Dec 31 15:44:03 patchbox pd[601]: userModuleDir : /home/patch/media/orac/usermodules
Dec 31 15:44:03 patchbox pd[601]: currentPreset : demo1
Dec 31 15:44:03 patchbox pd[601]: Preset : Init
Dec 31 15:44:03 patchbox pd[601]: Preset : demo1
Dec 31 15:44:03 patchbox pd[601]: Preset : demo2
Dec 31 15:59:17 patchbox pd[601]: preset loaded : demo1
patch@patchbox:~ $ sudo systemctl status mec
● mec.service - Run MEC at boot
Loaded: loaded (/etc/systemd/system/mec.service; enabled; vendor preset: enab
Active: active (running) since Fri 2021-12-31 15:59:07 GMT; 9min ago
Main PID: 2801 (mec-app)
Tasks: 6 (limit: 3861)
CGroup: /system.slice/mec.service
└─2801 /usr/local/MEC/mec-app osckontrol.json
Dec 31 15:59:07 patchbox mec-app[2801]: Midi output opened :Pure Data:0
Dec 31 15:59:07 patchbox mec-app[2801]: MecMidiProcessor enabling for midi to Pu
Dec 31 15:59:07 patchbox mec-app[2801]: MecApi_Impl::init
Dec 31 15:59:07 patchbox mec-app[2801]: oscdisplay initialise
Dec 31 15:59:07 patchbox mec-app[2801]: listening for clients on 6100
Dec 31 15:59:07 patchbox mec-app[2801]: KontrolDevice initialise
Dec 31 15:59:07 patchbox mec-app[2801]: KontrolDevice::init
Dec 31 15:59:07 patchbox mec-app[2801]: kontrol device : listening on 6000
Dec 31 15:59:07 patchbox mec-app[2801]: KontrolDevice::init - complete
Dec 31 15:59:15 patchbox mec-app[2801]: KontrolDevice::new client 127.0.0.1 : 60
lines 1-18/18 (END)
EDIT:
Done
curl https://raw.githubusercontent.com/dsedleckas/orac-control-web/master/install-orac-control-web.sh | sh
And now, it’s stuck…on a “looking for OSC service”.
EDIT
I’ve got now something: an 'ask mark" menu. But nothing more