#1201

norns 2 : is there somewhere the signal flow?

#1202

command line:
sudo date -s "Thur Apr 4 12:00:00 UTC 2019"

also can check date to see if your timezone is correct, etc. sudo raspi-config (in localization options) to change your timezone

I think there were some issues with not being able to use a network time server Ah - the CM3 does not have a real time clock (RTC) to keep the time set when the unit is not-powered so I think it gets reset by the network when it boots?.

1 Like
#1203

Here it is!

norns-audio-route
norns-audio-route.png1429×323 12.1 KB

And here

image
D716BDC9-6092-4F4C-BC73-3206A89EC91C.jpeg1755×1105 239 KB

2 Likes
#1204

thanks @AlessandroBonino, what’s the difference between input and external?

#1205

“external” is application input, in this case, supercollider. but in the future this jack port will be available to any application run on norns (pd, custom, etc)

full norns 2 docs will be posted tomorrow. in the meantime: https://github.com/monome/docs/blob/norns2/docs/norns/index.md

2 Likes
#1206

@swhic I agree that external is a bit counterintuitive for the user, Application/app or something would be more intuitive. I explained that Ext is actually what the user perceives as the internal synth at least four times this week.

1 Like
#1207

renaming “ext” to “engine/eng” for the release tomorrow :slight_smile:

3 Likes
#1209

What’s the battery life on the Norns like? I’m only getting about 2 hours with no grid attached. Wondering if it needs a few cycles/callibration?

Lovely thing though, very touchable. I keep walking around holding it. My first script is running also, it seems very easy to work with. Looking forward to digging into it more.

2 Likes
#1210

2 hours sounds about right. it’s a small battery, 2000mah. if you need extra long life you can use a battery bank— they’re cheap and USB-USB makes this easy.

norns is not a low-power-optimized device. since there’s an industrial raspberry pi inside it’s quite powerful and can draw a lot of power under load. it’s a good idea to keep an eye on the battery level, and generally have it plugged in.

2 Likes
#1211

Cheers. Sleep deprived, and was convinced it had 4-5 hour life. Not an issue though.

#1212

I just updated to 2.0 and added all the new scripts. Everything seems to be running well except I seem to have lost access to the params menu on all scripts and cannot get strum to work with the Karplus_Rings engine! Any idea how to help me troubleshoot these? I’m very new to Norns and 2.0…

TIA :heart:

#1213

Parameters work different now. When you are on the main menu (not in patch), use ENC 1 to cycle through menu pages. Parameters is the last page to the right (if I recall correctly). Enjoy!

3 Likes
#1214

Awesome! Thanks so much @yobink for the quick reply. Great system, now I just need a nice little midi controller :grimacing:

#1215

Hi - Do you get errors or just can’t hear anything?

The KarplusRings engine volume is quite low. I asked the author of the engine if there was any way the output could be increased and he was not aware of any. One thing I’ve done is to increase the BPF Freq param to 400 or so. That helps. The low volume from KR is why I added the PolyPerc version. Not same sounding, but at least its an option.

1 Like
#1217

Can you open maiden in your browser and try to run strum_kr again? Then let me know what error message you’re seeing?

1 Like
#1219

Open your browser and enter “norns.local” or the IP address of your norns.

1 Like
#1220

Thanks! I’ll get back to you shortly :heart:

#1221

obviously not a game breaker, but does anyone know if this is how the 2.0 menu system is supposed to look? i.e. no file tree, just every code on the main page?

#1222

yea, that’s the new design.

i think we need to add a simple ‘favoriting’ system asap.

8 Likes
#1223

without git / terminal

download latest from github

(direct link)
https://github.com/monome/we/archive/master.zip

unpack and transfer to ~/dust/code/we on your norns.

with git / terminal

shell into your norns, and do

cd ~/dust/code
git clone https://github.com/monome/we.git

ensure there is only one copy of we anywhere in ~/dust. otherwise supercollider won’t work.

4 Likes