#141

Any idea why I would still be getting this error: init? System is up to date.

1 Like
#142

can you try loading another script first after restarting and then load oooooo?

1 Like
#143

Same error, I tried resetting and sleep a few times. Also removed and reinstalled OOOOOO in maiden. No idea, but bummed bc I love this script!

1 Like
#144

are you able to ssh into your norns? my only guess at this point is that maybe you have a parameter file that is bugging out (somehow?). if you can ssh you can remove the possible parameter files with

> rm -rf ~/dust/data/oooooo
#145

So… huge caveat that I have no idea what I’m doing but have so far been able to follow directions with stuff like this. I used cyberduck to ssh into the norns, and somehow managed to delete everything in the dust/data/oooooo folder. I uninstalled and reinstalled it from maiden and am now getting a “supercollidor error”. Any ideas? Do I have to wipe the drive and start over?

Honestly I love the norns but not being a coder or that comfortable with this stuff makes me question how much time I spend troubleshooting.

1 Like
#146

sorry to hear about the trouble!

in the maiden REPL, there’s an sc (supercollider) tab which will print some specifics about the error:

image
image1475×940 68.5 KB

if you can share any messages that are printing there as well as in the matron tab when you’re loading the script, that’ll tell us a bit more about what’s happening and how to solve it :slight_smile:

1 Like
#147

Well last night I reset and also put it to sleep and restarted, same supercollider error. Today it launched the script no problem. No idea but seems to have fixed itself.

Here’s the SC messages from just now:

free engine: an Engine_None
CroneEngine.free
a CroneAudioContext

– crone: done loading engine, starting reports

engine: an Engine_None
cpu_peak
cpu_avg
amp_in_l
amp_in_r
amp_out_l
amp_out_r
pitch_in_l
pitch_in_r
starting poll…

And the Matron tab:

script load: /home/we/dust/code/oooooo/oooooo.lua

cleanup

script clear

pset >> write: /home/we/dust/data/system.pset

script run

reading PMAP /home/we/dust/data/oooooo/oooooo.pmap
m.read: /home/we/dust/data/oooooo/oooooo.pmap not read.
Engine.register_commands; count: 0
___ engine commands ___
___ 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

pset >> read: /home/we/dust/data/oooooo/oooooo.pset
pset :: /home/we/dust/data/oooooo/oooooo.pset not read.
initializing 1
initializing 2
initializing 3
initializing 4
initializing 5
initializing 6
initializing 7
tape+adc only

#148

ah, cool! i’m glad it resolved itself – if you ever run into that trouble again, those two tabs will have everything someone would need to troubleshoot. enjoy oooooo!

2 Likes
#149

Thanks so much, super helpful to know.

2 Likes
#150

hi, loving this script so much - it’s genius! Would there be any chance of each tape having its own dedicated filter at all? Similar to cheat codes - would be awesome to have slow moving filters if its possible/not too complex. thanks!

4 Likes
#151

@jhyde i like that idea! i can definitely add filters to the voice menus. i’d also like to add this to barcode.

what are good defaults for filter modulation? i’d like to always have a nice set of defaults in these scripts. namely i’d like to know what might be considered “cool” sounding when choosing a combination of:

  • filter type (low/high/band-pass)?
  • modulation speed (slow/fast)?
  • modulation type (sine/triangle)?
  • cut-off frequency range?
  • wet/dry ratio?
3 Likes
#152

great yeah those defaults sound perfect! So I use the filter on this Max for live device called Dekoboko FX which does all those things and also has a sequencer (not suggesting to include that), but currently its at the end of the chain on all the loops going into ableton, hence thinking of independent filters. I mostly mess with the wet/dry, freq, res and mod speed. Here’s the device;

thanks!

2 Likes
#153

Hi there.
Please Is it possible to save the loops that we recording in the Oooooo ?
And with the Presets ?

it might be cool if the loops are automatically saved to the oooooo file

2 Likes
#154

To save, simply scroll through tapes until you reach “A,” turn E2 until you reach save, and press K3.

6 Likes
#155

WoW thank you a lot :pray:
Now I am feeling so anxious because I lost some nice work :grimacing:.
It was ridiculously simple. I don’t think about find it in the A section.
Thanks again :smiley:

2 Likes
#156

A futur feature with saving all 6 loops will so perfect :ok_hand:

1 Like
#157

The method above saves all 6 tapes and their parameters!

2 Likes
#158

Ok sorry I was testing and not understand correctly. So now I have it.
Thank you :blush:

1 Like
#159

Hello. I would like reset the « factory » startup but without delete my presets with loops.
Please which files I have to replace ?

#160

Love this. Not sure if I’m missing something. MIDI mapping, is this possible for vol / pan of the individual 'o’s? The option is not in my mappable params.
I can see a demo of @Blit playing with 16n as a controller for volume but also reports that this might be a future implementation. Tried to hack the code myself but ended up with a script that did not load. :confused:

1 Like