#103

Can you run even a one line command like print(2 + 2) or output[1].volts = 5? If that works maybe you can try creating a minimal script and running that, like

function init()
  print('caw!')
end

When you try running a script, what happens? druid freezes?

#104

ran them all and druid doesn’t freeze, but doesn’t run anything after i entered the code either

#105

Thanks for the video, that’s super helpful. What’s odd is that druid shows <crow connected> when you start it — this should mean that a crow was found and it’s in normal mode and not the bootloader – but you’re not getting any response from crow. In your earlier screenshot the lines starting with repl:1: are definitely being sent back by crow’s Lua evaluator.

Is it possible you have multiple druid windows open? This can result in weird behavior where more than one program is trying to read crow’s output. Currently druid doesn’t know how to detect / prevent this.

#106

just quit the current druid one, quit terminal, reopened and still having the same issues

#107

Huh! After opening druid, maybe turn crow off and back on (you may have been trying this all along)? I wonder if it is stuck in some Lua code from a script and can’t respond to input. You should see something like:

<crow connected>
<crow disconnected>
<crow connected>

where the first crow connected message is the message druid shows on startup when it detects that crow is there, then disconnected / connected happens when you turn crow off and back on. After that maybe see if you can run something simple like print(2+2) again?

1 Like
#108

by the way, thanks so much for following this so closely i really, REALLY appreciate it haha

just tried that and still no results …

Screen Shot 2020-08-27 at 7.43.38 AM
Screen Shot 2020-08-27 at 7.43.38 AM666×561 21.7 KB

1 Like
#109

This is working, the “No user script” and “Calibration failed” messages are coming from crow. But it sounds like when you try to run a script like r druid-master/quantizer.lua that druid freezes and then crow becomes unresponsive? Can you upload the quantizer.lua file here that you’re trying to run so we can confirm what it looks like? Maybe there’s something in the file that’s confusing crow?

#110

heres the script, replaced the bad version but still freezes druid

quantizer.lua (1.8 KB)

— quantizer example
– s wolk 2019.10.15
– in1: clock
– in2: voltage to quantize
– out1: in2 quantized to scale1 on clock pulses
– out2: in2 quantized to scale2 on clock pulses
– out3: in2 quantized to scale3 continuously
– out4: trigger pulses when out3 changes

– nb: scales should be written as semitones (cents optional) in ascending order
octaves = {0,12}
Persian = {0,1,4,5,6,8,10}
dmpen = {1,5,7,9,12}
csus = {1,6,8}
majorTriad = {0,4,7,12}
dominant7th = {0,4,7,10,12}

– try re-assigning scale1/2/3 to change your quantizer!
scale1 = Persian
scale2 = dmpen
scale3 = csus

function quantize(volts,scale)
local octave = math.floor(volts)
local interval = volts - octave
local semitones = interval / 12
local degree = 1
while degree < #scale and semitones > scale[degree+1] do
degree = degree + 1
end
local above = scale[degree+1] - semitones
local below = semitones - scale[degree]
if below > above then
degree = degree +1
end
local note = scale[degree]
note = note + 12*octave
return note
end

– sample & hold handler; sets out1 & out2
input[1].change = function(state)
– sample input[2]
local v = input[2].volts

– quantize voltage to scale
local note1 = quantize(v,scale1)
local note2 = quantize(v,scale2)

– convert semitones to volts and update out1 & out2
output[1].volts = n2v(note1)
output[2].volts = n2v(note2)
end

– streaming handler; sets out3 & out4
input[2].stream = function(volts)
– find current quantized note
local newNote = quantize(volts,scale3)

– check if quantized voltage is equal to current voltage
if n2v(newNote) ~= output[3].volts then
– if not, update out3 to new voltage and pulse out4
output[3].volts = n2v(newNote)
output4
end
end

function init()
input[1].mode(‘change’,1,0.1,‘rising’)
input[2].mode(‘stream’,0.005)
print(‘quantizer loaded’)
end

