norns: new image 220306

alexam · 2022-03-17T10:11:42.994Z

yes i am using the official supply with 3 amps

aurbit · 2022-03-17T15:16:39.458Z

I’m still very new here, so please forgive me if this should go somewhere else. Is anyone else having trouble with the Boingg script on this new image? It was working ok for me on my previous hacked together setup with unofficial hardware. Now I’m using a true norns shield and this latest image. The graphics for Boingg show up on the screen and I can place a ball and watch it bounce. However, when the bounce occurs there is no sounds and the lines below #script init in the log pasted below show up in the REPL at the moment there should have been a note played. I noticed the engine is PolySub and saw there were changes in this image pertaining to that, but don’t know enough to make the necessary adjustments.

REPL output:

# script clear
pset >> write: /home/we/dust/data/cyrene/cyrene-01.pset
calling: passthrough post cleanup
# script load: /home/we/dust/code/boingg/boingg.lua
calling: passthrough
# script run
loading engine: PolySub
>> reading PMAP /home/we/dust/data/boingg/boingg.pmap
m.read: /home/we/dust/data/boingg/boingg.pmap not read.
lua: /home/we/norns/lua/core/clock.lua:59: bad argument #1 to 'resume' (thread expected)
stack traceback:
	[C]: in function 'coroutine.resume'
	/home/we/norns/lua/core/clock.lua:59: in function 'core/clock.resume'
lua: /home/we/norns/lua/core/clock.lua:59: bad argument #1 to 'resume' (thread expected)
stack traceback:
	[C]: in function 'coroutine.resume'
	/home/we/norns/lua/core/clock.lua:59: in function 'core/clock.resume'
lua: /home/we/norns/lua/core/paramset.lua:423: invalid paramset index: swing_amount
stack traceback:
	[C]: in function 'error'
	/home/we/norns/lua/core/paramset.lua:423: in function 'core/paramset.lookup_param'
	/home/we/norns/lua/core/paramset.lua:327: in function 'core/paramset.get'
	/home/we/dust/code/cyrene/lib/arcify.lua:122: in upvalue 'redraw_ring'
	/home/we/dust/code/cyrene/lib/arcify.lua:146: in upvalue 'redraw_all'
	/home/we/dust/code/cyrene/lib/arcify.lua:217: in field 'event'
	/home/we/norns/lua/core/metro.lua:164: in function </home/we/norns/lua/core/metro.lua:160>
Engine.register_commands; count: 25
___ engine commands ___
ampAtk	 	f
ampCurve	 	f
ampDec	 	f
ampRel	 	f
ampSus	 	f
cut	 	f
cutAtk	 	f
cutCurve	 	f
cutDec	 	f
cutEnvAmt	 	f
cutRel	 	f
cutSus	 	f
detune	 	f
fgain	 	f
hzLag	 	f
level	 	f
noise	 	f
shape	 	f
solo	 	if
start	 	if
stop	 	i
stopAll	 	
sub	 	f
timbre	 	f
width	 	f
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
# script init
lua: 
/home/we/norns/lua/core/paramset.lua:423: invalid paramset index: output
stack traceback:
	[C]: in function 'error'
	/home/we/norns/lua/core/paramset.lua:423: in function 'core/paramset.lookup_param'
	/home/we/norns/lua/core/paramset.lua:327: in function 'core/paramset.get'
	/home/we/dust/code/boingg/boingg.lua:99: in upvalue 'update_cycle'
	/home/we/dust/code/boingg/boingg.lua:120: in field 'event'
	/home/we/norns/lua/core/metro.lua:164: in function </home/we/norns/lua/core/metro.lua:160>

Justmat · 2022-03-17T15:41:15.824Z

that is/was a bug with boingg, i just fixed it. update your boingg script and you should be gtg

aurbit · 2022-03-17T18:14:53.002Z

Wow thanks for the quick fix! Confirmed boingg is working as expected for me now.

