I have no experience with Windows but doesn’t the “Add Python 3.x to PATH” checkmark add Python and the place that Python “executables” are installed to to PATH?

yes

And why is running as admin required?

it shouldn’t be, but maybe depends on the windows security setting on the machine being used?

I don’t think there’s a new release firmware with the updated threshold voltage, so updating is probably the same. If you have druid working, you can send ^^v to crow for it to tell you its current firmware version, if this says 1.0.0-something you are currently up to date.

To adjust the threshold for the time being you can either:

  • execute the following after every time you load First (so after every power-on), until a new firmware is available with this change:
    input[1].threshold = 1.0
    input[1].mode = 'change'
    
  • OR modify First.lua, adding a , threshold = 1.0 here, and upload this as the user script. Uploading scripts may also give you some trouble right now, especially if you’re on OSX, this should also be improved in an upcoming firmware + druid update.

Good question, probably if it tries to modify your system path instead of the user path? I have basically always configured paths to Python binaries manually on Windows. I think sometimes it would configure the path for the Python binary but not pip? Really not sure off the top of my head what the Python installer does.

1 Like

Sorry, my question should’ve been more clear. I meant the fact that druid needs to be run as admin. Are regular users not allowed to connect to UARTs/modems?

I find that I am only able to upload (via r mostly, but I’m pretty sure this applies to u as well) once without a power cycle. That is, first upload goes fine, then second one hangs. Maybe once in a while I can get more than one without a power cycle, but I pretty much gave up on trying and just made the power cycle part of the process so I’m not sure how often this happens nor have figured out anything that might make it work sometimes but not others.

Is this the (or one of the) problems that will be addressed in the upcoming update you reference? If not, anyone involved please see my first paragraph for a bug report.:wink:

Speaking of bug reports. Should I just skip the forum and go strait to Github, or is it best to discuss it here first?

1 Like

Oh, nope, I don’t need to do this! One possibility is if you run it in a command prompt that defaults to a location like c:/ or c:/Windows it would fail to write log files or read scripts. Running from the user’s home directory ought to be fine.

Yes, this is hopefully much improved by some changes that should be in the next update. In particular you may find that it works better if you convert line endings of script files to \r\n instead of just \n, going forward druid will do this conversion during upload. Still not sure why but this seemed to resolve a lot of problems in my tests. There is also a change on the crow side that may improve this behavior.

Yeah, checking the GitHub issues pages for crow and druid may help to figure out if a problem is already known. I would say discussion here is probably good for figuring out weird behavior, if you have a reproducible bug report for a new problem then filing a GitHub issue sounds good to me.

1 Like

4 posts were merged into an existing topic: ^^ crow help: max and max for live

Thanks for this. Can confirm sending the command from Druid got First responding to my various gate sources. Happy it’s not broken :sweat_smile:

closing the loop: the default threshold for input changes is being updated to 1.0 in the upcoming release. this manual adjustment for ^^First to respond as expected to certain makers’ gates will not be necessary by this time next week!

2 Likes

FWIW - I switched to using \r\n for my scripts but it did not help, I still need to reset crow every other upload – ^^r usually works, though every once in a while it seems that only a power cycle will do.

Hi all,

I’m trying to get crow to talk to W/, no luck.

My idea was to try to clock W/ with Ableton to make a tempo-synced delay — any idea how I can accomplish that?

Thanks!

2 Likes

Dang this was exactly one of the things I was going to build in my livestream today! Postponed until Monday -

But until then here’s a high level overview of the M4L logic.

you’ll need to grab the ableton tempo and turn it into bangs at your chosen clock division - see the ^^outs device for an example.

Then you will want to send ii.wslash.cue( 0 ) to crow on every bang (prepended with tell_crow) - this will reset crow to the nearest cue point. Equivalent to WS.CUE 0 on TT

4 Likes

Thanks!

What is tell_crow? I don’t think I’ve seen any documentation on this.

1 Like

it’s all wrapped up in the [crow] object’s help patcher inside the crow-max folder from the github repo and also mentioned in the Max scripting section of the crow FAQ :slight_smile:

suuuuper duper specific to working in Max and m4l, no reason for you to have seen it anywhere else. feel free to ping the ^^ crow help: max and max for live thread for additional help!

3 Likes

Okay I figured it out I think… For whatever reason crow -> JF -> W/ wasn’t working. Connecting W/ directly to crow seems to establish the connection.

1 Like

Trying to upgrade firmware to 1.0.1. I put my crow into crow dfu bootloader, double clock on window-firmware_update.dat and get a cannot open device. Ask dfu to list devices and it say cannot open device. Thanks for help.
image

Fixed. Windows people need to update USB driver. Instructions on GitHub here

Is it possible to update Crow from a Raspberry Pi / Norns connected to Crow ?

Sorry if it’s been asked before, I haven’t read the whole thread… :confused:

I don’t have access to a computer running at least OS X 10.10 at the moment (I only have an old MacBook and 10.7 is the max) therefore I can’t install the latest Python, Druid etc.

NB: I can install DFU utils on RPI but I don’t know how and if I can run Druid on RPI in order to put Crow in Bootloader mode. Do you know if it’s possible ?

1 Like

Did you get an error running pip3 install monome-druid and then druid? I would expect this to work, if the Linux update instructions fail on RPi specifically it would be good to know. Edit: on my RPi pip puts the binary in ~/.local/bin, which was not on my PATH by default, you may need to add this for the druid command to be found.

I would also expect this to work, homebrew might not officially support 10.7 anymore but it should be possible to get Python >= 3.5 installed.

1 Like

Thanks for your reply. No I didn’t get an error because I didn’t know it was possible to install Druid on RPi, I might have missed that in the docs, is Python pre-installed on Stretch or do I I need to install it before installing Druid ? I will try again tomorrow. And about the Mac, I’ve tried to install Homebrew on this old machine but without success, I’ll try with an older version :slight_smile:

Edit
You’re right, on Raspbian I need to run Druid with ~/.local/bin/druid

This is the install process I used, in case it’s useful for anyone:

Python 2.7 and 3.5 come both pre-installed on Raspbian Stretch, however by default it will use 2.7, so:

sudo nano ~/.bashrc and add the following line at the end of the file.

alias python='/usr/bin/python3'

save and reboot

Now python --version returns Python 3.5.3

sudo apt-get install python3-prompt-toolkit

sudo apt-get install python3-pip
pip3 install --upgrade setuptools
pip3 install monome-druid

Run Druid ~/.local/bin/druid

Aliasing one program to another is probably not the best thing to do. Any python2 specific script or application will probably fail after aliasing python to python3. Better to just leave it as is and use pip3 to invoke Python3’s pip specifically.

If you are going to run druid from you user’s local bin directory (which I don’t understand how that would work with the pip install command you posted, unless pip is somehow patched by debian to always install to your user’s home instead of systemwide) it’s easier to just use pip3 install --user monome-druid.
You’d still need pip for python3 installed of course if that’s not the case by default.
The setuptools upgrade should no longer be necessary.

1 Like