#123

Is it possible to have a basic BPM tempo adjustment instead of seconds in the future update? Seconds is cool and gives more flexibility, but bpm would be much more convenient when using other groove boxes etc

#124

mabye there could be a toggle for timescale?
classic (seconds/miliseconds) or bpm mode

not sure if the app would allow it but if bpm were added i’d like to be able to choose

1 Like
#125

So much, it would make a crazy companion for beat oriented music damn…

1 Like
#126

I’d definitely chalk this up to limitations in my code, but in the past, I found that precision was lost when rapidly manipulating the metro — hence why I leaned heavily towards an async approach. Definitely interested in exploring this area more, though!

2 Likes
#127

Hello everyone! First post in this thread, assembled my diy Norns Shield a couple of days ago and got to play with Compass, really enjoying it so far :slight_smile:

Although, after the latest update 200129, the script seems not being able to load properly and I get an error: init message on the Norns screen. Guessing it to be just a firmware compatibility issue, don’t know if I’m correct.

Here’s what Matron reports back:

### SCRIPT ERROR: init
/home/we/norns/lua/core/softcut.lua:140: bad argument #3 to 'cut_param' (number expected, got nil)
stack traceback:
	/home/we/norns/lua/core/norns.lua:126: in function </home/we/norns/lua/core/norns.lua:126>
	[C]: in field 'cut_param'
	/home/we/norns/lua/core/softcut.lua:140: in function 'core/softcut.pre_filter_fc_mod'
	/home/we/dust/code/compass/compass.lua:297: in global 'init'
	/home/we/norns/lua/core/script.lua:93: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:127: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
>> reading PMAP /home/we/dust/data/compass/compass.pmap

PS: First time reporting a block of code from Norns, please let me know if my formatting is not correct.

1 Like
#128

@tehn or @zebra - is this a typo? aount instead of amount

softcut.lua:140:

SC.pre_filter_fc_mod = function(voice,aount) _norns.cut_param("pre_filter_fc_mod",voice,value) end

and/or should those items be matched (value instead of aount)

updating to this gets compass to work properly

SC.pre_filter_fc_mod = function(voice,value) _norns.cut_param("pre_filter_fc_mod",voice,value) end

FYI if you decide to update softcut.lua yourself, you’ll need to ;restart from maiden or do a RESET on device.

2 Likes
Norns: update 200129
#129

It did work succesfully, thanks a lot for your help :slight_smile:

1 Like
#130

yes its a typo and will push hotfix [PR’d.] [merged.]

1 Like
#131

LOL, I was thinking about this, and because I’m the idiot so you don’t have to be, I figured “well, I should try feeding the output of the Tape (i.e. physical “L Output” on the back side) into the L Input (e.g. with just a 3” mono-to-mono patch cord) and record that (while praying that the feedback loop doesn’t cause a black hole to appear)"

Hilariously enough - IT WORKED. It takes a little jiggery, but I recorded something with meadowphysics to Tape, and then fed Tape’s out back into the buffer in compass…

Mainly, you want to hold K3 (to reset the compass play heads), quickly release it (to start playback), then flip over and start the tape play (which you’ve already set up). Otherwise, compass might try overdubbing, which is safe, but probably not what you want.

Levels set like so:

IMG_0462
IMG_04621536×770 136 KB

5 Likes
#132

I just recorded a little video with Compass. I am a new Fates user, trying the scripts. This Compass script is wonderful!

First, I play a synth melody with the Deluge, that is recorded into Fates using the Compass wonderful script from Olivier Creurer and then I begin playing the piano. I like the contrast that happens between the 2 instruments, where everyone seems to be playing on his own, and other times they play perfectly in sync.
Piano is recorded with a pair of Marshall MXL603s and a touch of Valhalla Vintage Reverb is added.

I have one suggestion: I think when you don`t want to use the whole tape and you choose a start and end loops points, setting for example a 30sec loop, the play head shouldn’t jump outside this initial loop when an “L” command is readed. What do you think? I have to be very careful to quickly eliminate and L command of the sequence, so the head didn’t jump and I got silence from the unrecorded part of the tape.

24 Likes
#133

This is beautiful @mcpepe - thanks so much for sharing. I totally hear you on the potentially destructive nature of the L command – sometimes I like the way it works from a performance standpoint, but other times I exclude it from my command sequence for precisely the reason you mentioned.

I may have some time this week to look at alternatives!

4 Likes
#134

That would be wonderful. Thanks for this great script!

1 Like
#135

very cool noiz!

are you going to perform on the Deluge tour?

i’m going to make noiz at the Austin show.

#136

Thanks! I am from Spain and the Deluge tour doesn’t come near here. :sleepy:

1 Like
#137

I’d love to have a random record function…

4 Likes
#138

Totally!
Punch in and out commands could be a lot of fun. Especially with a smaller loop creating a more delay like effect where it randomly grabs new audio and mangles it :smiley:

3 Likes
#139

@mcpepe @swhic - thanks for the super helpful ideas. I’ve got a work in progress that feels pretty good. More testing/tweaking to be done, but I’ll try to have a new version up in a day or two.

16 Likes
#140

Looking good!
Keen to try this out :smiley:

2 Likes
#141

and it sounds good! :slight_smile:

1 Like
#142

v2.1 released!

Download at Github (see top post for link) or install via Maiden’s project manager.

Frame 2
Frame 21600×800 3.59 KB

Updates:

  • :: – this new command toggles recording on/off
  • Loop behavior has been redesigned. When you adjust the Start and End point parameters (same as always: K1 + E2/E3 or in params), a fixed window will be created for your loop, indicated by those little dots in the screenshot above. As a result, if the L command is used, your loop won’t ever jump beyond your start/end points.
  • Compass now has an sc engine! A local copy of the Decimator ugen (the same one @Justmat bundled into Otis) is available for bit reduction fun (head to params to adjust bit depth).

:warning: Heads up

The new loop behavior, along with the addition of a bit depth control, necessitated changes to the params list. If you had previously midi-mapped some stuff, you’ll need to re-map after updating.

Also, make sure to restart norns after installing/updating to avoid any engine errors.

27 Likes