ampism · 2022-03-18T09:28:08.527Z

So am I correct in saying that if I have a shield, I can ignore this vid until 3:40? It’s just the Etcher/sd card stuff, and no need to dismantle the shield and flick a switch?

@tehn I’m not concerned about losing anything. Just concerned about the actual process.

dani_derks · 2022-03-18T10:41:47.086Z

ampism:

It’s just the Etcher/sd card stuff, and no need to dismantle the shield and flick a switch?

correct! just pull the card, do the etcher / imager process as outlined in that part of the video / docs, then you’re set to put the card back in shield, expand your file system (!!), and continue restoring your data by downloading fresh copies of the scripts you want and migrating your data and audio back in over wifi. the etcher flashing + validation process for a shield card should take around 10 minutes total.

eequeue · 2022-03-18T13:05:28.632Z

I didn’t see this answered elsewhere in the thread (my apologies if I missed it). To ensure we’re flashing the correct image on a Shield we’d use the date code on the top left corner?

For example mine says, 200323 and I’m using an R Pi 3, so I would flash rpi3-cs4270, correct?

Edit damn fat fingers Good catch, @JosueArias

JosueArias · 2022-03-18T13:07:51.698Z

Not CS4279 but 4270 !

faisanquartet · 2022-03-18T17:51:59.661Z

Just installed the new image and the brand new shield received few days ago. (Raspberry 4 with the new codec)

All went smooth until expanding filesystem, which was OK to process. But after the reboot I got a “Supercollider failure”.

Turned off the machine and now it seems OK.
Don’t know exactly what happened

bharris22 · 2022-03-19T12:32:31.374Z

dani_derks:

bring your data and audio folders back in

download fresh copies of the scripts you want on your device and run them so their dependencies (if any) are all installed

I flashed the image, and Awake is up and running . So far, so good.

Now my question is about bringing the data and audio folders back in. In my old data folder, there are sub folders for many of my scripts. If I copy those data folders to the new and improved dust folder, and then download fresh copies of the scripts through Maiden, will that save any time? Or, will downloading and installing the new scripts simply create new sub folders for those scripts?

Similarly, for example, I have audio folders for Arcologies and mx.samples, among others - the mx.samples folder is quite large. Am I better off copying the audio folders for these scripts into the new dust folder manually, or re-downloading the audio through the newly installed script? Does it matter?

Thanks in advance again for all your help!

dani_derks · 2022-03-19T15:35:47.092Z

glad you’re up and running!

bharris22:

In my old data folder, there are sub folders for many of my scripts. If I copy those data folders to the new and improved dust folder, and then download fresh copies of the scripts through Maiden, will that save any time? Or, will downloading and installing the new scripts simply create new sub folders for those scripts?

your backed up data folder will contain:

system.state: the parameter settings for the system, eg. reverb, compressor, levels, your list of previously-connected MIDI devices
system.favorites: the scripts you highlighted as favorites, which will show at the top of the script list with an asterisk (once they’re reinstalled)
subfolders for each script, which contain:
- a .pmap file: MIDI mappings which you created for that script
- .pset files: presets you saved for that script
- pset-last.txt: the last preset you had loaded for that script

so, it’s more a matter of whether you want to start totally fresh with those scripts, or if you want to restore your previously-generated sessions / play. it’s true that when you run a newly-downloaded script for the first time, a data subfolder is created for it if one does not already exist – but if you want to restore your previous work with a script, you should restore the data subfolders from your backup. running the newly-downloaded script on your 220306 software will not overwrite the restored data subfolders – rather, it will respect their presence and integrate your restored PMAPs and PSETs into the newly downloaded copies of the scripts.

bharris22:

Am I better off copying the audio folders for these scripts into the new dust folder manually, or re-downloading the audio through the newly installed script? Does it matter?

for audio, you can also just do a blanket restore. for example, if you restore your backed-up audio folder with all your mx.samples libraries, your newly-downloaded mx.samples will see these and surface them in the UI as selectable instruments.