#111

Hm, not sure, it looks basically okay but I’m not able to test with crow right away. I would say maybe give some small test scripts or some other Bowery scripts a try? There have been a lot of changes in crow v2.0.0 and I’m not sure if everything on Bowery has been updated / tested.

1 Like
#112

every other patch seems to be working haha

2 Likes
#113

I think the Bowery quantizer is broken.

i submitted a pull request on the bowery repo with the simple quantizer above. https://github.com/monome/bowery/pull/7

there is a ton of stuff buried in posts. it would be good to update the bowery repo.

3 Likes
#115

So I sold Crow, not because I didn’t like it but updating the firmware was too difficult. No matter how long I spent, it never worked. Maybe make a easier way to get the firmware in and I’ll buy it again.

#116

hello!!

i wasn’t able to find this anywhere on the thread however its troubling me — i am having a difficult time understanding how i could recalibrate my jf while connected i2c to crow! i am trying to tune it to play with another synthesizer, but it i am having a tough time getting them to tune together. anyone have any ideas if there is a way to recalibrate jf while being sequenced via i2c?

i am running the latest norns firmware, crow firmware, and i am using patchwork to sequence! any help is appreciated!

#117

Thank you to everyone on this thread – I just received my Crow last week, and the info here has helped me tremendously.

One of my goals was to connect my 16n faderbank to control different parts of scripts on Crow via i2c. I picked up a TXb and some jumper wires, and to my surprise it Just Works.

Now I’m scratching my head, trying to learn Lua and how to code the ideas I have, but I love how easy (relatively) its been to set everything up physically

2 Likes
#118

Were you ever able to get this sorted? I’m noticing the same thing with my
Piston Honda III. It is not picking up the 1v/oct from output 1 of the crow.
I think someone else had the same issue with their PH as well. My other oscillator (Just Friends) picks up the output pitch voltage just fine.

#119

Do you know (roughly) the memory limit? I apologize if this has already been answered, but searching for “RAM” and “memory” yielded only this thread.

#120

Crow’s microcontroller has 256kB of RAM of which ~150kB is available to the Lua environment.

1 Like
#121

hi, i need help with my Crow. it was working fine prior firmware 2.0 (been following maps with trent and doing a bunch of stuff with it on druid without problem).
i’ve updated the firmware to 2.0, and updated druid successfully a few months ago. since then i haven’t use crow for a while up until today. (edit: just remembered, i did use crow once after firmware 2.0 update with norns (cheat codes) sending external clock to crow input, and it was fine.)

at first, i was trying to use it in ableton with max for live device, but somehow it can’t get connected.

then i tried to open druid, but always get ‘crow disconnected’ no matter how many times i tried. (quit the druid & open again; plug/unplugged the usb cable; and tried several different usb cable)

then i tried to do force bootloader & reinstall the firmware, but with no luck. i get message ‘dfu-util: No DFU capable USB device available’.

update: i tried to run force bootloader again, then run ‘dfu-util -l’
i got this message:

Deducing device DFU version from functional descriptor length
Found Runtime: [05ac:821a] ver=0042, devnum=6, cfg=1, intf=3, path=“250-1.1.3”, alt=0, name=“UNKNOWN”, serial=“UNKNOWN”

(i’m on macos 10.13.6)

UPDATE: been trying several times to do force bootloader, and then run erase_userscript.command, but with no luck at all.
always get this message :

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Deducing device DFU version from functional descriptor length
dfu-util: No DFU capable USB device available

can anybody help/guide me how to solve this, please ? @Galapagoose
thanks

#122

Maybe you’re already doing this, but for me (running Ubuntu Linux) it turned out crucial to run Druid as administrator (i.e. “sudo druid” from the command line - I guess it’s not very different on macOS). Otherwise I also get the crow disconnected message.

#123

just tried it, unfortunately, no luck still get crow disconnected. but thank you though for the suggestions.
the thing is that bug me, this just happen yesterday, never had any problem before.