#83

Hmm, not sure, but you can always do it this way https://monome.org/docs/crow/update/#forcing-the-bootloader

#84

Yeah sounds reasonable. I’ll investigate as well! I am using VS Code on a Mac though, to be clear. I would imagine it behaves similarly in both environments, assuming it’s some kind of default line ending setting.

#85

Following up as I’m still dealing with this issue. Running ^^b results in Lost Connection (I am on 1.0.0, just tried reinstalling the firmware to see if it would change anything—no luck there yet), ^^c, r, u, ^kill, all lock up crow up and I have to restart it. Any of those commands result in:
lua bootstrapped
input loaded
asl loaded
and nothing else; druid stops working. Can type commands but nothing responds besides q, which still closes the program as it should. The problem is replicated in derwyyd (awesome app by the way) in addition to iTerm and good ol terminal. Basically all that I can use my crow for currently is ^^v and a couple live commands. I wonder what on earth I could have done ¯_(ツ)_/¯

Keep on crowin’ y’all

#86

Apologies for the lacking instructions here. We’ll get the bootloader page cleared up a little. In the interim:

When you run ^^b in druid, it will ‘lose connection’ because when crow enters bootloader mode, it stops being a usb ‘modem’ connection, instead becoming a ‘dfu’ device (which druid doesn’t talk to).

The steps should be:

  1. in druid: ^^b to tell crow to enter bootloader mode
  2. in druid: q to quit and return to terminal
  3. in terminal: ./flash.sh to upload the new firmware
  4. in terminal: druid to rerun druid
  5. in druid: ^^v to confirm the firmware version is 1.0.0

I’d love to get the bootloader (including fetching firmware) into druid, but that’s a bigger technical challenge than it might seem!

11 Likes
#87

No need to apologize, this has been a great lesson in terminal alone! Good times.
I’m still getting this darn issue with all the libraries not loading though! Here’s a demonstration, crow freezes up and druid stops responding to commands after doing anything with script loading. I printed the script I had running last before it broke down. Haven’t been able to replace it.

10%20AM
Screen Shot 2019-10-13 at 9.11.10 AM.jpg1470×1998 165 KB

#88

I was having similar issues with freezing and scripts becoming unresponsive. I had a number of things on my I2c Bus as leaders, like polyearthsea on WW, TT, (and is crow a leader on I2c?). I disconnected crow from the I2c bus and then everything was working smoothly. I might get a second powered I2c board to segment out what is connected to what.

2 Likes
#89

You could try ^^c/^^clearscript after restarting crow, that should clear the script and allow you to work on other scripts again.

1 Like
#90

no dice! here’s me resetting the crow a couple times then running ^^c (also trying to run sketch):

59%20AM
Screen Shot 2019-10-13 at 11.14.59 AM.jpg752×1692 158 KB
42%20AM
Screen Shot 2019-10-13 at 11.16.42 AM.png510×744 57.3 KB

really appreciate the help :slight_smile:

#91

One thing I’m struggling with is finding a centralized place to see all the commands I can run via druid for live coding crow. I tried this from the crow study, but it didn’t work:

output[1].action = “{ to(0,0), to(5,0.1), to(1,2) }”
output[1].execute()

It gives me a string eval error message.

Something like this seems to work fine:

output[1].volts = 3.33
output[1].slew = 0.1

1 Like
#92

Check out this reference page.

I believe you grabbed this from the Norns/crow study, and removed the crow. prefix. In other cases, this would be a fine way to adapt a crow command on Norns to crow… but on Norns, you have to wrap asl actions in strings before sending them to crow, whereas on crow you do not

When directly coding on crow (either via a script or live in the druid REPL), you do not wrap asls in quotes:

output[1].action = {to(0,0),to(5,0.1),to(1,2)}
output[1]()
1 Like
#93

Thanks for the help. I don’t see a URL linked for ‘this reference page’ unfortunately.

Seeing some stuff on https://github.com/monome/crow that is similar to your example.

#94

Edit: fixed the link above @Jonny

1 Like
#95

I may be missing something but I don’t see a link from the Crow GitHub to https://monome.org/docs/crow/reference/

It’s entirely possible that I’m overlooking it, but this feels to me like an example of why a unified INDEX would be a great resource…

1 Like
#96

There isn’t and there shouldn’t be, all relevant documentation pages are linked to from the main crow documentation page https://monome.org/docs/crow/

The stuff on GitHub shouldn’t be relevant for someone who just wants to read the docs. What’s currently still there on GitHub will probably be cleaned up.

#97

Forgive my ignorance but do you mind explaining the difference? How would you categorize the stuff on GitHub?

Thanks!

#98

I usually start here for monome documentation:

https://monome.org/docs/

It’s sort of like an index.

I do think that the live coding aspect of Druid + crow could use some studies or demos but I see now that the reference is linked in the main crow page.

#99

Hey everyone, I’ve just received my crow and tried to run First with my two mangroves. I don’t get any pitch or envelope data being sent. Clock into input 1 doesn’t do anything. What am I doing wrong?

I was able to run Druid and check the version. Got the bootloader to work, and tried to recalibrate using the cal.test() command. But no luck.

#100

Seems that some clock sources (notably Make Noise?) are not successfully triggering First because currently the default threshold voltage is 0.5V, which is lower than the “off” voltage of some gates. Can you try adjusting this by running:

input[1].threshold = 1.0
input[1].mode = 'change'

and see if you’re able to clock First after that?

1 Like
#101

I see that now too. Thanks!

1 Like
#102

Hi there, thanks for your reply! I’m trying to clock using a square wave from Just Friends. I ran these commands. I see input[1] = 1 at the top of the Druid console which switches from 0 to 1 maybe relating to my square wave?

I am getting also very very scratchy tones from my mangroves. I dont seem to get an audible tone unless I move the barrel down as far as it will go.

When I try to resolve this by recalibrating and running the cal.test() cmd I see, despite jacks being unplugged:

Calibration failed. Unplug the below jacks & retry!
out 1
out 2
out 3
out 4
Using default calibration