I tried the
more verbose tape names method in the tweaks docs of the norns community and I think I have messed something up in the process. I seem to be getting a
supercollider fail message but I cannot determine what the cause is just yet. And it seems to disappear after sleep. Honestly I do not know what makes it pop up - I just know it started after this tweak.
One of the potential symptoms (or maybe it is script specific??):
I can record to tape just fine with the Awake script (and in the tape/ folder will be e.g. 0024 awake 90bpm.wav) but @okyeron
MI-resonate script will not save even though it allows me to proceed with a verbose tape name and and hit start and stop. The transport shows it is recording but nothing gets saved.
I have followed the troubleshooting steps in the Norns help docs. Here is what the super collider restart produces:
I could just revert the
tape.lua file and see if that solves things or I guess I should just run update 210607 and see if that irons things out?
It is totally possible I borked something when using cyberduck. However, since this was one of my first attempts at making a change to Norns, I am not quite sure what I’d be looking for that I did wrong. Anyhow, thought I would put it out there for advice on how to proceed. Thanks yall!
EDIT: it appears the
supercollider fail appears after I sftp into Norns via cyberduck and disconnect. Even if I do not modify anything and disconnect, after I
restart Norns the
error: supercollider fail message appears and then powering on after
sleep makes it go away but the not saving to tape issue still persists. Here’s more detail: if I start a recording before I start the MI-resonate script, I get for example:
0027 none 90bpm.wav and the recording is saved! But when it is more verbose, e.g.
0029 mi-eng/resonate-r 90bpm it does not save to tape as described below.