hope this helps! please feel free to ping back with any further q’s / clarifications!

bharris22 · 2022-03-19T15:49:20.932Z

@dani_derks, this is very useful information - thank you! Off to copy folders now

ideaofnorth · 2022-03-19T19:07:38.659Z

dani_derks:

if you’re using a standard norns, the biggest snag for vanilla use seems to be the connection to etcher / Imager (the 5th step of the walkthrough ). fwiw, i also ran into this issue this morning with an old unit, which was actually resolved just by unplugging the usb cable, restarting my computer, and trying things fresh. worked first time after that. i’ve also added some other gotchas to that section:

So I’m running into this exact issue. Each time I try to Select Target the initializing device progress bar runs to completion, then starts over again and gets hung up around 20%.

I do have an older factory Norns and at this point have restarted my Mac (new M1 Mac Pro, os 12.2.1) 3 times, including once when it crashed and restarted itself. I’ve also tried 3 different USB dongles including an official Apple one, and 3 different USB cables. Any other ideas? Happy to go to email but thought others might run into this issue.

dani_derks · 2022-03-19T19:13:20.214Z

sorry to hear about the trouble, hope all’s well otherwise!
just to quickly verify, this is happening with both etcher and Imager?

ideaofnorth · 2022-03-19T19:17:24.276Z

Oh, I’ve only tried Etcher. Somehow missed the fact Imager could work with a Mac. I’ll try that next, thanks!

Edit: just tried Imager and I think am running into the same issue. Nothing shows up when I click Storage. Again tried different cables and restarting.

Screen Shot 2022-03-19 at 3.22.24 PM1584×1120 76.9 KB

dani_derks · 2022-03-19T19:42:24.840Z

this is a weird one to advise, but could you try flipping disk/run switch rapidly a bunch? like, a dozen or so times? apologies for the brute force nature of the suggestion, but this has worked for a few folks. if this doesn’t get it going, let’s move over to help@monome.org

ideaofnorth · 2022-03-19T20:17:38.192Z

I tried a couple bouts of flipping that switch around 20 times. I had a minor Mac OS upgrade I ran, restarted the laptop, tried different cables and dongles, but had the same issue. Thanks again for all the help today, I’ll email now.

EDIT: I brought my Norns to the office today to attempt the command line flash and update. I tried Etcher one last time with a usb cable connected to my apple display and it worked! For the record I tried 2x 3rd party adapters and an official Apple one at home with no luck.

chochacho · 2022-03-20T23:52:13.706Z

For those running into issues, I’m on an M1 Mac and was having a problem where Balena was hanging while initializing or crashing at around 3/4s of the way through.

Turned out it may have been my USB hub. I connected directly to my computer and the steps in the installation guide worked fine.

ypxkap · 2022-03-21T03:47:49.982Z

like many technophobes (a role i have come to embrace in the last year or so) i’ve been dreading this one. so in case i wasn’t the last one to run this update and you’re reading this looking for a sign…i ran into zero of the issues above.

my info:
—“standard” norns
—2019 macbook pro
—apple-made USB A to USB C adapter
—not the “standard” norns charger cable (zero recollection of which cable that was)
—balenaEtcher on macos 11.6.2

the process was exactly as described in the guide. my one issue was when i screwed the plate back on i didn’t immediately notice that i screwed it on upside down.

(if this wasn’t the case for you reader—sorry to gloat!)

spamula · 2022-03-21T04:30:47.558Z

ypxkap:

like many technophobes (a role i have come to embrace in the last year or so) i’ve been dreading this one.

Same boat here Shield has been sitting in front of me for days, waiting for me to take it apart and get the SD card out

I dont even have any files I care about losing

EDIT: Doing it now… And its all good. First reboot gave me a supercollider fail. Second reboot and everything is working just fine. Excellent stuff.