wild – each device was flashed and tested before being shipped, so please email help@monome.org and we’ll get it sorted out :slight_smile:

@atomboyd, it sounds like @Loitering isn’t getting anything on any platform – I think you’re safe, but please let us know if things get weirder!

1 Like

“When the going gets weird, the weird turn pro” :laughing:

2 Likes

Welcome to bonkers town.

The damnedest thing happened. I found out my friend who lives nearby got a crow also. I had him bring his over and we swapped it into my setup changing NOTHING. JF worked instantly in poly mode as it was supposed to. So we swapped my crow back in - again changing nothing, not even a single I2C cable order or anything - and then my crow and JF immediately worked. I’ve seen some weird stuff but that takes the cake.

Then about an hour later, while unpatching a few cables from my JF (still in poly mode) it abruptly went silent and stopped working (in poly mode - still works totally fine as normal) and I’ve not been able to get it to go into poly mode since.

At this point, I think SOMETHING must be loose (?) in my JF or something. No idea what to do next.

1 Like

i’ll add an input clocking mode to awake as an example, apologies for the delay

that is a gremlin of a problem. you already mentioned switching the cables. there’s a chance there’s a tiny cracked solder joint somewhere, but hard to know if on the JF or crow. (you could test JF if you have a TT). seems like it might be time for a service email

2 Likes

I was going absolutely insane yesterday: my Crow was working - after I was re-cabling stuff in my stuff in my studio, then I was completely unable to communicate with it via my Norns. I dug around replacing an i2c cable, repeatedly rebooted the Norns, reseated the cable on both ends, nothing.

Finally I changed out the usb cable between the Norns and the Crow (for a different, also Monome-supplied cable of the same length) - and it worked! Strangely though, that “bad” cable works fine with my Arc and Grid.

The kind of problem that almost seems like it’s all in my head.

2 Likes

I’m going to try a few more things and then I’ll be hitting up service. :smiley: One weird thing I noticed is that the “landscape” PCB and the standoffs on the back of my JF are loose now, kind of rattling around when I move it. I”m going to tighten it back down just for the hell of it and try recabling and poking a few more things. Everything feels like a smoking gun at this point.

thanks for reminding me that the USB cables are a point of failure. easily overlooked, and not unlikely given the mass-production from which they come.

1 Like

update procedure on windows?

I’ve tried

dfu-util -a 0 -s 0x08020000 -R -D crow.bin -d ,0483:df11

image

edit: oop. need to install dfu-util

You’re trying to run dfu-util from inside druid, but they are totally separate so you’ll need to run flash.sh from a bare terminal.

On Windows things can be a little (or a lot) weirder! @EqualTemperament wrote up this great google doc on the windows update procedure which we’ll get wrapped into the official docs soon. Posted here in the interim.

1 Like

Ok thank you. I’ll have a look at the doc. First is ace by the way! Just lost the last 30 minutes on that :slight_smile:

quite the hairy update procedure!

but all seems ok, ^^version(‘1.0.0’)

1 Like

At the risk of a stupid question: M4L gets spoken about a lot with regards to crow, does that mean this all works for regular, ol’e Max as well? I don’t have Live but I’m considering picking up a Max license to play with my new crow…

Looking for advice on crow and i2c

If I was going to hook up one module to start with, which one and why?

I have Ansible, W/, and JF. I also have Cold Mac Sisters and a pair of mangroves, but those don’t use i2c, so…

I’m psyched to try one, but must manage the multiple learning curves…

Thanks!

Hi, I just received my crow, plugged it into my shared system, and first will not advance with any clock source.

I have verified polarity, changed plugs, and still no response.

When unplugging the clock source, the script advances when the cable shorts out on the jack.

Also, it seems both Inputs are outputting positive voltage. Any ideas?

You should be able to open the .amxd M4L devices in max - you can try this even without buying a Max License! Some of the M4L devices though are expecting to receive data from Ableton to work though - MIDI notes, clock etc. Simple modifications would allow them to work with other data sources though.

I am working on some devices that will be for use natively in max so that you do not need an Ableton license or a max license - all you will need is Max installed! You will be able to run the patches in max runtime mode (unauthorized) but not save your own changes. If your desire is just to use pre-made patches built by others, then you will not need a license, but you will need to wait until they are published by whoever is making them!

If your goal though is to program your own max patches, then the answer is yes, crow is totally hooked up to Max! Go for it! All the M4L devices are just plain ole patches with special communication channels with Ableton.

You can always download the trial and see how you like designing in max!

4 Likes

This is great thanks! I want to start doing my own work in max seems like a lot of fun in the little bit I’ve played with it so far. Good to know about the differences that might show up w/ regards to the live-integrated patches… Cheers! :clinking_glasses:

Go with JF, just because :slight_smile:

5 Likes

Just saw your update to awake, very excited to try it out. Would it be possible for INPUT 1 or 2 to act as universal clock input for whatever script is active on norns, making it somewhat of a CV/MIDI converter for crow to norns.

There are a few patches I have been experimenting with lately that use a global clock shift, so being able to clock it externally from a different master source would be very helpful without having to use some other type of CV/MIDI conversion just to send a clock source into norns via USB rather than into crow.

I’m not saavy on the coding end and also not sure if this type of communication is even possible on crow/norns. Just trying to find some workarounds because I love the sequencing capabilities of Crow/Norns

we’ve been envisioning a universal clock utility for norns… internal/external, midi, ableton link, etc… could add crow to this list.

honestly it’s very easy to make small changes to individual scripts. it’s much more of a challenge to devise these master-design-plans… so they take more time.

in the meantime i’d expect to see some little fix-it wedges to achieve the sort of functionality you’re imagining.

10 Likes

I spent some time last night troubleshooting. I’m trying to verify if I have a faulty crow. I cannot get my crow inputs to respond to gate/trigger signals.

  • Crow is plugged into a MN shared system.
  • Different power cables and headers tried.
  • Verified polarity.
  • Updated to 1.0.0, verified and re-calibrated with druid.

I am still seeing a positive voltage output from the inputs. Feeding gates/triggers to the the input does nothing. Shorting a cable plugged into the input advances the script.

I am trying to gauge if this is a hardware fault or something I can fix with software. I was hoping to spend the day with crow.