Bowery: a crow collection

Galapagoose · 2019-10-10T18:30:44.701Z

Longer scripts were pretty flaky with pre v1.0.0 firmware, so hopefully folks will have better luck after updating. I’m pretty sure Ornithopters wouldn’t have even worked with the r command in druid before 1.0.

glia · 2019-10-10T18:35:22.095Z

ah ok

sorry if i came across as kinda forceful…my crow is still enroute so i haven’t tested any of these

just reading the code and it seemed like it will be fun

voidstar · 2019-10-10T19:05:04.544Z

not forceful at all! Glad to hear it looks exciting to you!

AlessandroBonino · 2019-10-11T09:00:02.780Z

Wow! Just a question: if I wanted to add scale quantization to shiftregister.lua, would it be very difficult?

ioflow · 2019-10-11T09:21:10.584Z

i’m having severe issues with shiftregister.lua: it seems that it can’t properly track and output pitches; it’s playing just friends (via i2c) severely detuned. not sure if the issue is the script, crow, just friends, or ansible/kria.

steps to reproduce:

load & run shiftregister.lua on crow.
connect JF outs to mixer; either all six N outs, or mix out. (result will be the same either way). set JF to sound/transient. set JF knobs to something like a plain filtered sine-ish sound; no wild FM or harsh timbres.
setup a sequence of notes within ansible kria. for my test scale, i just used two whole, whole steps, and left the other note slots empty. only root, major 2, major 3.
patch ansible cv/pitch out to crow input 1, and patch any desired gate/trig source to crow input 2. i’ve used kria and teletype pulses; same results.
listen as JF plays the kria notes sent via crow i2c.
result: severely detuned, drifting, repeatedly off-key as time goes on.

attached is an audio clip. this issue has made shiftregister.lua completely unusable for me.

i’m not sure if the crow script is/isn’t doing something, or if just friends is drifting somehow and unable to play the correct pitch, or if ansible kria is unable to output a stable v/8 voltage.

crow-jf-asr-detune.mp3:

further testing:

send only one unchanging kria note into crow input 1, letting JF/JT repeatedly play that same note over i2c
switch JF over to regular RUN mode oscillator, sound/sustain
patch crow output 1 (the first delayed asr) to JF v/8 input
result: tiny, but audible rise in pitch from JF; it goes slightly sharp as long as it is physically patched. unplugging the v/8 cable at the crow output 1 end…immediately slides the frequency back down to “base” from i2c.

addendum: the pitched-up-detune-while-plugged issue is present with every oscillator i’ve tried so far; not only JF. crow’s outputs are noticeably sharp.

sonoCircuit · 2019-10-11T09:49:25.967Z

Not sure if this might be the issue:

^^ crow strategies: Just Friends

destination: all the notes at the same time

while building the ^^jf_synth device for crow’s Max/Max for Live toolkit , I ran into a funny thing – Just Friends is a 6 voice polyphonic synth, but in transient/sound it sometimes loses track of pitch data when it receives simultaneous messages over i2c.

If I understand the script correctly, all ASR outputs are updated simultaneously after a trig in.

EDIT: Can’t wait to try the scripts! My crow is still on its way…

ioflow · 2019-10-11T09:52:12.177Z

yeah, that was one of the first things i read. that thread deals with max4live and norns, so i’m not sure how to fix it in shiftregister.lua. also, even slowing down the incoming clock, so that JF doesn’t have to deal with and generate so many rapid notes, doesn’t help.

the slightly off-pitch issue is also present in JF sound/sustain when physically patched; though not nearly as severe as in sound/transient over i2c. it’s also present when using mangrove and other oscillators, so i think crow’s outputs aren’t precisely tracking the original pitch.

Jonny · 2019-10-11T12:52:10.935Z

@ioflow - It might be worth trying to delay the sampling after the trigger just a tiny bit to see if that helps. Perhaps the pitch is still rising or falling when that occurs.

voidstar · 2019-10-13T20:03:04.142Z

github.com

monome/bowery/blob/master/lorenz.lua

-- Lorenz Attractor
-- s wolk 2019.10.13
-- Input 1 resets the attractor to the {x,y,z} coordinates stored in Lorenz.origin.
-- Input 2 controls the speed of the attractor.
-- Output 1 is the x-coordinate (by default)
-- Output 2 is the y-coordinate (by default)
-- Output 3 is the z-coordinate (by default)
-- Output 4 is a weighted sum of x and y (by default)
-- The config table allows you to deactivate the attractor for outputs and take direct control.
-- The weights table allows you to specify the weight of each variable for each output.

config = {'on','on','on','on'}
weights = {{1,0,0},{0,1,0},{0,0,1},{0.33,0.33,0}}
Lorenz = {}
Lorenz.origin = {.01,0,0}
Lorenz.sigma = 10
Lorenz.rho = 28
Lorenz.beta = 8/3
Lorenz.state = {.01,0,0}
Lorenz.steps = 1

This file has been truncated. show original

