Oooooo

infinitedigits · 2020-11-28T21:49:54.671Z

vehka:

Can’t see them in the params menu

are you on the latest version of norns too? could you try doing a system -> update? the new trigs require the latest version i think.

vehka:

would it be possible to modify the script to accept MIDI input from more than one MIDI interface? I’ve been using a Faderfox UC3 to control the script, but now that rec triggering is happening, I’d love to use a MIDI footswitch for that.

i’m not sure! if you find out please let me know

dtm · 2020-11-28T22:00:48.756Z

Yes, I meant can we’ load arbitrary wave file into a loop’. Thanks so much for clarifying!

888m · 2020-11-29T01:30:17.645Z

cranking the vol pinch param definitely makes it easier for me if i can’t manually mess around with the stop/start points, but @infinitedigits do you think it’d ever be possible to let the beginnings/ends of loops crossfade into each other?

encephalitislethargi · 2020-11-29T02:27:41.751Z

This is incredible, thanks so much

vehka · 2020-11-29T13:00:15.886Z

Yeah, there was a norns update I had missed, the params menu works now. Sorry about that. Also, multiple MIDI devices seem to work now!

terje · 2020-11-29T17:58:47.196Z

This is so great! The way this works really clicked with me and I’m looking forward to further explorations.

https://www.instagram.com/p/CIK6NMBJF_E/

mbillz · 2020-11-29T20:02:05.727Z

@infinitedigits have you made any progress on the Grid / Arc implementations or have any specific UX ideas about how you want those implemented? I don’t have any MIDI controllers hooked up to my Norns so I’d love some more tacticle control over the loops. I’d be interested in helping you implement that functionality if you’re still looking for help!

infinitedigits · 2020-11-29T20:32:19.198Z

@terje absolutely beautiful looping! thanks for sharing.

@mbillz no progress on grid or arc, nor plans to make implementation. at this point i would love to offload it to someone! if you’d like to work on it i will support your effort 100%. feel free to implement it in any way you’d like. i can give you rundown of the codebase and answer any questions you have, just lmk!

mbillz · 2020-11-29T20:48:46.541Z

Sounds good! Let me marinate on the UX over the next week and I’ll DM you when I’ve got some ideas.

mattlowery · 2020-11-30T01:00:14.137Z

Ok. I’m in.

https://www.instagram.com/p/CIMQ1SRh7ml/?igshid=11vofwe573jlq

encephalitislethargi · 2020-11-30T14:28:45.201Z

priming and recording midi mapping works great. I was wondering if you would be able to suggest a practical mapping layout for the nanokontrol2

image750×231 32.3 KB

so far, i have the length of each loop mapped to knobs 1-6, the rate of each loop mapped to faders 1-6, the volume of 1-2 on knobs 7&8, volume for 3-4 on faders 7&8.
i have “Recording Trig” of each track mapped to “R” on 1-6(which is probably not necessary since “arm” seems to do the trick itself), and “Arming Trig” to “S” on 1-6.

I realize im still going to have to use the norns controls for some things if i want to really use it as intended, but i’m hoping at least for now, i can set up a simple:

select a track 1-6
arm a track 1-6
adjust length on each track
mess with rate & volume for each track (unless there is a more useful parameter you think i might be using)
All without touching the norns

is that possible? I can’t figure out if there is a midi mapping parameter for “track select”, and “arming trig” for a specific track doesn’t select that track, it just arms whichever track is currently already selected

i’m sorry to ask for more features after you’ve been so gracious with fulfilling all of these other very useful requests. but maybe there’s something already in place that i am missing?

infinitedigits · 2020-11-30T14:52:21.304Z

your use of nanokontrol is excellent! wow, mapping the lengths and rates too! i’ve never tried that, should make for a lot of cool possibilities.

encephalitislethargi:

“arming trig” for a specific track doesn’t select that track, it just arms whichever track is currently already selected

are you on the latest version? the latest version is correctly arming the whichever track it is triggered for.

encephalitislethargi:

a midi mapping parameter for “track select”

