So I was playing with a script and I wanted to record the output to ‘tape’ (locally on the norns). I couldn’t figure out an internal audio “loopback” way to do this, so I did something seemingly unholy: I plugged the outputs into the inputs. It worked, but it still feels so wrong. Is there a way to record what is being played by a script to tape without resorting to what I just did above? Is this the canonical way of recording what you hear on your norns, back to your norns?

@gmuller the tape always records anything that is getting passed to the outputs, so you shouldn’t need to do this cable loop. it’ll record the engine output as-is.

1 Like

Weird @tehn , I tried that and got 4:36 of silence. I’ll try again this afternoon. I’ll look really silly if it works and I just did something wrong. Thanks!

Well, @tehn I’m not sure what I was doing wrong the first time I tried it, but it seems to work. It was a little on the quiet side but thats probably my source samples. And yeah, I feel kinda silly now.

So this started happening frequently after playing MLR with midi sync enabled. Touching a button on the grid causes the screen to go crazy for a brief moment before staying like this

a very noticable high pitched noise is coming from the unit. The clock is very unstable and does fluctate on every step. Unable to restart the unit, i have to push the button under the unit.

any ideas?

Yes, I’ve had this, it’s a bug since midi cc’s were enabled in the new firmware update - it has already been reported in the MLR thread

I get that exact thing too!
Hopefully its sorted soon.

working on this.

one thing to try is moving your midi and grid around to different USB ports. i can’t explain why but i’ve seen this change the behavior.

2 Likes

when I’m trying this it won’t delete my sample folder, says it’s a directory

to delete a folder, you’ll want to add the recursive option. assuming your folder is called sample and you’re in the directory that contains it, try something like:

rm -R sample

but be super careful. there’s no undo!

6 posts were merged into an existing topic: Norns: scripting

I’m having issues with Kayan, when I start messing around with the parameters, I start getting glitching notes and noise. It then will slowly get worse and even seems to react to rotation of the encoders. Sometimes it will lock up and I have use the reset button. Other times I can switch to a different script and it seems fine. I am running the 180707 update. I have run into similar noise in other scripts once and a while, it seems like it’s when I start nearing the top end of certain parameters. Anyone else have this issue?

And one more question: What are the largest integer numbers that can be used inside a script?

I just bought a Norns used, and I’m getting a lot of crashes. I’m not doing any scripting, and have yet to do anything complicated at all really. I checked and I’m on the latest version [180707]

One crash that’s happening consistently, is I’ve joined my Wifi network, visited http://norns.local/ and tried to create a sub-folder within “Audio” to store some of my completed tracks from SoundCloud, so that I could remix them in MLR.

The first time the device froze when I tried to add the folder. I hard reset, and rebooted. I then had to go back into network menu to turn wifi off, and then switch it back on before I could connect to Norns again.

The second time, I was able to create the folder, but then as I went to copy over some files onto a thumbdrive, Norns was frozen again a few minutes later.

Any ideas?

@xeric there is a known wifi bug that we’re working on: https://github.com/monome/norns/issues/399

what’s happening is that sclang gets confused by the time sync jump when wifi connects, and it hits 100% cpu. after an immediate restart the time jump should be minimal, and the problem should not present itself.

the other way around this is to serial connect over USB, run stop.sh and then start.sh in ~norns/

or just use hotspot mode (which annoyingly means your laptop won’t be on the internet)

we’re hoping to get this fixed soon, it’s top priority

3 Likes

question (apologies if this isn’t the correct place) - has deleting files from TAPE directly via norns been considered? I think this could be a useful feature and didn’t see anything in git issues.

5 Likes

Speaking of tape recordings, I’ve also been thinking that having a quick interface to rename a file directly on Norns could be useful, especially if you’re generating a lot of little recordings to be used in your current session - I find myself getting lost pretty quickly. Maybe something like the interface that’s already in place for entering a network name in the system menu?

6 Likes

this is a good idea. TAPE has quite a list of features to be changed/added, i’ll add this

@Olivier renaming makes sense too

added issue: https://github.com/monome/norns/issues/487

4 Likes

20 chars of awesoooome

“I’m having issues with Kayan, when I start messing around with the parameters, I start getting glitching notes and noise. It then will slowly get worse and even seems to react to rotation of the encoders. Sometimes it will lock up and I have use the reset button. Other times I can switch to a different script and it seems fine. I am running the 180707 update. I have run into similar noise in other scripts once and a while, it seems like it’s when I start nearing the top end of certain parameters.”

I’m still having this issue… Primarily with Kayan, but I have had it happen in I think Earthsea. It’s almost like a digital noise feedback loop that causes it to total crash and freeze. Anyone else have this happen?