Hi all,
Has anyone tried the below and successfully gotten it to load in MODEP?
It has some nice IR’s in it, but it just crashes mod-ui every time I try to add it.
Any help would be appreciated.
Nov 25 11:49:32 patchbox authbind[836]: INFO:tornado4.access:200 GET /effect/get_non_cached?uri=http%3A%2F%2Fmoddevices.com%2Fplugins%2Fmod-devel%2Fcabsim&_=1606304964463 (192.168.0.101) 5.80ms
Nov 25 11:49:33 patchbox authbind[836]: DEBUG:root:[host] popped from queue: add http://moddevices.com/plugins/mod-devel/cabsim 0
Nov 25 11:49:33 patchbox authbind[836]: DEBUG:root:[host] sending -> add http://moddevices.com/plugins/mod-devel/cabsim 0
Nov 25 11:49:34 patchbox authbind[836]: INFO:tornado4.access:200 GET /?v=1606304963 (192.168.0.101) 70.88ms
Nov 25 11:49:35 patchbox authbind[836]: INFO:tornado4.access:101 GET /websocket (192.168.0.101) 3.28ms
Nov 25 11:49:35 patchbox authbind[836]: WARNING:tornado4.general:Connect error on fd 25: ECONNREFUSED
Nov 25 11:49:35 patchbox authbind[836]: WARNING:tornado4.general:Connect error on fd 19: ECONNREFUSED
Nov 25 11:49:35 patchbox authbind[836]: INFO:tornado4.access:200 GET /img/favicon/favicon-32x32.png (192.168.0.101) 4.43ms
Nov 25 11:49:35 patchbox systemd[1]: Stopping MOD-UI...
Nov 25 11:49:35 patchbox systemd[1]: modep-mod-ui.service: Main process exited, code=killed, status=15/TERM
This what is in the logs…not sure what it means though or how to fix
What about mod-host logs?
Nov 26 06:19:46 patchbox systemd[1]: modep-mod-host.service: Main process exited, code=killed, status=11/SEGV
Nov 26 06:19:46 patchbox systemd[1]: modep-mod-host.service: Failed with result 'signal'.
Nov 26 06:19:48 patchbox systemd[1]: modep-mod-host.service: Service RestartSec=2s expired, scheduling restart.
Nov 26 06:19:48 patchbox systemd[1]: modep-mod-host.service: Scheduled restart job, restart counter is at 2.
Seems that the lv2 plugin is killing mod-host and mod-ui
SEGV means ‘segmentation fault’, meaning that some invalid memory access was performed, most likely after the plugin was loaded. This would indicate a bug in the plugin, or that it was built in some incompatible way.
@Giedrius looks like I was being silly and compiled for modduo instead of modduox and the duo’s armv7 architecture is what is causing the SEGV fault. Rebuilding now and will post my updates once all is done
No difference unfortunately…bummer
You could try to ask the author of the plugin whether it’s known to work on Raspberry Pi, or if there’s any known issues.