use SYSTEM > UPDATE while connected to the internet
if you have not yet fresh-installed norns: new image 220306, you will not be able to complete this update – maiden will alert you that a new image is necessary and you will see that your version number hasn’t changed on the SELECT / SYSTEM / SLEEP screen.
mega call out of gratitude to @markeats + @Justmat for laying out a brilliant framework with their LFO libraries (changes and hnds, respectively), which was a massive help in filling out the maths and seeing the paths forward.
I keep getting a “disk full. needs 400M” message.
I’ve never seen this before, and it’s a bit stranger now because after wiping the drive for the last update I’m guessing I’ve never had more free space. Any ideas?
even if this is a 4gb norns, you should have about 1gb of free space after a clean install.
the extending storage info linked above should help – extending storage is applicable to both standard norns and shields, which i’ll make clearer in those docs!
Everything else is fine. I think the issue is on my side tbh.
I’m trying to connect/work on norns from my fedora OS day job machine. Previously, I used a busted old windows machine for music/norns stuff and that worked fine. Now, I get lots of the these network errors and a lot of lag on the ssh connection
ah! good that the callback is working as expected from the menu, thank you for the follow-up!
in thinking back on this feature, i remembered that it was implemented with the assumption that the most useful case where a script author would want the PSET number to get passed to their params.action_read function is when another (non-scripting) user of their script would load a PSET via the menu, which passes a numeric value for the loaded PSET slot to params:read, where it is wrapped up as the pset_number. this is the workflow that’s outlined in the extended reference: params | monome/docs
for scripting PSET reads (independent of the menu-based workflow), you should be able to get things groovin’ by using the alternative number argument outlined in the API, rather than the absolute path.
eg. params:read(1) should get your _path.data.."timber/player/player-01.pset" PSET loaded and the pset_number sent back. this is of course assuming you’re scripting within the timber player script, rather than referencing PSETs for one script from another. if the latter is the case, and managing the awareness of the coded PSET reference from the code that’s calling the PSET doesn’t feel workable, then it’d be rad to learn a bit more about your use case!
Thank you @dan_derks ! That make sense and I wasn’t aware that it should work as intended and I stored pset number globally so it works for me now. params:read(1) will simplify a lot, thanks for the tip!
In my use case I am trying to map midi button to switch to the next defined pset and I need to reset all samples by loading first pset first to clear all samples then load defined pset because of the timber bug that can’t sometimes properly load pset one after another.
I am also getting a lot of warnings with this update in Timber that wasn’t before and I can’t find initial logs because it keeps printing for couple seconds and erases old messages in Maiden:
! stealing separator ID <Amp Env> from earlier separator
! stealing separator ID <Mod Env> from earlier separator
! stealing separator ID <LFO Fade> from earlier separator
ah, yes! these messages are benign (eg. won’t affect usability unless one tries to programmatically hide/show any of these colliding separators), but since all parameters now have ID’s (including separators and groups), these informational messages will print if a script does not differentiate separator IDs from one another – separators and groups now have IDs to facilitate hiding/showing in the params UI menu.
i’ll take a look at timber this week and push a PR to give each a unique ID.
yes, absolutely – all norns updates are for both standard units and shields, though you will need to make sure that you’re on version 220306 (which is 2022 March 6th) or later in order to perform the update. see this note for additional details:
Today I’ve updated my norns shield to 220802 and now it won’t start up. The red and green lights are on while turning it on, but after a minute or so it’s only the red light and still nothing on the screen after half an hour. What to do?