there is no parameter for track select because essentially there is no track select. the track selection (highlighting the loop) just enables you to modulate parameters from the main screen and thus is only available at the main screen. however, all those modulations are available via the parameters menu (the ones that are midi mappable) so by mapping parameters you can affect every track even though it is not selected on the main screen.

if i misinterpreted your question/intension, please don’t hesitate to lmk

encephalitislethargi · 2020-11-30T15:06:46.469Z

oh, you’re right. sorry, i thought it was arming the loop i was on because when i would arm loop “3”, the main screen still had “1” displayed at the top, but it would still record to loop 3. so you’re right, there doesn’t seem to be a need to select a track/loop

thanks for clarifying. this rules, by the way. thanks again for all of your work here

kingmetal · 2020-12-02T06:50:25.058Z

This is such a cool tool - I am a sucker for a flexible looper and this is that in spades.

If you’re ever looking for new ideas, I’ve recently gotten really fascinated by multi-track loopers that use the first recorded loop to sync all subsequent loops. A really fantastic example of this is Christopher H. M. Jacques’ Loop Sync patch for the Zoia. The first loop sets the length and all other loops are a ratio of the first loop.

Punching out of the loop recording in oooooo modifies the loop length, so just starting with a long loop lets me make an unquantized loop (and I can sync the loops) but it would be incredible if there was an option to copy the loop length of loop 1 (or 6, whatever should be “first”) to the next loop in the chain.

Supporting sync’d loops that were longer than the original loop would be tricky. I guess in that case you’d avoid copying the loop length to the next loop but if the user punched out before the end of the first loop it would pad the end of the loop and if the user punched out after the end of the first loop you’d just pad the loop by some ratio (2x length).

Just spitballing. Thanks for your incredible work!

infinitedigits · 2020-12-04T15:56:43.344Z

v1.3.0 - share and collaborate.

new feature: add sharing (via SHARE global parameter) through norns.online/share. upload and download oooooo saves from anyone in the world. requires installing norns.online script.
new feature: load loops from audio (via loop X -> load audio). loop will be set to length of audio. (thanks @dtm for this idea)
new feature: infinite saves (you specify the name) via save/load parameters
new feature: sync all loop lengths to first loop (after recording first loop) (thanks @kingmetal for the idea though not exactly what you mentioend)
bug fix: not recording multiple loops, add sync to first loop
ux: some parameters moved to all loops

note: to use the sharing you also need to install norns.online script. but if you don’t have norns.online, you can still update and use all the other features. the sharing has a lot of moving parts (~2000+ lines of code) and while i tested very thoroughly, some bugs may have fallen through the cracks. please don’t hesitate to lmk if you find a bug.

kingmetal · 2020-12-04T19:55:22.898Z

I can’t wait to play with this! Thank you so much @infinitedigits

Mad86 · 2020-12-04T20:51:56.269Z

Wowowo
@infinitedigits thank you a lot
I wish you a nice weekend

kingmetal · 2020-12-05T00:28:17.251Z

Spent less than 15 minutes playing with loop length sync and my initial impression is:

“Oh no, now I’m going to need to buy a mixer.” This is basically the highest praise I can give.

I’d been using Foulplay as the drum machine in my chain and Loop Sync on my Zoia. I think oooooo just became my primary looper, so now I need to bite the bullet and get a mixer since I don’t want to loop my drum machine (a Volca Sample currently).

Actually, I could probably just edit this line: https://github.com/schollz/oooooo/blob/bb61a00f4d687f5832e53e2c414929de3234dad8/oooooo.lua#L405 and only pull input from one of the input jacks and just monitor in mono mode. Maybe I’ll make my first PR against oooooo if I can figure out how to add input L, Input R and Input L + R to the options menu!

infinitedigits · 2020-12-05T01:13:19.538Z

kingmetal:

now I’m going to need to buy a mixer.” This is basically the highest praise I can give.

lol i know what you mean, and thank you

i really encourage you to make a pr! i’m totally open to making this a collaborative script.

for your changes, you can change this option to use line-in stereo, line-in l, line-in r:

