#22

Hey everyone, been messing about with crow and max for live devices available for it today and had some issues:

When connecting crow first via commander, then on another track i set up the Outputs m4l device and mapped an envelope follower coming from a drum track to one of the crow’s outputs. Due to envelope follower being very fast in terms of responce, crow would first work fine by outputting envelope follower’s output via output 1, then it would always switch to one of the previously loaded druid scripts. Then I would have to disconnect crow and plug it back in to get the envelope follower output working again. After a few times my Ableton would just crash completely.

Is this caused by very fast cv signal from envelope follower not being able to pass via usb? Is this is a bug? I did try to slew the envelope follower a bit, but the same issue would come up sooner or later.

Steps to recreate:

  1. Connect crow to computer via usb cable.
  2. Connect to crow using commander m4l device on one midi track.
  3. Add Outputs m4l device on another midi track
  4. Create another track that has drums for fast amplitude variation.
  5. Drop a m4l device called envelope follower to the drum track and map it to one of the outputs on the Outputs m4l device for crow.
  6. Crow should translate the envelope follower for a minute and then it will switch to previously uploaded druid script.
  7. To make it work with envelope follower again, disconnect and connect crow using the usb cable.
  8. After a few iterations of the last step Ableton should crash.
#23

Hearing that crow would switch to a previously loaded druid script seems to me that it might have been running the whole time.

When you connect crow to Max/M4L, the current script is nor cleared unless you specifically ask it to, instead the messages from Max are being executed ‘on top’ of whatever is running.

Easiest solution is to run the ^^clearscript command (from druid or comnand center). You’ll only need to do this if you have since uploaded a script from druid.

2 Likes
#24

I have been having difficulty getting crow to talk to a second ansible using the ii.ansible commands. They both work just fine when the ansible address is set to 0, but they don’t appear to receive commands when set at 1 or above.

using max I can successfully send ii.ansible.trigger(1,0) to the unit addressed as 0, but don’t see any indication of response when the unit is addressed as 1 and I send ii.ansible.trigger(5,0) or any trigger on a channel above 4.

Am I missing something here?

Thanks for the help, really enjoying max and crow!

#25

This is because crow only currently supports a single ansible connected at once. The good news is it’s 1 line of code to enable it, I just had no idea that multiple ansibles could be chained like that! I’ll get this into the next release.

2 Likes
#26

Thanks, glad to hear! I’m just starting to scratch the surface on the 1st one, so this will help me from rushing into complexity. Just getting around to integrating old max patches and crow and it is a blast

1 Like
#27

I received my crow somewhere in January. Is there a way to check its firmware version?

#28

Type ^^v into druid or the maiden REPL. Or from max use the help patcher which has a page for these system actions.

1 Like