#133

This sounds like your norns software is not up to date. Which version of norns are you using? If it is the most recent, I’ll have to see if there’s an issue with the norns integration script.

1 Like
#134

Just updated my norns. That did the trick. Thanks!

1 Like
#135

My crow is behaving a bit inconsistently when it comes to connecting to my norns (fates), with a script that makes use of all it’s inputs and outputs.

Usually when I hot plug it to norns I need to restart my norns script for it to behave properly, but for some reason that doesn’t always work. Sometimes I need to unplug crow, plug it again to norns, and restart the script again.

This norns script I’m writing does not include any code regarding hot plugging/connecting to crow, is there any command I can include to make sure crow connects correctly when hot plugging, or alternatively in the init block to ensure the connection happens when restarting the script? Thanks in advance!

#136

Was wondering if somebody could help…!

I have crows and Norns both running the latest version. I never had this problem with previous versions of Norns/Crow.

My crow output is behaving strangely when running awake (norns), clocked by pamelas new workout.

The crow clock on Norns shows the bpm of the Pam, that’s fine. The output 1 is v/oct and output 2 is the gate which triggers a e Envelope generator.

The problem is that sometimes it skips a beat -and makes these random ratchet rhythms. You can see that on the grid the steps are jumped randomly.

Thank you so much in advance​:pray:t2::pray:t2:

#137

Hello,

Would it be possible to write a Norns script that would tell Crow to run the druid script last installed on Crow?

1 Like
#138

Provided you haven’t cleared the script with ^^c or run ^^f, you can simply tell crow init() which will cause crow to re-run the init function of the script currently in memory.

From norns (including maiden REPL) that looks like:

crow.send "init()"

This is untested, but I glanced at the norns code for connection and it should be enough. If for some reason this isn’t working let me know the behaviour and I’ll see what I can do.

1 Like
#139

Thanks @Galapagoose,

Can I send this from Norns without maiden (without my computer)? Sorry for the ignorance.

#140

yes

pretty much any command that could be sent from druid to crow can also be sent from norns w/o computer*

*if your lua script says so…i don’t think there’s a “livecode crow” script yet that mimics druid or some the m4l devices

#141

Great @glia. Thanks. Would it be the:

crow.send “init()”

saved like a little script in the menu basically? The Crow studies covers this idea probably?

1 Like
#142

Will not lie…I need to go thru em again myself! Usually wrangle crow from my computer not norns so I can’t recall off head

Others could probably chime in with details
cc @dan_derks??

1 Like
#143

Gotcha. This evening I will see if I can save:

crow.send “init()”

as a lua script and put it in the code folder and then run it from Norns menu. If that works that would be perfect for what I had in mind.

#144

you’ll need to wrap it in the norns script init, but this should work:

function init()
  crow.send("init()")  
end

let us know how it goes! :slight_smile:

3 Likes
#145

Edit: Also this isn’t a huge deal. I thought it would be cool to be able to do and more convenient then power cycling crow but it doesn’t seem like it is a simple thing to implement perhaps.

Sadly It did not work.

Norns was running Cyrene with Crow. Crow was putting out clock through output 4. When the init script was selected, crow continued to output clock and did not run the druid script in memory.

Then after unplugging/replugging crow into Norns, Crow had no clock outputting and no script running. Then running init script again, clock resumed outputting out of #4.

After those tests Crow was unplugged and power-cycled. It ran the memory script unplugged as normal.

Edit: Also when crow is running a script from memory and then plugged into Norns it stops running that memory script.

#146

When crow connects to norns, we ‘reset’ the crow virtual machine, stopping any currently running script. This is by design, and was implemented a while back because it became very confusing to people when they tried to run a norns script with crow integration and it was partially still doing the ‘crow-script’ thing, plus whatever the norns script added on top.

We don’t clear the script on crow when connecting to norns, simply deactivating it instead. That script is still available though, hence my suggestion of simply running crow.send "init()" which tells crow to run it’s internal init() function that the crow script should define.

One thing to note, whenever you load a new norns script, the crow environment is reset. This means you could have a script that just executes the above line, but as soon as you reload another script to have norns do anything, it will disable crow again.

From your message it sounds like the above is not working correctly, but I’m having a hard time understand what is happening vs what you’re expecting. If you could run through what happens on crow before you attach it norns, then when you connect to norns, and again when you run the crow.send "init()" command. If you could post the crow script you’re using that’d be super helpful too. I looked at Cyrene and nothing in there suggests it would break this functionality.

I know you say it’s not a big issue for you, but I think it should work, and perhaps there is a tiny fix that needs to be made to make it act as expected.

3 Likes
#147

