#119

I’m truly embarrassed to be asking this here, but maybe someone can throw me a bone. Are there any other “just crow” apps besides the one it ships with? Where do you find or upload crow apps? I see all sorts of Norns apps that basically use crow as CV output - is there anything else cool currently to do with it?

1 Like
#120

I think the best way at the moment is to look for the #crow tag in forum topics: https://llllllll.co/tag/crow - of course that will also include things that use or require norns et al.

I am a bit fuzzy on this myself, to be honest. The crow ecosystem is looser than norns/dust. There is the bowery repository which may have been intended as an umbrella for these apps, but as yet it doesn’t seem to include any beyond the core examples.

1 Like
#121

There are quite a few scripts for just crow. You’ll want to get familiar with druid. From druid you can upload scripts. There is a repository called “bowery” with a good amount of crow scripts in it.

Start here: https://monome.org/docs/crow/

#122

The coolest thing to do is to make your own scripts!

1 Like
#123

Yes, this is the real joy of crow!

#124

hi

this is a great question…check the thread below for druid scripts (crow standalone apps that dont require norns/max/something else to function)

#125

Thanks so much! I feel like this cleared up some real confusion on my part.

#126

i guess input[n].mode( ‘change’, …) would allow the same but only for a given voltage precision, though i could add lag in supercollider to make up for any “stepping” you might encounter depending on the rate of change.

actually this isn’t correct, i thought change worked by any voltage change past a given hysteresis, but that doesn’t appear to be the case. fwiw polling does the trick good enough for me right now :stuck_out_tongue:

#128

I’m having a little trouble getting the input scale quantization mode to work. Any ideas?

crow.input[2].mode("scale", {0,2,4,5,7,9,11}, 12, 1.0)
crow.input[2].scale = function(new_note) print(new_note) end

I get this back in maiden:

    ### SCRIPT ERROR: init
/home/we/norns/lua/core/crow.lua:94: attempt to concatenate a table value (local 'a')
stack traceback:
	/home/we/norns/lua/core/norns.lua:136: in metamethod '__concat'
	/home/we/norns/lua/core/crow.lua:94: in field 'mode'
	/home/we/dust/code/shahin-seq/seq12.lua:91: in global 'init'
	/home/we/norns/lua/core/script.lua:105: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:137: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
#129

You can’t print ‘new_note’ directly be ause it’s a table. See the crow docs for the contents pf that table, or use the print function in tabutil (i forget the name exactly) to explore via the repl.

1 Like
#130

tab.print(new_note) should do it!

2 Likes
#131

Thanks @Galapagoose and @dan_derks. It doesn’t help when the debug statements add to the confusion. :wink:

If I remove the print statement and have just the line below, I still get the same compile error.

crow.input[2].mode("scale", {0,2,4,5,7,9,11}, 12, 1.0)

#132

Appears to work if I call in druid however.

#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.