Here: crow

eblomquist · 2019-09-28T10:07:50.633Z

Can Crow be used without Norns?

I have one Ansible and one JF, a Grid and an Arc but no plans currently for a Norns.

I’m most interested in using it for interfacing between Ableton/M4L and my eurorack, alongside my MOTU Ultralite mk3hybrid as a way to send cv into the eurorack.

Thanks.

GoneCaving · 2019-09-28T10:30:16.796Z

eblomquist:

Can Crow be used without Norns?

I thinks that’s answered in the docs and videos which show it being driven from Max, M4L and directly from a laptop. No Norns in sight.

grey · 2019-09-28T11:09:04.999Z

@eblomquist, yes, you can definitely use crow without norns: The demos show it with M4L in Ableton, via druid for Teletype like direct connection with a computer, and it can also run in a standalone mode where it just runs whatever script that is loaded on to it when it boots.

tehn · 2019-09-28T11:34:44.312Z

spoiler— here’s some audio from first

crow → mangrove → RIP

(reverb and recorded to tape via norns)

ether · 2019-09-28T12:02:08.936Z

Thank you @tehn, @Galapagoose, @dan_derks and any others I’ve missed for the amazing vision and drive to make this real. Looking forward to new ways of making norns + modular music and more.

riggar · 2019-09-28T12:41:17.627Z

Many thanks to all the hard work putting this togther - it’s looks to be a great extension to monome ecosystem

SwainVoorman · 2019-09-28T12:52:24.546Z

Very excited to include crow in my system in the future.

As I currently have a W/, is it possible to connect a W/ and a crow on a slash board to consolidate power and i2c? If so, does anyone know when more slash boards would be available for purchase or will those only be available DIY n the future?

alanza · 2019-09-28T13:54:14.844Z

Yes, I believe it’s possible; @Galapagoose mentioned that he had racked up something like this while testing Crow. It seems likely that Slashes boards will remain DIY for now.

sbaio · 2019-09-28T15:44:44.941Z

Wonderful, congrats to all involved!

Very excited to extend the zellen sequencer with crow, especially in conjunction with JF!

dan_derks · 2019-09-28T16:09:26.105Z

speaking of those involved, quick shout out to @voidstar who provided the initial foundation/inspiration for the m4l devices. sam’s efforts were essential in helping me understand the crow syntax and how to approach the structure. also, sam is incredibly giving of time, advice, and positive energy.

scotttburton · 2019-09-28T16:55:40.919Z

Congrats on the new release! I ordered so fast——-I’m excited to extend my methods of using a guitar to interact with modular, by sending gates and envelopes. And stoked to learn some of what this ‘code’-ing thing is all about!

speakerdamage · 2019-09-28T19:28:17.646Z

in the demo video script I see the options for output. will it be possible to send audio (internal engine, I assume) + Crow ii JF together? I see audio + midi so I’m guessing it could be done.

dan_derks · 2019-09-28T19:39:26.101Z

yes, both could feasibly happen simultaneously – it all depends on how the script is coded. looks like awake offers silo’d choices at the moment.

tehn · 2019-09-28T19:43:25.119Z

somewhat sloppy and uncommented, but here’s the output switch:

github.com

tehn/awake/blob/crow/awake.lua#L117


one.pos = one.pos + 1
if one.pos > one.length then one.pos = 1 end
two.pos = two.pos + 1
if two.pos > two.length then two.pos = 1 end


if one.data[one.pos] > 0 then
  local note_num = notes[one.data[one.pos]+two.data[two.pos]]
  local freq = MusicUtil.note_num_to_freq(note_num)
  
  -- Audio engine out
  if params:get("output") == 1 or params:get("output") == 3 then
    engine.hz(freq)
  elseif params:get("output") == 4 then
    crow.output[1].volts = (note_num-60)/12
    crow.output[2].execute()
  elseif params:get("output") == 5 then
    crow.ii.jf.play_note((note_num-60)/12,5)
  end
  
  -- MIDI out
  if (params:get("output") == 2 or params:get("output") == 3) then

sellanraa · 2019-09-28T20:57:07.528Z

Totally tangential, but my real concern in all this is when will @voidstar release more music?!?, because the Salon CD is fantastic.

madeinspace · 2019-09-29T06:05:22.519Z

How would you use Crow in conjunction with MLR for example

its_your_bedtime · 2019-09-29T07:54:21.881Z

my guess is to control w/ as an external mlr track (not sure thats possible right now)

crim · 2019-09-29T11:22:51.959Z

madeinspace:

How would you use Crow in conjunction with MLR for example

you could presumably modify norns midi clock to output a clock signal to crow and sync mlr with your modular.

Maybe you could also modulate certain mlr params with the modular (toggle record arm with triggers, modulate slew with cv, idk).

There’s been a lot of talk around sequencing the modular/JF with crow, but I’m also pretty excited about having norns scripts respond to cv. I’m not sure how well streaming continuous change like an lfo or envelope will work, but even just responding to triggers and thresholds could be cool…

ioflow · 2019-09-29T11:33:46.800Z

tehn:

Nordseele:

I’m planning to connect Crow to the ER-301 via I2C but for regular modules

ER-301 is not yet mapped out (neither trent or i have one)— but it’s incredibly simple to add new i2c modules— see https://github.com/monome/crow/blob/master/lua/ii/jf.lua as a reference.

if someone would like to make er301.lua and send in a PR we can release an update right away. i think the TT can be used as a reference implementation for the protocol.

done. i made the initial attempt at supporting er301 ops within crow. sent the pull request.

note: due to lack of information on er301 internals–including value size and signed-ness it expects to receive–this set of commands has a bit of guesswork. the 301 wiki doesn’t have the info, either. signed/unsigned float for certain numbers/voltages? or just 16bit int, and is it signed or not? this might be in TT’s sourcecode; will look. also, some of the er301 ops use values from TXo ops, so crow might also need TXo support.

next day edit: after some extremely helpful discussion with @odevices over on the O|D forum (thanks, brian!), i’ll send in a revised patch, asap.

this er301 support will need testing by folks who have all the hardware; my er301 is from the first batch, and lacks the bridged pins for i2c integration. also, there’s currently no support for multiple er301 units; i’m not sure how to handle second and third devices with 0x32, 0x33 addresses within crow’s lua framework.

Nordseele · 2019-09-29T11:44:01.123Z

That’s great, thanks a lot !
I also started to write a file yesterday, mostly based on the ansible model https://github.com/nordseele/crow/blob/master/lua/ii/sc.lua but it was just an attempt. I was not sure about the types of arguments so I have asked Brian on the OD forum, perhaps he’ll reply soon.

I think the LUA name of the module is also the name that needs to be used when writing the commands in the scripts and must match the name of the file, so do you think we can call it sc.lua instead of er301.lua ? It would save a few characters. sc.trigger() in place of er301.trigger()

I’ve ordered a Crow on Friday and I have a 301 with I2C, I can do some testing when it arrives.