EDIT: ok - just read i need to re-flash my norns to be able to update this way. Thought i was on a later version than that.
ok thats odd - its saying i am on 210607. So that seems to be the problem.
I go to update on the norns itself and it goes through the various screens and seems successful finishing with the power off phase, but its obviously not installing.
It there another way to update without a full re-install?
2 Likes
xmacex
580
Yes that’s right, some milestone updates require a full wipe and reinstall. Enjoy the fresh noooooorns once you are done 
2 Likes
joshhh
581
I’ve been having a recurring issue where loop 1 will get “stuck” on 100% playback rate. the rate (%) in the parameters menu will change based on MIDI/encoder input, but the actual playback rate remains the same. when turning E3 on the main playback rate screen the actual and displayed rate remain stuck on 100%. toggling reverse still works.
I’ve only had this happen on loop 1 so far, and I haven’t figured out what could be causing it. has anyone else seen this / is there anything I should look for to help debug? the only remedy I’ve found is creating a new preset, which then sometimes runs into this same issue.
also, is it normal to be able to extend loop lengths beyond the length of a loaded file? when this happens it seems like I sometimes get silence but other times will start getting playback of other (previously loaded?) files.
1 Like
can you look to the maiden output to see if any errors are spewing? this sounds like strange behavior for sure! sorry that it bit you.
this is normal! the loop is like a big tape, so if you load something into it, and then load another thing into it that is shorter, it will still have the material from the first thing on the outer edges. you can reset loops though which should clear all the audio in that part of the buffer.
3 Likes
my norns fates wont load “oooooo”.
it shows the script in the select menue but after loading thru the select menue “error: load fail” come up
i updated also the os today and also the script is fresh loaded but wont change…
any idea?
xmacex
584
Woopsie, what output do you find in Maiden? That usually helps figuring out what is going on. You can copy+paste here in a reply, preferably preceded and followed by ``` so it’ll be easier to read
here we go:
# script clear
pset last used: 1
including /home/we/dust/code/oooooo/lib/grido.lua
including /home/we/dust/code/oooooo/lib/json.lua
including /home/we/dust/code/oooooo/lib/glyphs.lua
including /home/we/dust/code/oooooo/lib/json.lua
including /home/we/dust/code/oooooo/lib/monosong.lua
including /home/we/dust/code/oooooo/lib/table_addons.lua
including /home/we/dust/code/oooooo/lib/lattice.lua
### SCRIPT ERROR: load fail
/home/we/dust/code/oooooo/lib/monosong.lua:4: module 'sequins' not found:
no field package.preload['sequins']
no file '/home/we/norns/lua/sequins.lua'
no file '/home/we/norns/lua/core/sequins.lua'
no file '/home/we/norns/lua/core/params/sequins.lua'
no file '/home/we/norns/lua/lib/sequins.lua'
no file '/home/we/norns/lua/softcut/sequins.lua'
no file '/home/we/dust/code/sequins.lua'
no file '/usr/local/share/lua/5.3/sequins.lua'
no file '/usr/local/share/lua/5.3/sequins/init.lua'
no file '/usr/local/lib/lua/5.3/sequins.lua'
no file '/usr/local/lib/lua/5.3/sequins/init.lua'
no file '/usr/share/lua/5.3/sequins.lua'
no file '/usr/share/lua/5.3/sequins/init.lua'
no file './sequins.lua'
no file './sequins/init.lua'
no file '/usr/local/lib/lua/5.3/sequins.so'
no file '/usr/lib/arm-linux-gnueabihf/lua/5.3/sequins.so'
no file '/usr/lib/lua/5.3/sequins.so'
no file '/usr/local/lib/lua/5.3/loadall.so'
no file './sequins.so'
stack traceback:
/home/we/norns/lua/core/norns.lua:144: in function </home/we/norns/lua/core/norns.lua:144>
[C]: in function 'require'
/home/we/dust/code/oooooo/lib/monosong.lua:4: in main chunk
[C]: in function 'dofile'
/home/we/norns/lua/core/startup.lua:43: in function 'include'
/home/we/dust/code/oooooo/oooooo.lua:29: in main chunk
[C]: in function 'dofile'
/home/we/norns/lua/core/script.lua:186: in function </home/we/norns/lua/core/script.lua:186>
[C]: in function 'xpcall'
/home/we/norns/lua/core/norns.lua:145: in field 'try'
/home/we/norns/lua/core/script.lua:186: in function 'core/script.load'
/home/we/norns/lua/core/menu/preview.lua:23: in function 'core/menu/preview.key'
/home/we/norns/lua/core/menu.lua:140: in function </home/we/norns/lua/core/menu.lua:117>
# script clear
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'
xmacex
586
Perfect, thank you. I suspect your norns needs system update to the latest version, since it seems to be missing the sequins library oooooo uses.
On the SYSTEM screen you can see which version you are running. What’s the six-digit number? You can scroll upwards this thread a little bit, other artists seems to have had similar issue on 2023-07-14, and in July and March 2022.
Having all discussion relating to a script in a single thread is super useful feature how we organize this forum, and checking out threads is often a good idea not only for installation problem solving, but I have learned sooooo much about just the functionality of the various scripts by checking out discussion Also great source of musical inspiration!
Was noodling and un-thoughtfully activated the chord layering which completely wrecked the mood I carefully had set up… but because of how there is stuff composting in the recycled buffers for something totally amazing! oooooo really is one of these happy accident scripts.
(Samples from Studio Eksperymentalne Polskiego Radia (PRES))
7 Likes
thank you for the quick reply and help!
problem was:
fates has another image than the shield!
ooooo works perfect!
thanks again
2 Likes
xmacex
588
Happy to hear it, well done sorting it oooooout.
2 Likes
Hi! I have a working fates for 4 years now, and oooooo is working properly on it. Now I also have a working shield with 210330 codec PCB, system currently is 220306 (can’t update for some reason). So the problem is that if I load any sample to any of the reels in oooooo, a horrific white noise (like an infinite feedback loop) comes in, and even if I switch to any other script, it is still there. The only way it stops is if I send the norns to sleep. Any ideas why this is happenning?
Thank you! It was the case with the Fates, so I reflashed it, but I thought with the shield it is doable from within the system. But will try it. However I am not sure the problem with oooooo is because of that.
1 Like
We’ve fixed a couple problems over the years that would occasionally cause this on some systems. Updating is absolutely necessary.
2 Likes
You are one of us. You are welcome.
Bit more live OOOOOO from my first time ever using it. This was two small mics hanging inside either side of a very broken piano, with a marble rollercoaster running on top of it and a solenoid firing inside the piano, hitting a set of keys dangling in front of the strings
5 Likes
Hey everyone,
I’m fully engaged with this script. I apologize if this question has been addressed previously, but is there a method to adjust the default loop length to, for example, 20 seconds collectively without the need to modify each one separately? Additionally, I’m curious if it’s possible to alter the loop duration using the grid within the 4.47-second range?
Thank you!
1 Like
yes! goto PARAMETERS -> EDIT -> startup -> start length -> 20 beats and then simply set the BPM to 60 so that you have 20 seconds in each when you startup the script.
7 Likes
Brilliant! Thanks so much for the help 
1 Like
