you should be able to see these errors by connecting with maiden, navigating to the SC REPL tab, and entering ;restart at the REPL prompt.
otherwise, you can stop/start things manually from the terminal on norns:
~/norns/stop.sh to stop everything
(killall sclang, killall scsynth to just stop supercollider components.)
sclang to launch the supercollider interpreter - it will start an scsynth process automatically
~/norns/build/matron/matron to launch matron/lua.
~/norns/build/crone/crone to launch the crone process (the ‘master’ jack client - not supercollider - which boots very fast and shouldn’t really need to be relaunched.)
(to be clear: the ~/norns/start.sh script (and the systemd services) willl launch matron and sclang with wrappers to pipe their stdin,stdout to the browser interface (via websocket.) so that’s the motivation for launching things manually if you want to capture output on the terminal instead.)
(NB: if you stop/relaunch SC components without stopping/relauching matron, not everything innorns menus / scripts will work - there is a handshake step that needs to happen. if you just need to see if SC interpreter is successfully launching - duplicate classes will prevent this - then it doesn’t really matter if matron is running correctly or not.)
lastly: if you just want to search for duplicate .sc files in ~/dust, this bash one-liner works for me (and yes, we should just bake something like this into the norns menu):
find ~/dust/code -type f -printf '%p/ %f\n' | sort -k2 | uniq -f1 --all-repeated=separate | grep *.sc
(alternatively, install and use fslint, for more options and ease of use at cost of some disk space)
(and a final pedantic point: what actually breaks SC is not duplicate filenames, but duplicate class names. in practice, for norns engines you are unlikely to encounter the latter without the former.)
yeah that’s on me, still. sorry! maybe i can do these today / tomorrow, they should be easy but life has been very full lately.
