#21

Not sure how many crow/Max users out there are also big Jitter people, but it might be worth mentioning somewhere in the docs that [jit.gl.lua] isn’t currently supported in the new Jitter gl3 package.

I totally forgot about that in my first 5 minutes of trying to send crow commands from Max. Eventually I will want to do audio/visual crow things but you can totally get around that with running 2 separate instances of Max. That’s kind of good CPU management with heavy a/v stuff with Max anyways.

1 Like
#22

An interesting point - I had no idea!
@dan_derks do you have any insight why there is a [jit.gl.lua] but no plain [lua] object?

#23

The lua fanatic on the team was focused completely in the visuals domain.

2 Likes
#24

I’m guessing the need for delay is that the way i2c communication works means one can only send one command at a time, right? I.e., there’s no I2C command for “play these two notes”, so you have to make sure Crow sends one followed by the other. Is 10ms as low as the delay can go?

#25

for Just Friends, this gave me the most stable results. ymmv with going smaller, but worth further testing!

#26

On just the I2C bus I would say that way tighter timings than this are achievable. For a 32 bit message / 400 kHz clock I would expect a message to tie up the bus for at least 0.08ms, probably call it 0.1ms to account for software and other stuff (edit: I am forgetting ack bits and addressing and stuff. maybe at least double this number). Could probably cook up a crow script to get a pretty precise measurement. I use I2C for Kria fugue type stuff with TXo a lot and have never been bothered by triggers being out of sync, but lots of people can hear much smaller timing differences than I can. With PC -> Crow you also have the serial link (slower than I2C at 115200 bps, and sending more data) and the Lua evaluation latency in the loop which may also be a factor.

#27

For what it’s worth, I believe the need for i2c messages to be spread out with Just Friends, is because of the way Just Friends queues received messages internally. One day we’ll get around to improving that, but crow is perfectly happy to queue up a bunch of ‘simultaneous’ i2c messages & bang them out at the maximum possible speed.

3 Likes
#28

yo!
just got my crow and thought i’d start with this max for live kit.

unfortunately i’m getting consistent ableton live crashes every time i start to send data to crow.

running live 9 / max 7.36

adding command center is fine, but once i add another unit (doesn’t seem to matter which one) live will crash as soon as it starts sending data to crow…

any troubleshooting tips?

#29

I think that there’s fundamental trouble with lua + Max pre-8 :disappointed: . the entire crow serial communication is lua. it was working during initial tests, so I wonder what went weird.

I’ll download and test, though. apologies for the snag!

also, any crash reports you can send over would be :100:

edit: @shellfritsch , I’m not getting crashing on a newly installed Live 9.7.7 and max 7.3.6. loaded up ^^command_center on one midi track, selected my crow, then loaded ^^dual on another MIDI track. set keyboard to play notes, threw an arpeggiator in front, and am getting expected results. same with ^^jf_synth. plz let me know any more details to replicate?

edit pt 2: ah! got things crashy by switching modes rapidly on ^^outs, crow itself needed a power cycle + Ableton reported com.cycling74.MaxLua trouble. but this was after a few successful tests + once I power cycled crow the same test didn’t crash things.

edit pt 3: also, apologies for how wonky some of the labels on ^^outs looks with Max 7! blurgggggh backwards compatabilityyyyyy.

3 Likes
#30

upcoming livestream (<~~ click)

Sunday, October 20th | 5p-6p CT (US)

goals:

  • walk through setting up crow’s m4l devices
  • show example sets to demonstrate usage
  • answer any questions about the m4l devices y’all might have

full video will be posted after the stream, for those who can’t make it!

nb. the livestream won’t be a good space for detailed technical troubleshooting – if you are experiencing crashes, please reach out to help@monome.org or post here for assistance :slight_smile:

16 Likes
#31

Dan, this is really wonderful and most appreciated!

I’m hoping I can catch it in real time but am super grateful for it being archived…

Thanks so much :pray:t2:

#32

amazing! my crow is still inbound but i will be there with my notebook and pen at the ready :raised_hands:

#33

lol, u wanna just come over?

also, if anyone has q’s ahead of time, please post them! it’d be great to know what folks are curious about so I know what to cover and then the reserved q’s time can be more organic!

#34

i’m new to both crow and m4l, and i’m looking forward to using existing live/m4l sequencers with my euro gear while i learn how to code my own. any info on how to get that set up would be helpful!

if it wouldn’t mess with the livestream atmosphere/rhythm, sure!

#35

I’m getting some i2c cables delivered soon.

Many questions about them. I know I need to dig deeper into the user’s guide…

To try to focus the preliminary questions for a minute:

I only have Crow, not TT for now, what capabilities does Crow have to provide power to other i2c modules? I have W/ x1, Ansible x1 and JF x1. I also have a tetrapad…

Do I need some kind of i2c power distribution system like a txb or something else or does Crow provide enough power for a network of that size?

Can you address which i2c pins are which on Crow? I looked when I installed it and it wasn’t very clear…

Thanks!

#36

excellent topic! dope dope dope.

c’mon down!

@eblomquist, re: yr i2c q’s – this is all definitely outside the scope of the m4l livestream (and my skillset). I’d post these questions in ^^ crow help: general (connectivity, device q's, ecosystem) for the best answers :slight_smile:

2 Likes
#37

Dan,

I am thrilled to report that I’ve got JF and Crow connected over i2c, and I’m sending 6 voices to JF and at the same time I’m sending pitch to both mangroves and gates to Optomix from two Dual m4l devices on other midi channels… I’m modulating the JF v/8 time and fm from elsewhere in the rig…

The JF sounds like Elliot Sharp on guitar or something insane like that!

This is nuts, I love it!!!

Looking forward to Sunday if my schedule allows…

Thanks for everything!

Ed

5 Likes
#38

oh that sounds wild!! plz share any artifacts, happy to help :slight_smile:

1 Like
#39

I find myself getting lost in the flow of making the music and have a hard time breaking that to remember to set up the recording apparatus!

I need to get that together before long!

It was revelatory to have JF in polyphonic mode…I did notice some timing hiccups when doing things in Live like adding notes to the sequence, which was a bit confusing… however if I just let it run it sorted itself out…

Also the gates coming out of the dual didn’t seem to do much into Air on the mangroves so I ran them into optomix instead to ping the lpgs…

Lots of nice discovery and excitement for a tired Friday evening!

Oh yeah, I was able to get crow mounted better after a bit of filing on the holes… that was mildly anxiety inducing but worked out fine in the end…

Thanks again!!

1 Like
#40

remember, you can also switch those to envelopes! that might help hit Air just right