#68

I just ran into the same issue of input 2 on crow not reading incoming change (using Crow Studies pt 2 code) until I ran crow.reset() in maiden. should this be added to my norns script init?

1 Like
#69

Based on the teletype reference for Ansible i2c commands there is an actual pulse command so that looks like a bug in the Norns code. When I get a chance I’ll play around with editing that line on my Norns and see if I get expected results. If so I’ll make a pull request and we can get it sorted out!

I’m working on a Norns/Crow sequencer script and I’m feeling a little boxed in by only four outputs, so I would love to get the Ansible trigger outs working reliably.

#70

Sounds great… (i’m trying a little of the same - combining grids and arc). I changed the line locally on my Norns, and it helped with the pulses. I2c commands still seem to be rather randomly delivered to (or received by) ansible, resulting in randomly delivered pulses and cv’s. I don’t know where to begin to look for a solution to that problem?

#71

FYI got this fixed in master, so we should see it in a new release soon. I tested it locally with the latest version of Crow and it was nice to see properly synced up triggers on my oscilloscope!

2 Likes
#72

I would like to change the Crow output CV voltage range in some Norn scripts to 1.2v / octave instead of 1v, so I can use with a Buchla. Also to adjust the output trigger ranges. Could someone point to the correct maths to do the conversion? For example in the Awake script i guess this is the line to change, but not really sure.

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()

#73

This is the line:
crow.output[1].volts = (note_num-60)/12

Just multiply the value by 1.2 before assigning to volts, which simplifies to:
crow.output[1].volts = (note_num-60)/10

For the trigger, you need to change the crow.output[2].action = ... to something like crow.output[2].action = "pulse(0.01, 10)". Where 0.01 is the pulse time in seconds (here 10ms), and 10 is volts of the high-state of the pulse.

2 Likes
Controlling Buchla with Monome
Buchla Thread
#74

That’s great thankyou :slight_smile:

#75

Sorry in advance if this is not the best thread for this, but I’m trying to find all the Norns apps that support Just Type via Crow, is there a simple way for me to search the library for that?

2 Likes
Here: crow
#76

In the Library section, you can then choose the tags. There are a few, including Norns, crow, M4L to name a few.

2 Likes
Here: crow
#77

I’ve been working on a script for the last couple of nights, with norns > crow > jf ii communication working perfectly until a couple of minutes ago. For some reason, despite not being able to spot any relevant changes in my code, maiden is suddenly printing out the following after I enable ii communication for jf in the params menu:

ii: lines are low. try ii.pullup(true)

I do indeed have ii.pullup(true) included in my function for managing outputs, so I’m a little stumped – especially because everything seems to be working as expected despite that message.

#78

Has Just Friends frozen? You can check by changing to cycle mode and you should see JF’s lights turn on.

If that works it’s likely another device on your i2c bus has crashed or something has physically happened to the i2c cables.

1 Like
#79

Thanks! JF hasn’t frozen, and nothing changed with the rack from one session to another. I’ll see if the issue persists later tonight.

I’m guessing it must be something else. In case it’s a helpful data point, I do have TT (w/ backpack) on the same ii bus, and it has been performing (independent) functions while crow’s been in operation.

EDIT: This was definitely a case of my ii bus being overloaded. With crow + TT working simultaneously, I’d get the lines are low message when TXi and Txo+ were performing more complex operations. Cutting some of those out of my TT scene has fixed the issue.

1 Like
#80

Raising this, as I’ve come across similar issues myself. I’m looking to implement a safeguard for those using my scripts, but don’t want to do anything too heavy-handed either :sweat_smile:

3 Likes
#81

Hypothetically if I have two crows connected to one Norns and am running a script like Awake would both crows function identically? Thanks

#82

This is totally expected for any transmissions crow detects on the i2c bus that crow did not initiate – the lines are low some of the time, because the TT is pulling them low to signal to some devices. Aside from the usual warnings about increased possibility of crashes when using multiple leaders on the same i2c bus, I’m pretty sure this message is benign. Might be nice to have this message be possible to disable when you’re expecting this situation, ii.warn_busy(false) or something?

1 Like
#83

I’m currently experiencing some issues with crow. Norns does not seem to recognise crow and when I open druid, I get the following message:

Screenshot 2020-03-19 at 20.40.22
Screenshot 2020-03-19 at 20.40.221588×928 334 KB

I already tried reflashing the firmware. Any help is greatly appreciated.

#84

try running the user script erase command, after putting it into bootloader. it’s called (something like) osx_linux-user-script-erase.sh

1 Like
#85

Thank you! That fixed it.

#87

5 posts were split to a new topic: Norns + crow + clock: ^^first restarts and overrides norns script crow actions

#88

Considering crow to revisit just friends.
The information is very spread and i am not sure what i could expect.

May main questions would be, are there scripts (if i am not getting into scripting lua) that open polyphonic JF via grid+norns+JF ?

And the other way around, will crow allow to recieve JF as modulator to modulate within norns scripts? i suppose only on certain scripts that are written for crow, so not modulating anything like timber or passersby?