#43

that would be rad!!!

1 Like
#44

Happy to contribute some loops! Dm me if you’d like some stuff :slight_smile:

8 Likes
#45

^ doooo iiiiiit. @vcvcvc_val’s tunes are the fantastic!! ^

2 Likes
#46

me and @vcvcvc_val are cooking up some loops. in the meanwhile, I’ve made a small update that auto-creates the beets audio directory and copies a basic Amen loop in there to play with.

8 Likes
#47

This is really cool after getting some loops loaded into the folder. Tempo control from the main interface would be a nice addition or potentially in increments from some of the unused grid buttons maybe. Also would be extremely cool for each loop that is loaded to retain each of their commands. Nice work. Also not sure if this is a system type bug/issue but when I was running the script and told Norns to change the grid orientation, it left all the led lights still lit at the old rotation.

2 Likes
#48

Thanks for the bug report (now fixed in the latest code commit) and some good suggestions. Interesting thought about making the settings retained per-loop… the main reason that they’re global across loops right now is to preserve the possibility of controlling it entirely through params (and hence using MIDI controller mapping) for those without a Grid.

3 Likes
#49

20 characters of great 1.0!

1 Like
#50

Just loaded a couple of one bar loops, and it seems like now beat 1 of the loop is on step 8 of the top row. Do I need to somehow set where beat 1 is for loaded loops? I also plugged my arc in and see that encoders 1 and 2 have a sort of time division thing going on, but only as a display. Is this intended? Made me think of how cool it would be to maybe have filter and cutoff of each loop on an arc knob…

Edit: I should note that everything is happening at the correct timing in terms of when the loop restarts on the one, but the one visually is pad 8 in the top row.

#51

That is odd, and definitely not expected behavior. The code should load each loop and fit it to the current BPM starting at beat 1 no matter what. Would you be able to message me one of the loop files you’re using, just in case I missed something in the file loading code?

#52

My selfish reason for suggesting settings per loop is probably because my first use case was taking a 4 bar loop and chopping it into 4 pieces and then loading it into beets. It was fun playing around with it like this

#53

As for Arc, I just got my Arc a week ago and I’m figuring out how to incorporate it. I threw in a quick visualizer to see how it feels, and I also thought about just plugging in Arcify so you can make your own param mappings. Something for a future release.

2 Likes
#54

finally getting a chance to try out this script…

think i need a little help.
:stuck_out_tongue:

all i get is a display message that says LOAD LOOPS IN PARAMETERS

when i go to Param page…

i see the Loops folder and next to it is the 5th loop i have in the folder.
if i highlight that and hit Button 3 nothing happens.

if i highlight Load loops…a little square blinks

if i go back to the script main page i just get the LOAD LOOPS IN PARAMETERS message.

i’m on the latest OS and i even uninstalled and re-installed Beets as well as a restart from SLEEP…

oh yeah…
the GRID does not activate but the first two knobs of ARC do…one moving in blocks and the other just sits there.

#55

It seems like the folder layout I chose is kinda confusing and hard to explain… can you check if this is how you’ve copied the files over:

Directly inside the folder dust/audio/beets there should be no files, only folders. You make one folder there for each set of loops you want to load together. Inside each folder, you put some loop WAVs. Then when you run the script, it’ll list each folder (not each file) in the “Loops folder” param. When you choose one and load it, it loads each wav file from inside that folder into loop slots one, two, three etc… then the grid lights up and starts listening to your commands.

image

Also I should remove the Arc code, it was just there to try out some visualizations for a later feature. It’s confusing for people with Arcs when it doesn’t do anything useful.

3 Likes
#56

AHHHH!!!

AWESOME!

by all that is un-holy…FRACKEN AMAZING!

thank you!!!

i loaded up some loops a slammed out on the kit, some Taiko and a Pandeiro lick.

WOW!!!
it gets really crazy when it’s switching between completely musically divergent styles.

thanks again for the help!!!

2 Likes
#57

so Beets became the star of tonight’s broadcast…
:stuck_out_tongue:
this is a set of 8 loops i made a very long time ago on Nanoloop.
also using Cheat Codes and Vorpal from the NC-01 project with a NAVA extra 9.

4 Likes
#58

As of today, if you install Beets from scratch then it’ll copy over a fantastic new set of demo loops created by @vcvcvc_val so that you can get jamming right away. You can find them in https://github.com/mattb/beets/tree/master/demo-loops/demo-beets if you’ve already installed and need to copy the folder over manually into dust/audio/beets.

Here’s a snippet from some happy jamming times I had this evening using the loops:

13 Likes
#59

Great video. Groovy! Is the delay coming from your modular? So I just updated everything. Love the unmentioned addition of arc mapping. Outstanding. But I’m still getting the “beat 1 on pad 8” issue. And unless I’m just crazy and feeling the beat an 1/8 note off, it looks like the 1 in beets is also on pad 8 in your video. And please excuse my stream of questions, but I have a couple more. So on the edit screen, the display seems to show voice 1. Is there a way to show voice 2? And when editing each of the 8 step squares, what is the difference between a blank square, K, and S? I’m not hearing any difference between the three settings. Thanks for your ongoing work on this! And thanks to @vcvcvc_val for the great beats!

1 Like
#60

In the video, the modular is making the bleeps (clocked from Beets by Crow into Ansible) and the delay is on an iPad running AUM with the K7D delay.

The edit mode is part of the unfinished/undocumented additional Crow support. The idea is that you can mark the slices of each loop that contain a kick (K) or a snare (S). Then whenever they play, a Crow output fires a trigger. If I remember correctly, I use this in the demo video to spike the filter frequency on the snare beats. Previously I’ve used it to fire a deep analog kick to beef up the kicks in a loop.

Please keep the questions coming! I’ve got a busy week at work but this weekend I will try to load up some very simple loops and nail down the timing issue.

5 Likes
#61

Ah, K and S for Crow. Love it! I’ll have to give this a try. Thanks!

#62

To enable the outputs in the current code, you’ll need to set ENABLE_CROW = true here: https://github.com/mattb/beets/blob/master/beets.lua#L17

I had to disable them to make sure they didn’t stomp over the new Crow output options in the global clock. I need to make the choice of output configurable before I can publish the feature.

2 Likes