you’ll probably need to delete the file you created in…
~/.local/share/SuperCollider/Extensions/dust/sc/

I’m afraid i can’t find the folder on norns - theres a dust/lib/sc folder were i deleted my original file from already. I deleted that via USB drive syncing.
Not sure how to access that link - do you connect norns via usb cable to a laptop and access via the terminal window?

is that link you gave on a Linux laptop or directly on norns?

i’m on macOS so from the laptop side would direct me to this ~/Library/Application Support/SuperCollider/Extensions/
which also doesn’t exist on my laptop even though i have supercollider installed.

Sorry, its all very confusing to me.
Not sure why you can’t view all the folders on the screen in Norns like you would with file/system manager?

I would use a program like Cyberduck to SFTP into norns and delete the file manually. I’ve found that sometimes the USB sync doesn’t delete the file. Use the username we and password sleep when logging into norns via Cyberduck

6 Likes

Thanks @carltesta , I got into Norns via Cyberduck.

I’m looking for
~/.local/share/SuperCollider/Extensions/dust/sc/

But t it doesn’t exist.

Update : I did find a folder with an engine that I deleted before - so I deleted it again with Cyberduck. Looks like that worked after rebooting.

The correct folder is :

home/we/dust/lib/sc

~ means /home/we

so look in /home/we/.local/share/Supercollider/dust/sc/

better yet, find the actual error: ssh into the norns:

cd norns
./stop.sh
./crone.sh

you’ll see crone (sc) start up and throw an error. ctrl-c to quit and go fix the file

1 Like

Thanks - I found the rogue file in home/we/dust/lib/sc

I redeleted, rebooted and now it working - I updated my previous post above

I didn’t see the folder you suggested (is it hidden?) :

/home/we/.local/share/Supercollider/dust/sc/

Files and directories that start with a “.” are hidden by convention. I’d also suggest to ssh into norns and get comfortable with the command line. It doesn’t take long to learn the basics and it’ll make editing and transferring files much easier in the long run.

1 Like

Thanks - having access via Cyberduck helps a lot now I can actually see what going on. I can also now see what specific UGen stuff is on Norns.

At the moment I’m on Supercollider going through different generators for coding ideas and super impressed what is available, especially the Chaos/Gendy self generating stuff. Its just a case for me to get that stuff translated across in Lua and working the way I want it to on Norns.

5 Likes

this sounds super interesting to me. I really need to find some time to dig into this stuff

1 Like

hey everyone,

im having issues with mlr. i loaded in a 8 bar loop and found that when it gets to the end of the loop it will drop out audio for about 16th of a note before staring again. also, if there was a loop previously loaded in the track, it will play a a sliver of the previously loaded sound in that 16th note of space before starting over. also, it will fill that that 16th note of space with a part of the next descending track if there is a sound loaded in it. this all make it impossible to use a 8 bar loop.

also, in hopes that an update would help i updated to norns180603, and now i cant seem to log in to maiden via hotspot. i was using it in hotspot in order to avoid the confusion of logging in through a router. i guess i’l try that later, just feeling a bit spent after spending all day troubleshooting.

anyone else having these issues?

1 Like

the update removed the need to use port 5000 on maiden, just try typing in the IP address.

i’ll check out the mlr loop issue. if your loop is longer than 10 sec if might be the problem.

2 Likes

I’ve had the same issues loading loops sometimes and haven’t been able to figure out how to recreate it.

i am not sure if you’re having a problem that i feel like ive been having, but just in general, i have found that norns doesn’t like playing large audio files. ive had a couple lockups in glut and mlr loading things that were longer (3-5 minutes). i’ll try again when i get home tomorrow…

mlr is not going to handle large files gracefully right now. i’ll be fixing this…

3 Likes

Is this the best place to report bugs, maybe I should be using GitHub instead? I managed to crash my Norns by attempting to load http://norns.local/doc/modules/osc.html, I was connected via WiFi. Is there a log I should post?

1 Like

If you have a github account that would be preferred, that’s the place where we track all issues/work

2 Likes

after an hour of charging through USB from my MacBook Pro while going through studies, I started seeing these blocks of messages in maiden:

failed to read battery percentage
failed to read battery charging status
failed to read battery current
failed to read battery percentage
failed to read battery charging status
failed to read battery current

anything I can help log in GH? (edit: maybe friggin READ the GH for current convos, Derks!)

2 Likes

oh yeah, i get those reliably too. conversation ongoing here:

https://github.com/monome/norns/issues/404

1 Like

shamed edit above. thanks for the redirect!

2 Likes

thank you! works like a charm

any chance this is one of the new things included in the update friday? sorry to be a pest

1 Like