Hi, I was just wondering what Norns scripts would be best suited to pass clock from Ableton Link to Crow? I’m a new Crow user and unsure about the capabilities of the current scripts with existing Crow support. Thanks!

#148

none needed! :slight_smile:

  • in the CLOCK menu, select source link to get norns synced up with Live
  • scroll down to crow out and select an output to send a pulse at the specified crow out div

oh right, totally spaced on this – could the three line crow init function posted above actually just be getting swallowed? since it sounds like @jasper_ryder is looking for a laptop-less way to do this, maybe it’d be easier to assign a norns key to crow.send("init()")? that way crow is reset at norns script launch and the key press can reinitialize the crow script?

2 Likes
#149

Hi @Galapagoose. Thanks for the reply.

When crow connects to norns, we ‘reset’ the crow virtual machine, stopping any currently running script. This is by design, and was implemented a while back because it became very confusing to people when they tried to run a norns script with crow integration and it was partially still doing the ‘crow-script’ thing, plus whatever the norns script added on top.

I mentioned that crow did this when Norns usb was connected because in my brain it seems like as long as Crow has that usb connection it is in a “Norns” mode and so far I haven’t been able to get crow to run it’s “memory script” when in “Norns” mode.

We don’t clear the script on crow when connecting to norns, simply deactivating it instead. That script is still available though, hence my suggestion of simply running crow.send “init()” which tells crow to run it’s internal init() function that the crow script should define.

Yes yes, now if we can reactivate it as easy from Norns! So far the crow.send “init()” hasn’t fully gotten there for me.

One thing to note, whenever you load a new norns script, the crow environment is reset. This means you could have a script that just executes the above line, but as soon as you reload another script to have norns do anything, it will disable crow again.

I guess what I would do then is initialize Crow’s “memory script” then simply unplug Crow from Norns. That way Crow would be doing it’s internal script and I could then select a Norns script without any issue.

Now that I think about that, if simply unplugging the usb connection between Crow and Norns could re-initialize Crow that would work fine for me.

From your message it sounds like the above is not working correctly, but I’m having a hard time understand what is happening vs what you’re expecting. If you could run through what happens on crow before you attach it norns, then when you connect to norns, and again when you run the crow.send “init()” command. If you could post the crow script you’re using that’d be super helpful too. I looked at Cyrene and nothing in there suggests it would break this functionality.

Yes I used Cyrene in the example because I have been using it a lot lately so I wanted to see if I could go from that script running to initializing Crow easily.

So to try and keep this clear, when I run the crow.send “init()” script, Crow “resets”. Which is to say it stops outputting any script on it’s outputs, but it does continue to output Norns clock signal (on output 4). This happens regardless of running it while having a Norns script running or from “none”. Does that make sense? So Crow just doesn’t go that extra step to running it’s “memory script” it seems.

Now as far as before I attach Norns to Crow; lately I power up the rig all together. Crow powers on with a usb connection to Norns and is in “Norns mode”. If I power up Crow without a usb connection to Norns, Crow plays it’s “memory script”.

The current script I have on Crow is: 0-ctrl crow.lua (426 Bytes)

#150

Ok, I think I understand the issues here. Thanks for posting the crow script as it helped a lot.

Firstly regarding the clock on output 4, this is managed by the norns system itself, not a specific script, so it make sense that it would continue. If you want to turn that off automatically when switching to crow’s internal script, you can set that param directly but I don’t know how to do that (though I know it is possible).

The problem with the script is not that it isn’t running, but that the input[2].change handler has been overwritten by Cyrene. You can get around this by giving your event handler a name, and then reassigning that inside the init() function, like so:

0-ctrl crow. restartable 
function init()
  input[1].mode( 'scale', {0,3,5,7,10}, 12, 1.0 )
  input[2].change = change_handler -- forces update when crow env is dirty
  input[2]{ mode = 'change', direction ='rising'}
end

count = 0

change_handler = function()
  v = input[1].volts
  if math.random(100) > 50 then
    output[1].volts = ((v * 12) + 5) / 12
  else
    output[1].volts = v
  end
  output[2](pulse())
  count = count + 1
  if count >= 5 then
    count = 0
    output[3].volts = v
    output[4](pulse())
  end
end

I looked for a way to reset the Lua environment on crow without triggering norns to capture control, but I think it would require a firmware update, so the above seems the best option for now.

1 Like
#151

Edit: The altered script works very well. Thanks! Would, for example, the bowery scripts require a similar tactic as well?

Thanks @Galapagoose,

I’ll give this a try this evening. :grinning:

#153

A post was merged into an existing topic: ^^ crow 2.0+ help: general (connectivity, device q’s, ecosystem)