#122

Experienced complete loss of audio today running Earthsea. Seemed to occur as I was moving the Grid to my lap… Might’ve jostled the USB connection. Mixer screen confirmed no audio being sent out. A sleep cycle fixed it.

#123

this is likely related to an audio bug that is fixed in the update. hold tight.

1 Like
#124

Had a little trouble getting norns to see my grid again – it did eventually work, but flipping the inside switch wasn’t doing it. Not sure what got it going this time, which makes me think it was probably a coincidence the first time. :thinking:.

I will play a bunch this week and try and confirm for myself if there is a problem or not.
If so, I will mail support directly and take it from there. :+1:

1 Like
#125

A post was merged into an existing topic: Norns: updates

#126

3 posts were merged into an existing topic: Norns on Raspberry pi + Blokas PiSound

#127

what is the easiest way to load samples into /audio/common
iwould like to add some wavs there
i am having a rough day so forgive me if i missed the general users manual

#128

Sync Norns to a FAT-formatted USB drive to back everything up, then load that drive to your computer and add your audio files to dust/audio/common or even a new folder in there. When every is loaded up, plug the drive back into Norns and then sync from USB.

1 Like
#129

also remember it’s just a linux computer, you can shell in, scp, etc.

manual is here: https://monome.org/docs/norns

1 Like
#130

Thank so much
got all into building shenanigans today and i tried to program a granular swarm and now i fell into the Euclidean patch
awesomes

#131

What size USB i assume at leat 4GB?

#132

More wifi problems with the new update180603.

Here is a successful wifi connection with my tethered phone:

Log Selected interface 'wlan0' wpa_state=SCANNING p2p_device_address=40:a5:ef:dc:48:e8 address=40:a5:ef:dc:48:e8 uuid=981e2e8d-c470-5c82-8393-6086dbaba3df

Selected interface ‘wlan0’
wpa_state=ASSOCIATING
p2p_device_address=40:a5:ef:dc:48:e8
address=40:a5:ef:dc:48:e8
uuid=981e2e8d-c470-5c82-8393-6086dbaba3df
dev: loaded udev
DUID 00:01:00:01:22:69:57:63:40:a5:ef:dc:4b:ad
wlan0: IAID ef:dc:48:e8
wlan0: adding address fe80::ddc8:88d2:802e:123a
wlan0: soliciting an IPv6 router
wlan0: rebinding lease of 172.20.10.3
wlan0: probing address 172.20.10.3/28
wlan0: leased 172.20.10.3 for 85536 seconds
wlan0: adding route to 172.20.10.0/28
wlan0: adding default route via 172.20.10.1
Too few arguments.
Too few arguments.
forked to background, child pid 12509
PING 172.20.10.1 (172.20.10.1) 56(84) bytes of data.
64 bytes from 172.20.10.1: icmp_seq=1 ttl=64 time=12.5 ms

— 172.20.10.1 ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.567/12.567/12.567/0.000 ms

Here is an unsuccessful attempt with my wifi:

Log Selected interface 'wlan0' wpa_state=SCANNING p2p_device_address=40:a5:ef:dc:48:e8 address=40:a5:ef:dc:48:e8 uuid=981e2e8d-c470-5c82-8393-6086dbaba3df Selected interface 'wlan0' wpa_state=ASSOCIATING p2p_device_address=40:a5:ef:dc:48:e8 address=40:a5:ef:dc:48:e8 uuid=981e2e8d-c470-5c82-8393-6086dbaba3df

Selected interface ‘wlan0’
bssid=82:37:73:c8:0e:9c
freq=2452
ssid=NETGEAR-Guest
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=4WAY_HANDSHAKE
p2p_device_address=40:a5:ef:dc:48:e8
address=40:a5:ef:dc:48:e8
uuid=981e2e8d-c470-5c82-8393-6086dbaba3df
dev: loaded udev
DUID 00:01:00:01:22:69:57:63:40:a5:ef:dc:4b:ad
wlan0: IAID ef:dc:48:e8
wlan0: adding address fe80::9073:c880:1b4:c513
wlan0: soliciting an IPv6 router
wlan0: rebinding lease of 192.168.0.48
wlan0: probing address 192.168.0.48/24
wlan0: leased 192.168.0.48 for 86400 seconds
wlan0: adding route to 192.168.0.0/24
wlan0: adding default route via 192.168.0.1
Too few arguments.
Too few arguments.
forked to background, child pid 14414
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

— 192.168.0.1 ping statistics —
1 packets transmitted, 0 received, 100% packet loss, time 0ms

#133

despite what the menu says, did you try pointing your web browser to 192.168.0.48?

#134

Hi Tehn,

thanks for the quick one. It works - I can reach Maiden - on the tethered phone at its associated ip address (172.20.10.3) when my laptop and my norns are on that same network.

I cannot reach Maiden on my home wifi network (wifi>failed displayed on norns). But I can tty in and see that it is connected to my network (ip 192.168.0.48 in this case).

It’s not a big problem as I think I will just use my tethered phone for now (was fixed in this update - thanks). I just wanted to identify to see if it might help to troubleshoot.

1 Like
#135

Ok! Not sure if this is the appropriate topics to create or should I post in the help thread?

Anyways just received the Norns and I cannot find a way to load existing loops in MLR.

Anyone can shed some light? Thanks

1 Like
#136

Open mlr. On the grid, press the 3rd button on the top row. This will open the clip page. On norns press button 2 to load a clip into the selected slot.

4 Likes
#137

you need to sync a usb drive to norns.

plug in a usb drive
go to parameters,
go to system
go to sync
hit “sync to disk”
this will create the “dust” folder on your usb drive
inside “dust” there will be an audio folder, you can use this to transfer samples in to mlr

2 Likes
#138

https://monome.org/docs/norns/dust/tehn/mlr

and just noticed a typo here

2 Likes
#139

re:MLR, potential silly question… I feel like i’m overlooking something obvious.

I’ve got a TS cable input in the IN1 input and i’m only able to get tracks 1 and 3 to record a loop. Tracks 2 and 4 are always blank. Recording monitoring shows appropriate levels. Is there something in the system audio settings that I need to tweak regarding mono input? Something else?

#140

So I was able to get tracks 2 and 4 to record with a duplicate mono cable to the IN2 input. I was just a bit confused as Norns seems to take the mono inputs and duplicate them appropriately when monitoring/recording. Ah well, at least it’s working and happy to be exploring.

#141

Weird experience getting maiden fired up today with the new firmware.

Start norns. Start wifi. Wifi failed, norns locked. Removed wifi USB, inserted wifi, reinserted wifi, inserted USB stick (because why not), restarted.
On restart, norns recognizes network, maiden starts at norns.local. And may I say, it’s a beauty.

Now I want to add the “use button 2 to turn the sound on and off” for the “why?” script … when I’m feeling brave I’ll play with the code…