#63

You can trigger notes on Just Friends (or TXo, or ER-301, or Disting EX, or eventually crow or W/syn) from Ansible directly, e.g. having Kria (or any other Ansible app) notes send JF.NOTE commands simultaneously with the normal gate/CV output. You could activate this mode and still send messages like ii.jf.shift from crow to transpose the pitch JF is outputting, for instance. However when Ansible is in leader mode it can’t act as a ii follower, so you cannot poll Kria parameters over ii.

1 Like
#64

got it, thanks! The polling solution seems to be what I’m after – I’m gonna try writing a few different scripts in isolation that each do one ‘part’ of what I’m looking for, and then see if I can get them to play nice together – as a personal test I’m gonna try not bugging you for a week :stuck_out_tongue:

#65

Thanks @Galapagoose, @yams and @desolationjones

I forgot to mention that I’m running fully up to date firmware on both crow and Just Friends, so that factor is eliminated.

I’ll adjust the script to put the metro starts in the right place as suggested, and try a shorter cable from the 16n to the crow - I have a really short one somewhere. Failing that I’ll see if I can source a Txb. I’ll report back on this thread in case it’s useful to others - I’m sure there are a few folk looking to build crow scripts with the 16n as a controller.

Alternatively I could use Norns as an intermediary and avoid i2c - I guess I’m hoping to use Norns for other things but I do worry about using external i2c connections in a performance setting just because of needing to be careful about cable length, powering on in the correct order etc. keen to get a feel for it all before making any judgement tho.

#66

i2c is quite electrically sensitive so a complex network with external cabling is perhaps dubious.

sounds like there is a need for a tiny usb-i2c bridge module

6 Likes
#67

I just got a w/ in the mail today and want to connect it to Crow and try out the i2c feature. Booted up the M4L device for w/synth and read the “manual” where it states that I need a Just Friends for it to work. I am totally new to this so if anyone would like to guide me for my first steps, getting sound from w/synth with crow from either M4L or Norns I would be very thankful.

#68

oh! weird, apologies – you definitely don’t need Just Friends for it to work. the w/synth m4l device is not release ready (it’s an easter egg), so it hasn’t gotten that final touch-up :slight_smile:

have you updated your w/ to the 2.0 beta firmware? if so, you just need to set w/ hardware to the W/Syn mode. then, load ^^command_center on a track in Live, connect it to your crow, and then load the w_synth device – that is the common workflow for any of the M4L devices.

if you have any specific q’s about the M4L toolkit, happy to help! ^^ crow: max for live + max v2.0

2 Likes
#69

good suggestion @tehn - I don’t have the skills for designing circuit boards, but if there was a way of prototyping a USB to i2c interface on a breadboard, I’d be happy to give it a crack, or else be a beta tester for something someone else designs. I guess a teensy would be an easy option, but maybe that’s overkill.

A 2hp form factor would be ideal for in terms of something that sits next to crow, but hard to prototype something that small I guess - how hard would it be to adapt the existing Txb pcb design to serve this purpose?

#70

Revisiting the situation and everything is working. Probably missed something yesterday. Thanks for your help.

1 Like
#71

This is probably expected behaviour/user error but:
I’m using the shift register script on crow to control JF by I2C. A couple of odd things happen:

  1. I don’t understand how to stop JF responding to Crow without restarting the module. I can change the script on Crow, but it still continues to pulse like it is receiving a clock, emitting sound but the pitch not changing. I can address by JF Synth in Max, and that will play it, but the pulse still doesn’t go away. So is there a Crow/Druid command that will reset JF back to its normal state?

  2. There could be many explanations for this. I can put a quantised random voltage into the shift register, and it will play fine and keep in tune. But if I feed it an output from Ansible (Kria), it’ll go wildly out of tune. The same sequence straight into JF is fine.

I think I’m looking for an answer to the first, and speculation on the second! Thanks all.

#72

To get out of synthesis mode you can send this message from druid ii.jf.mode(0).

Not sure about the second question.

2 Likes
#73

Is crow capable of jack detection?

#74

Same/similar question. Looking to “normalize” input 1 to input 2 when nothing is plugged into input 2. Could not find anything in the docs.

If not directly supported maybe there is a clever programmatic way to a chive this?

#75

