how are your command line skills?

you’ll need to serial in with screen (from the docs:)


When connected via WIFI you can SSH into norns at the IP address shown in SYSTEM.

  • user: we
  • password: sleep

Without WIFI, you can connect to norns via USB-UART by connecting the power cable to your computer. On Mac/linux do:

screen /dev/tty.usb(tab) 115200

Where (tab) appears hit TAB to autocomplete the serial number. Login is the same as above.


culprit is like tape recordings:

cd dust/audio/tape
ls -l

this will show the files (and sizes)
to remove one:

rm (filename)

if it’s not there, we have to dig in deeper

2 Likes

thanks so much Brian- is there a way to do the USB thing on Windows?

Hello folks. Could someone please point me to some more details about midi mapping? I have followed the instructions buried above, but have had no response from the parameters in question.

The devices I’ve tried show up in devices>midi and it seems to go into learn more… But then no midi control. What am I doing wrong?

Oh, and can one map midi control to params currently set to norns buttons and encoders? eg. Use a foot pedal to trigger recording in cranes?

Many thanks!

1 Like

if this is in cranes, the current software doesn’t allow for the type of params in the script to be midi mapped. this will be addressed and cranes will be changed in the coming update, though!

Good to know about cranes (which I love, by the way). But the mapping problem seems to be in other patches too.

which I love, by the way

thanks so much for the kind words! :slight_smile:

I believe the issue is pervasive, depending on the script you’re loading:

to confirm, you haven’t been able to get any scripts responding to midi map?

1 Like

managed to delete the tape files using Putty to emulate linux commands. confirmed they were deleted by loading up a sampling script and navigating to the folder in norns, and they were in fact removed successfully.

disk still showing up 0MB free and wifi not working. :woozy_face:

logs?

1 Like

ooh interesting! these are the top files

-rw-r----- 1 root adm 783M Feb 12 06:25 daemon.log.1
-rw-r----- 1 root adm 783M Feb 12 06:25 syslog.1
-rw-r----- 1 root adm 207M Feb 12 22:42 syslog
-rw-r----- 1 root adm 207M Feb 12 22:42 daemon.log
-rw-r----- 1 root adm 948K Feb 12 02:26 kern.log.1
-rw-r----- 1 root adm 707K Feb 12 06:25 messages.1
-rw-r----- 1 root adm 432K Oct 2 06:25 syslog.7.gz

EDIT: navigated up to your original comment you quoted and did Brian’s suggested temporary fix to remove the top 2 files. disk space is back, and wifi is working!

begs the question though as to how this happened, if it could happen again, what to do from here :thinking:

but thank you so much @okyeron and @tehn for what appears to be a temporary fix!

2 Likes

made GH issue. we should install a logrotate cron job or whatever the contemporary equivalent

2 Likes

i’ve already run into trouble on the first study - i also ran the included study code (study 1 in the study folder) and ran into the same issue.

for the part of the tutorial where i’m supposed to be seeing key names and states, keys 1 + 2 don’t do anything, key 3 returns an error. is there a certain screen i’m supposed to be on when i do this? i wasn’t getting encoder info in the message box either.

error starts with " attempt to index a nil value (field ‘?’) "

here’s everything i get when i run the first study. i only have up until the intro of the key function. the error text happens when i press k3:

norns.script.load("many_tomorrows.lua")
# script load
# cleanup
# script clear
# script run
loading engine: TestSine
<ok>
Engine.register_commands; count: 2
___ engine commands ___
amp	 	f
hz	 	f
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
tape_play_pos
tape_rec_dur
# script init
the end and the beginning they are the same.
READING PMAP
lua: 
/home/we/norns/lua/paramset.lua:177: attempt to index a nil value (field '?')
stack traceback: /home/we/norns/lua/paramset.lua:177: in function 'paramset.t'
/home/we/norns/lua/menu.lua:690: in field 'key'
/home/we/norns/lua/menu.lua:144: in function </home/we/norns/lua/menu.lua:121>

I ran into this issue and got the answer over on the studies thread:

There are a couple of things over there that may save you some grief until 2.0 comes out.

3 Likes

huh. i was scouring the forum and never saw that. lots of information here! thanks a lot.

1 Like

I’ve done a bit of diving on the subject but couldn’t really find anything concrete. I also went through the physical study, somewhat grasp the markeats passersby example. Any rate, I still can’t get an external sync to work. I’ve had success with CC and MIDI learn, but no clock sync. I’m specifically trying to sync playfair and/or foulplay.

I’ve tried numerous scripts that utilize external sync with Ableton (MIDI and USB) and an OP-1. Has anyone else had any luck with this? Am I missing something obvious? :woozy_face:

There are some improvements in midi - specifically clock - that I worked on that are not in the current (181101) release.

So this is greatly improved in the next release, but that doesn’t help you much right now.

If you were feeling adventurous you could get the more recent midi.lua, replace that, stop/start norns and then update the scripts with the new midi fu.

I have an example test script which should work with external sync. You’d need to work from here to update playfair or foulplay.

3 Likes

Some things to check:

  • Is the device you’re trying to sync with configured to send clock? Are you connecting that device directly to norns? Are you able to sync things other than norns to that clock source?
  • Can you receive midi note data from the clock source to norns? Try one of the scripts that responds to midi notes.

The more specifically you describe your situation the easier it is for folks to jump in with suggestions.

1 Like

Thanks for the reply.

External devices (Ableton and OP-1) are set to send clock and they work with other devices. I’m also able to send note data and CC to Norns. The issue I’m having, specifically with playfair and foulplay is when I set the clock to external, norns is unresponsive. I’m able to clock things with norns just fine but for certain projects I prefer to have one master clock coming from my DAW.

This is perfect, thanks for the test script. I can always sync from norns for the time being but I’m happy to hear about midi improving.

What software version is your norns running?

Running the latest version 181101. Actually just re-uploaded the install thinking that might fix it but no luck.