#81

Compass 2.0!

This upgrade introduces crow support.

  • Compass’ command sequence can now be driven either by the default internal clock or by crow! Head to params to chose between the two. If clocking w/ crow, send your trigger to input 1. See the clock section of the docs for more info.
  • :warning: EXPERIMENTAL FEATURE: Crow’s input 2 is configurable via the params menu. When enabled, you can use it to control either softcut’s level or its rate (both voices). See the crow section of the docs for more info.

With crow support comes two new commands that can be fired from your sequence:

  • T sends a pulse from crow output 1
  • V sends a random voltage (0v-10v) from crow output 2

Tip: If Compass has a hard time detecting your crow, try simply re-launching the script.

Changes

The + and - commands have been modified – these no longer increment and decrement softcut’s rate. Instead:

+ : Sets a random positive rate (0.5x to 2x)
- : Sets a random negative (reverse) rate (-2x to -0.5x)

This will hopefully reduce some jagged cuts/clicks when rapidly jumping from a positive to a negative rate. Note than you can still use ! for that :slight_smile:

There’s a lot of new stuff in here, and though I did some thorough testing, weirdness may certainly come up. Please let me know if you encounter anything, and have fun!

17 Likes
#82

This is awesome! Cant wait to load it up

1 Like
#83

So excited to see crow’s inputs starting to be used.

1 Like
#84

Honestly - it’s a small miracle being able to re-configure a hardware jack in software on the fly!

5 Likes
#85

Here’s a question/idea/suggestion(?) @Olivier:

The external clock moves the command sequence along right?

I had this thought about Compass a few times and I’m not sure if its even possible to be honest…
If Compass was clocked by external/or internal BPM to create a perfect looping sequence? So I guess depending on the tempo the 64s buffer would have to potentially be shortened, right? And then the commands would be derived from that tempo or a clock division. Not sure if this makes sense or not, but this is also starting to sound like a new script separate from Compass. Sorry for the brain dump, would love to hear your thoughts. (I don’t want this to stray away from your initial concept in anyway)

Edit: This thought came to mind a few times while I’ve played more planned material live into compass while listening to a click track.

1 Like
#86

@ludvista29 - definitely something to think on. I don’t think Compass’ forte will ever really be synced material, but there are certainly things I could look at implementing to get partway there.

Even without an external clock, you can achieve syncing (kind of) by placing a 1 command in your sequence, which will make the play/record heads jump back to the start of your loop. This way, you can loop within a shorter section of the 64s buffer.

The length of your loop would of course be dictated by the length of your command sequence and by the speed of the internal clock, the latter of which I could maybe look at exposing as a param option.

I think this is where things could get tricky, with the commands not being able to keep up with the incoming clock if rapid/random changes are happening. Most likely a solvable solution, but probably not one I’d tackle in the near future.

Anywho – thanks for the suggestion!

2 Likes
#87

I appreciate you thinking about my little brain dump I just had!

This little tip is super useful and may give me some more control, so thank you for that :slight_smile:

Also, I hope you did not take my suggestions in the wrong way, I absolutely love the script but selfishly had some ideas that would maybe better fit my workflow. Can’t wait to try this with crow when I get my hands on one!

1 Like
#88

Absolutely not :slight_smile: I really appreciate any and all ideas, truly. Even if I don’t necessarily implement them, they broaden my understanding of various workflows and often influence other ideas.

2 Likes
#89

so did the Arc integration get removed?

i did have some serious problems with controllers not being recognized by norns a few days ago but the peeps on the MANGL thread got me sorted.

however, i wasn’t able to get the ARC to light up or connect while using COMPASS.

thanks for any help!

#90

Paging @GoneCaving as I didn’t implement arcify myself, nor do I have an arc to test with :frowning:

1 Like
#91

Nope, it’s still working fine for me. Make sure the Arc appears in the first slot under System->Devices->Arc, and set the Loop Start/End to Arc rings under the params page (those are the only params with arcify control enabled).

3 Likes
#92

Oh man… so far I’ve been mainly using Compass a lot to process my own sounds (which sounds great!), but last night I tested it with a violin player friend of mine and we went deep into some new unexplored territories. We’ve got a improvised opening performance coming up at a film festival, in which I’ll be mainly handling Compass + Crow/JF material, so this started off very promisingly.

5 Likes
#93

Rings into Clouds into Compass is the new Rings into Clouds

3 Likes
#94

This is beautiful, @yobink, and sets the perfect mood for the gray day we’re having here in Boston. Thanks for sharing.

1 Like
#95

will just plain MIDI clock input be a possibility?
(for those of us who do not have a crow)
:slight_smile:

2 Likes
#96

That would indeed be sweet. I’m short on Norns development time these days, but I’ll add it to the list of ideas.

3 Likes
#97

THANK YOU from a absolute non programmer!
:stuck_out_tongue:

2 Likes
#98

I’m not 100% sure that this is the best thread to post this on, but I made a little tutorial about using @tehn’s Awake and @Olivier’s Compass for creating ambient sound beds. Also featured is @tslesicki’s wonderful Lekko. Thanks for making such inspiring tools, guys. Hope you enjoy!

30 Likes
#99

:bowing_man: Awesome to see the role Compass plays in your workflow @mattlowery. The video overall is terrific!

1 Like
#100

lovely vid. agree 100% about compass, so far one of the best scripts to process audio.

3 Likes