@Galapagoose @csboling I am having an issue with Ansible playing 2 x JF with an Arc and wondering if it is Crow related. I have a Crow / Teletype / er301 / w/ also on the bus but not running any script. Once first set up, JF works fine activated in Ansible. The problem is whenever I reboot.

If I reboot, JF does not come back to synth mode and very difficult to get back to synth mode. It doesn’t lock up, but the synth mode is lost. The correct JF settings are still there in Ansible. Changing the JF setting in the system menu on Ansible after reboot, has no effect. The only way I can get JF back to synth mode is to send II.jf.mode(0) in Druid. I tried sending a mode change via Teletype but no effect, only via Crow worked. Reboots didn’t get JF synth mode back.

Not sure if it’s an Ansible issue, JF, or Crow. I’m on the latest firmware on all those modules. I was wondering if Crow is somehow running something on reboot that is reseting Just Friends and stopping the Ansible script working. Like a boot sequence that overrides Ansible.

I tried changing the Ansible system menu to select er301 after one of these reboots and that has no effect. Basically the whole of the i2c bit of Ansible is unresponsive after a reboot. The II.jf.mode(0) from Crow seems to clear the whole i2c line.

The only other thing I could think of was pulling too much power off the bus? I recently added 2nd JF to the case. I do have a powered backpack running and also Crow with pull up power. It’s just weird because it only happens after a reboot and when Ansible i2c modules are selected

Just Friends v4.0
#76

You could set a metro, check if the input is 0V, and increment a counter if it is. Anything other than zero clears the counter. Then trigger your function if your counter gets past a threshold.

1 Like
#77

Hi --I am thinking about trying out crow in my small eurorack system and was wondering if it’s possible to use it get polyphony from Just Friends without Max/Live. Is this something I can do using druid?

Also, has anyone done anything interesting with Reaper and crow?

#78

Yar! I believe that is precisely the theme of this episode of Maps w/ Trent.

1 Like
#79

Oh awesome! I didn’t know that existed and will check it out now. Thanks!

#80

This sounds kind of like something in Ansible’s i2c code got messed up during startup and after that it can’t send i2c commands, or something like that. If you have leader mode activated in your saved Ansible settings then it will try to set JF.MODE 1 as soon as Ansible starts up, if you have a large I2C bus I can see how sending a message during power up could maybe be problematic. However turning off all followers should cause Ansible to change to follower mode, which for the most part resets Ansible’s i2c driver, so it’s odd that this is having no effect. This is possibly difficult to reproduce given that it most likely depends on your i2c configuration, but I can try.

In particular I’m dimly aware of some issues where ER301 takes a while to be ready to accept i2c commands during startup, so I wonder if this could be related, but I’m not an ER301 user. I realize messing with one’s i2c bus can be a bit of an ordeal but it might help narrow down the problem if you can identify which maximum set of modules it still works correctly for, like “with modules X Y and Z connected it works, but after I add module Q it breaks”.

#81

Thanks, I tried again today. On reboot, both JF still didn’t default to synth mode I left it in. This time however, i managed to get them working by repressed the exact same JF lit settings for pitch and mode.

It’s interesting what you say about the er301 - that could be it. I’ll try turning off the i2c in the boot up system setting on the ER301. Then switch it on afterwards.

Update - i disabled the er301 i2c but still no joy with Ansible keeping JF settings on my system after rebooting. And again changing any of those system i2c settings in Ansible has no effect, the same as my original post.

i’ve open Druid and typed ii.jf.mode(0)
i get this error
ii: lines are low.
check ii devices are connected correctly
check no ii devices are frozen

i am pretty sure my lines aren’t low and correctly connected, but there are a lot of devices on my i2c that could be conflicting somehow after a reboot when connected to Ansible. Both JF aren’t frozen as they light up when switched to cycle. Ansible isn’t frozen as the output lights are working. As a test i connected Norns to Crow and tried the Awake script with JF as output but no go.
What is interesting is both Just Friends after a reboot sometimes play for 1 sec then cut out and stop.

Update : i took off er301 and the second Just Friends from my i2c.
I still have the same issue with Ansible after rebooting - i have to reselect the i2c for JF. Its seems like that setting is being overwridden on reboot

Just Friends v4.0
#82

Suddenly i have a error on my crow.
I now get
!ERROR! Out of memory
upload failed returning to normal mode

I get this when i want to upload any script (so even really small ones)
How can i fix this?