#8

Norns doesn’t start up again now is what I meant by ‘can’t reboot’ :cry:

I guess I’ll wait for the images? It seems to be bricked.

#9

Being able to both translate and rotate the screen is very exciting, especially for animation! Is there a scale feature?

Sounds like a killer update, thanks all!

1 Like
#10

:eyes: https://www.cairographics.org/manual/cairo-Transformations.html#cairo-scale

1 Like
#11

i’d guess the download wasn’t complete or something
(@tehn we really gotta check hashes for these if we aren’t doing so already? nvmd, i forgot how it works)

if you can shell to norns then at least you haven’t lost your ~/dust, and if you want we can probably sort out a recovery procedure that doesn’t require reflashing… PM or email monome?)

1 Like
#12

I’m reflashing the SD card to the previous update and starting over. I wasn’t able to shell to Norns unfortunately. Thankfully, I downloaded my tape folder recently and there wasn’t any custom code in dust.

After flashing, when I update it now shows statuses like ‘downloading’ and ‘unpacking’. None of that happened last time.

2 Likes
#13

For anyone wondering, this fixes the problem Dan described here: the MIDI mapping screen implied that you could map the full range of a MIDI CC to a small part of the range of a control or taper param, e.g. you could control a filter cutoff from 2000 Hz to 20000 Hz, even if the param’s actual range went down to 20 Hz – but that wasn’t actually possible until now.

param mapping screen

The new version also shows actual param values for out (as shown above) instead of 0 or 1 for the min/max of the param range, and you can fine-tune the min/max by holding K3, like you can in the params edit menu.

8 Likes
#14

can you describe what happened when it broke?

it sounds like there was a timeout with detecting the new version— which is likely a wifi/internet issue. if this happens in the future, try rebooting.

but what follows with the terminal business— did you shell in and run the norns update.sh manually?? from the norns folder? this is absolutely not good and should not be done (there are no instructions anywhere suggesting doing this, i hope). while this process should fail— i wouldn’t have expected it to brick your OS (though i haven’t looked, it very well may).

#15

Yeah, based on what I’m seeing and reading here, there was some sort of issue with the internet connection and the update process. It was odd because I was able to connect to Norns via wifi and the system status showed wifi was working.

I did ssh into Norns and manually ran update.sh. The reason behind this is because when I had Norns in the past, that was the update process if I recall. Took a break from things and it seems they are a little different now, so I won’t dare do that again…eek. I’m in good shape though now after reflashing and running update via the Norns menu. It didn’t take me long to get up and running again and to my surprise, a lot of the scripts I use were part of the image. :+1:

Sorry to cloud the thread, but hopefully someone benefits from the odd things that happened and just restarts their Norns if updates don’t seem to start. :slight_smile:

#16

glad it worked out and thanks for the heads up— it gives reason to clarify the purpose of some files in the repo, along with adding some timeouts if the wifi github query isn’t working.

#17

Does this fix the jumpy encoders?

#18

nothing in software is going to fully fix jumpy encoders. you probably need to replace the encoders

#19

Ok. I’ll send it back cause right now it’s unusable.

#20

This update on a DIY shield went well here. Got it trough on the second go. Thanks!

#21

Works on my norns shield and no issues with my script “pixels” as of yet.

1 Like
#22

Hi all!

I hadn’t used my norns shield in a while and decided to check out some of the new scripts.
I checked if there were any updates and there was one so I updated the norns and ran a few scripts.

It may be a coincidence, but after this update, the norns won’t turn on! There’s a red light on the rPi, but I can’t see the norns on the network.

Is there anything I should be doing? Is there any way to do a full reset and get it back running?

Thanks in advance!

#23

see the install instructions for full reset

do you recall what version you were on previously? did the process complete?

#24

Thanks! I’ll have a look at these instructions and report back!

Can’t remember which version I was coming from and the process did complete as I tested a few scripts before being “locked out”.

#25

Apparently it was an SD card problem!
Was having error messages while flashing the drive and tried a different card and it booted up just fine!

Thanks @tehn !

#26

sadly SD card quality is a tricky of failure— glad you had a another to test!

1 Like
#27

FYI in this update, it seems the screen levels have been tweaked to be 0-15, to match grid messages i guess. Previously, screen.level(16) set max brightness on a pixel.

1 Like