Lorenz Attractors on crow! Chaotic, slow LFOs… plug 'em in to your vector scopes for pretty patterns, or use them as slowly-evolving LFOs!

mlogger · 2019-10-14T01:57:27.727Z

@voidstar The Lorenz could open up a can of worms for the vector synthesis crowd - great idea

dan_derks · 2019-10-15T00:39:52.745Z

3 posts were merged into an existing topic: Less concepts

voidstar · 2019-10-17T01:41:21.669Z

github.com

monome/bowery/blob/master/quantizer.lua

--- quantizer example
-- s wolk 2019.10.15
-- in1: clock
-- in2: voltage to quantize
-- out1: in2 quantized to scale1 on clock pulses
-- out2: in2 quantized to scale2 on clock pulses
-- out3: in2 quantized to scale3 continuously
-- out4: trigger pulses when out3 changes

-- nb: scales should be written as semitones (cents optional) in ascending order
octaves = {0,12}
major = {0,2,4,5,7,9,11,12}
harmonicMinor = {0,2,3,5,7,8,10,12}
dorian = {0,2,3,5,7,9,10,12}
majorTriad = {0,4,7,12}
dominant7th = {0,4,7,10,12}

-- try re-assigning scale1/2/3 to change your quantizer!
scale1 = major
scale2 = harmonicMinor

This file has been truncated. show original

This example illustrates one quantizing method, including a continuous output (plus a trigger output on note change) and clocked versions.

rennerom · 2019-10-20T17:25:38.653Z

@ioflow, have you found a resolution for the pitch tracking on shiftregister? I am experiencing the same issue with Kira providing the triggers and pitch information.

voidstar · 2019-10-24T13:04:31.505Z

Use crow to easily generate Euclidean Rhythms!

github.com

monome/bowery/blob/master/euclidean.lua

---  Euclidean Rhythms
-- sam wolk 2019.10.21
-- Create 4 euclidean rhythm generators
-- in1: clock
-- in2: reset
-- outs: euclidean rhythms

-- ER parameters for each channel.
lengths = {16,16,16,16}
fills = {4,5,9,12}
offsets = {0,0,0,0}

-- Non-User Variables
locations = {-1,-1,-1,-1} --

-- ER function adapted from  https://gist.github.com/vrld/b1e6f4cce7a8d15e00e4
-- k > Euclidean Fill
-- n > Euclidean Length
-- s > current step (0-indexed)
function er(k,n,s)

This file has been truncated. show original

cosmicsoundexplorer · 2019-10-25T01:09:34.499Z

Oh fantastic! I can see this besing super fun triggering jf in plume mode or hitting 4 lpg’s. As I’m not a coder I was thinking it may be nice to change the rhythm patters with cv into input 2 and have the whole thing reset when the clock is stopped? Just an idea but it would be really cool to have!

voidstar · 2019-10-25T01:15:21.638Z

Even though you may not currently do much text-based coding (modular is its own form of “coding” on some level - i.e. systems thinking), I think this would be a really good project for you to try if you want - happy to help guide!

Also, thanks to the I2C functionality, you don’t need to physically patch crow’s outputs to JF’s inputs - you could set up separate ERs and use those to trigger JF via i2c while the hardware jacks run their own rhythms (or do something totally different) - again, happy to help you with this if you want to try yourself! Would be a great jumping in point.

yobink · 2019-10-25T21:14:55.168Z

Super cool script! Had some fun with it this afternoon!

ioflow · 2019-11-06T17:16:21.957Z

not yet; the issue is still present. however, it has been addressed by @dan_derks and @Galapagoose. there are workarounds, and there may be a permanent solution in a future crow firmware update.

^^ crow strategies: Just Friends Monome

This will be fixed in the next Crow firmware release. I’ve got proper polyphony working already, but it needs more testing.

^^ crow strategies: Just Friends Monome

Sounds like Kria’s gates are triggering the input.change before it’s CV output has settled. There’s no in-built delay function in crow at the moment, but I sketched up this solution to the problem (though it’s untested as I’m away from my case rn): -- add this function to your script -- (to be included in crow firmware in future) function delay( time, action ) local function devent() action() -- this line executes the delayed function metro.free(dmetro.id) end local …

Lervais · 2020-03-29T21:24:37.799Z

Was this ever resolved? I just tried uploading shiftregister.lua for the first time (with newest crow firmware) and had the same tuning issues.

I would also love a way of playing JF as a pseudo-poly synth (à la rings with overlapping envelopes) by patching v/8 & trigs to crow - think shiftregister.lua without the shift register! I’m guessing this wouldn’t be too hard, but am unsure where to start as I don’t know the first thing about lua - or writing scripts in general for that matter.

Maybe everything I need for this is already in the shiftregister script, so all that is needed is some tactical redaction?

Edit: just saw the scripting guide and it looks more approachable than I expected. Really appreciate all the work behind this documentation. Will have to give it a go when I find some time!

cosmicsoundexplorer · 2020-03-30T03:22:57.758Z

Try this out.
input 1 = gate
input 2 = v/oct

jfs.lua (554 Bytes)