github.com

schollz/oooooo/blob/bb61a00f4d687f5832e53e2c414929de3234dad8/oooooo.lua#L114


params:add_control("rec level","rec level",controlspec.new(0,1,"lin",0.01,1,"",0.01))
params:set_action("rec level",update_parameters)
params:add_control("rec thresh","rec thresh",controlspec.new(1,100,'exp',1,10,'amp/1k'))
params:set_action("rec thresh",update_parameters)
params:add_control("vol pinch","vol pinch",controlspec.new(0,1000,'lin',1,500,'ms'))
params:set_action("vol pinch",update_parameters)
params:add_option("rec thru loops","rec thru loops",{"no","yes"},1)
params:set_action("rec thru loops",update_parameters)
params:add_control("stop rec after","stop rec after",controlspec.new(1,64,"lin",1,1,"loops"))
params:set_action("stop rec after",update_parameters)
params:add_option("input type","input type",{"line-in","tape","line-in+tape"},3)
params:set_action("input type",function(x)
  update_softcut_input()
  update_parameters()
end)
params:add_option("sync lengths to first","sync lengths to first",{"no","yes"},1)
params:set_action("sync lengths to first",update_parameters)
params:add_group("save/load",3)
params:add_text('save_name',"save as...","")
params:set_action("save_name",function(y)

and then move these lines:

github.com

schollz/oooooo/blob/bb61a00f4d687f5832e53e2c414929de3234dad8/oooooo.lua#L404-L405


softcut.level_input_cut(1,i,1)
softcut.level_input_cut(2,i,1)

into the update_softcut_input() function (putting them in a for loop for each of six loops!).

if you need help at any step, whether it be git, command-line stuff, lua, or oooooo lmk and i’ll help.

kingmetal · 2020-12-05T03:17:45.659Z

Got reasonably far, but of course I tried to get fancy and also figure out how to change the input that triggers input recording and that’s where I’m having trouble.

github.com

luciusbono/oooooo/blob/06cb68ddffd24eb178a0a29a9c7068c22898409a/oooooo.lua#L486


    params:set(i.."vol lfo amp",math.random()*0.25+0.1)
    params:set(i.."pan lfo amp",math.random()*0.6+0.2)
    params:set(i.."pan lfo period",round_time_to_nearest_beat(math.random()*20+2))
    params:set(i.."pan lfo offset",round_time_to_nearest_beat(math.random()*60))
  end
end
--
-- updaters
--
function update_softcut_input()  
    if params:get("input type")==1 then
      p_amp_in=poll.set("amp_in_l")
      print("listening on input 1")
      for i=1,6 do
        print("input L only channel "..i)
        softcut.level_input_cut(1,i,1)
        softcut.level_input_cut(2,i,0)
        audio.level_adc_cut(1)
        audio.level_tape_cut(0)
      end

I moved setting the p_amp_in variable into the update_softcut_input function and and tried returning the value of p_amp_in so that it can be where you were setting it previously:

github.com

luciusbono/oooooo/blob/06cb68ddffd24eb178a0a29a9c7068c22898409a/oooooo.lua#L295


timer.count=-1
timer.event=update_timer
timer:start()
-- position poll
softcut.event_phase(update_positions)
softcut.poll_start_phase()
-- call update_softcut_input to set polling input
p_amp_in = update_softcut_input()
-- set period low when primed, default 1 second
p_amp_in.time=1
p_amp_in.callback=function(val)
  for i=1,6 do
    if uS.recording[i]==1 then
      -- print("incoming signal = "..val)
      if val>params:get("rec thresh")/1000 then
        tape_rec(i)
      end

But this is clearly the wrong way to do it. It does work if you re-init the script but I’d like it to switch dynamically. I’ll take a break and poke at it some more later tonight - this has been fun! If I really figure it out I may rewrite the polling mechanism to allow for two channel polling since I could see some edge cases where that might be helpful, but that’s getting way ahead of myself.

Obviously I will happily conform to whatever interface standards you want to maintain so none of the settings names here are permanent.