#432

Can someone else verify that quantizer.lua works as it should on the latest crow firmware? I just tried it to verify that it works like i think it does, and it seems that the scaled output is identical no matter what scale is selected.

@mlogger try the hard reset? https://monome.org/docs/crow/update/#forcing-the-bootloader

2 Likes
#433

Thanks. I found code that supports both i2c follower and leader modes in github, so the 2nd scenario (one as leader forwarding messages to followers) seems plausible. But it seems like it would be simpler to have druid connected to several through a usb hub and address them individually. It would avoid all the various i2c contention issues.

1 Like
#434

Yeah I’m working from Max mostly at this point and I’d be thrilled if it became as simple as selecting between two crows as usb devices. Granted I’ve only thought about this in passing but it’s my preferred way of sending/controlling voltage at this point so the more outs the merrier.

I’d be curious to hear how it goes with two, post your updates along the way.

#435

Ha ha. They need to be back in stock again first :confused:

#436

Is the n2v function working? I remember having issues with that a few weeks ago. Maybe try replacing all n2v(x) calls with x/12.

1 Like
#437

thanks, yes I thought of that too. I updated as you suggested, it didn’t change the output. seems to quantize all inputs to a single volt per octave range.

#438

Well… that is exactly what I was experiencing. It is strange as I tried every single script I could find and they all seem to work, except the quantizer. The only thing I could change was to transpose the sequence up in semitones within the script but, nothing else.

Still a mystery!

#439

thanks for the info - I tried the hard reset but it is still showing disconnected.
This is a bit weird because i’ve had everything working without issues. I’m on all the latest firmwares for Crow, Python, DFU etc. but still can’t connect. I’ve tried different ports and different usb cables also. Crow seems locked up. @Galapagoose do you have any idea?

#440

This happens to me once in a while, between crow and a computer or between crow and Norns.
I kind of gave up with Crow + Mac. But for Norns what works for me most of the time is connecting the USB cable to Crow after the Eurorack case has booted. This might be a problem with the I2c bus or the 301, I still haven’t solved this mystery…

#441

I did try Norns Fates also, to see if that would unlock it, but no scripts will connect to it. I had it on the same bus as TT, Ansible, Just Friends and White Whale running Orca’s Heart. I think it’s best to keep Crow separate and just have it connected to 1 Just Friends for Norns on a separate bus, which is what I was planning to do.
I thought I could force the bootloader but that’s not working either. I had been sending code to it from Druid a few days ago and it was fine. I was wondering if it’s some issue with serial drivers on my computer? Or the i2c leaders from Ansible or Orca’s Heart?

#442

You need to ‘force’ the bootloader then run the erase_userscript command (not update the firmware). Something went wrong in an uploaded script that is stopping the system from booting (probably an infinite loop or something).

Please use this custom download_erase_crow.zip (346 Bytes) which will download the current script into userscript.bin then erase it. It’d be great if you could zip and upload the file here!

1 Like
#443

thanks, i ran the script (unzipped and double clicked) but it says “i don’t have appropriate access privileges” even though its set to read/write on my mac on the get info page and ok in the security section…
I also tried to run the file from the command line - no privilege
Then i tried to type in each line of that file into the command line

cd ~/Downloads/util
./osx_linux-download_userscript.command
-bash: ./osx_linux-download_userscript.command: Permission denied
#!/bin/sh
cd “$(dirname “$0”)”
dirname: illegal option – b
usage: dirname path

#444

@mlogger run ls -l after your cd ~/Downloads/util and paste what it says for the .command file

#445

ok - i get this

cd ~/Downloads/util
ls -l
total 8
-rw-rw-rw-@ 1 Jason staff 170 19 May 14:07 osx_linux-download_userscript.command
./osx_linux-download_userscript.command
-bash: ./osx_linux-download_userscript.command: Permission denied

#446

this is what is in the command file

#!/bin/sh
cd “$(dirname “$0”)”
sudo dfu-util -a 0 -s 0x08010000 -Z 0x10000 -U userscript.bin -d ,0483:df11
sudo dfu-util -a 0 -s 0x08010000 -R -D blank.bin -d ,0483:df11

#447

actually I just did it myself.

so ls -l outputs this:

-rw-r--r--@ 1 jmitchell staff 170 May 19 14:07 osx_linux-download_userscript.command

that stuff on the left is the permissions…it doesn’t have execute permission.

run chmod +x osx_linux-download_userscript.command

and that will fix it, you can then run the script like you tried

./osx_linux-download_userscript.command

#448

ok thanks - that’s gets me in

I have more issues now as its not seeing crow

Deducing device DFU version from functional descriptor length
dfu-util: No DFU capable USB device available
dfu-util 0.9
dfu-util: Could not open file blank.bin for reading: No such file or directory

I will try to force the boot loader again

#449

hmm, yea try forcing the bootloader turning the case power off and back on and maybe unplug/plug back the usb cable on your computer. whenever crow has not been reachable that and the erase_userscript command has got me back to a working state

1 Like
#450

ok i forced the boot loader again and got more luck

Opening DFU capable USB device…
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0 …
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Limiting upload to end of memory segment, 65536 bytes
Upload [=========================] 100% 65536 bytes
Upload done.
dfu-util 0.9

only one issue is this - not sure if its important or not :

dfu-util: Could not open file blank.bin for reading: No such file or directory

#451

Hmm not sure on that one. After a power cycle does crow respond like normal?