#222

apologies if this has been covered already but I was wondering whether there is any reason (other than speed of charging) that means I should use the 2A charger @tehn supplies with norns and not just an iphone 1A usb plug? The 2A is US so I’d need to use an adapter. In the interests of keeping things compact, and not having to buy another horrible plastic adapter, I thought i’d check with people who know more about electricity than me (almost everyone it seems). Thanks

#223

fwiw I’m having no problems using an iPhone charger.

#224

OK great, thanks. I still can’t believe this thing runs on batteries AND powers my grid, crazy.

#225

Ok, thanks for all the MLR info :slight_smile:

1 Like
#226

I was worried that the battery on norns was running out way too quick for the mA consumption, watching the numbers fall from 100 on levels page and rushing to record what I was doing before it ran out. But it just kept on going and going on zero, probably took an hour to go from 100 to 0 and it’s been going for another hour on zero with around 800mA consumption. So the numbers are off not the battery, just in case anyone else is in the same situation and gets panicked by the 0.

#227

agreed, the battery monitoring needs some attention, it seems to sometimes mis-report.

#228

i jammed with norns mlr with my grayscale 128 plugged in and the battery lasted for well over three hours. it was down to 10 when i stopped.

4 Likes
#229

Regarding wifi connection difficulties: I’m one of those unfortunate weirdos whose home wifi network has a space in both the SSID and the password. Had to make some changes to norns/lua to make that work, PR here: https://github.com/monome/norns/pull/434

With those changes in place, I was still getting “password failed” connecting to my network. Taking a look at the norns journalctl logs and my router monitoring info (it’s an eero mesh) I could see that the norns actually did connect, but failed to get an IP address. I suspected that the clock on the norns, set to May 24, was too big of a skew for the eero policies to accept. These steps allowed me to finally connect:

  1. put norns in hotspot mode
  2. ssh we@172.24.1.1
  3. ./norns/stop.sh (changing the date with scripts running froze the norns the first time)
  4. run sudo raspi-config and go into localization options to set timezone to US/Eastern
  5. sudo date 201806231416.12
  6. sudo reboot now

Raspbian should eventually get and store the correct time from the network once it’s connected, but some finicky routers might insist that the original clock be not too far off.

3 Likes
#230

I have the same problem. It’s surprising, because the SSID does display correctly, space and all. But, password never accepted.

Was able to more or less follow your directions on the clock update.
(sudo date needs a -s in there. And mine didn’t like your date format.)

Not confident (nor competent) enough to apply the PR yet, though.

I guess it can wait for an official update. Just sort of a pain, not having browser access to the outside world while connected.

#231

If you just want to make SSIDs with a space work, the change to line 1035 of norns/menu.lua should be enough.

#232

another thing to try is manually updating $HOME/ssid.wifi and $HOME/psk.wifi. those should get picked up by the menu and you’ll be good to go.

edit: quotes may be needed for strings with spaces. dunno. not in a good place to check…

1 Like
#233

so just for clarity do recorded samples directly into mlr get discarded upon shut down?

#234

correct. i’m looking to add loop saving soon.

4 Likes
#235

Regarding syncing with a thumb drive does it need to be a dedicated drive for norns? Will I run into issues if it’s storing other files on it?

#236

I think you should be fine assuming the USB key is FAT32 formatted. The key thing is that the sync feature will copy to and copy from a folder/directory called dust at the top level of the USB key so as long as that folder doesn’t exist beforehand I’d expect it to work.

#237

Thanks that makes sense. Just figured I’d ask for clarity

#238

that’s great I’m looking forward to that. such a powerful little sampler.

#239

Hi, I have a problem with the audio engine not starting after rebooting - any ideas what to do to start it manually?
I was trying to create an engine in sc yesterday which I put in the engine dust/lib/sc folder, so was thinking this was the issue. Since the audio engine didn’t start on reboot I deleted and removed that particular file I was working on, but I still get that error when trying to start every patch and after every reboot.

image
12CAA1B7-DC52-4ECD-9D69-7FE138A26F0E.jpeg1936×1936 619 KB

#240

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

it may be, like me, you forgot to rename the engine in the .sc file, this causes scsynth to fail to start due to a duplicate SC class :frowning:

2 Likes
#241

Ok thanks - I’ll check that out. What is the best way to view and delete that file. At the moment, I am backing up to usb, deleting the file on a laptop and reinstalling, since I can’t view that file in maiden remotely. Is there a remote way of viewing every file on Norns?

1 Like