#12

I have a working zero-crossing based pitch detector (ie ‘frequency counter’). It needs more testing, but fundamentally is only useful for tracking single-cycle waveforms – it will not work for general audio signals. The main use is as a tuner, or part of a volt-per-octave calibration system. This works up to ~20kHz as it has a dedicated digital input.

In terms of a general pitch tracking system, I don’t have the knowledge to build a smarter system. The 1.5kHz sample rate is likely the main limitation, but also, processing power isn’t limitless. I’d be very happy if someone with those DSP chops has the interest & time to add this feature!

9 Likes
#13

Awesome. Thanks for the clarification, and moreover continuing to develop this amazing module!

1 Like
#14

This is a “wow!” release!

Thanks to everyone who contributed to this awesomeness!

1 Like
#16

I’m Pumped this is great :+1:

#17

Not sure which Crow thread to put my appreciation in, but I’ll start with this one!

  • Received the Crow, today, here in London, having been sent on 14th, two days ago! And however the DHL works, I was able to pay the customs charges online so no delay because of that. Thanks @tehn for that!

  • Updated to the JF 4.0 Firmware, super easy

  • Connected all the I2C

  • Installed Python, Druid etc

  • Installed the M4L devices (thanks @dan_derks)

This took me less than 20 minutes in total, everything works perfectly, the module is perfect, adds a tremendous amount to the my rack. So thanks all.

Oh - and I should have understood this, but it was a nice surprise to be able to use the JF Synth device, and the Dual M4L devices simultaneously. Presumably the JF is just a pass through on the I2C bus.

12 Likes
#18

Don’t worry, I saw it

3 Likes
#19

I just received a Disting EX. Can someone point me in the right direction to work on adding ii support on crow? What do I need to do beyond creating a Lua file like the following?

#20

Creating a .lua file is all you need to do.
The name of the file must match the module name. disting.lua for example
Then you add each commands and arguments with their types (s8 etc.)

#21

There’s detailed instructions here, but all that’s required is the lua descriptor file. We generate all the ‘real’ code from that file.

If you don’t want to set up the build system, you can open a github PR with the monome/crow project, and your changes will be compiled (or compilation errors will be shown), and a .zip ‘Asset’ will be created.

1 Like
#22

Great, thanks @Galapagoose and @Nordseele!

1 Like
#23

I just received a Disting EX. Can someone point me in the right direction to work on adding ii support on crow? What do I need to do beyond creating a Lua file like the following?

I’m working on adding Disting EX support on my fork here: https://github.com/CarlColglazier/crow/blob/distingex/lua/ii/disting.lua

I’ve tested that it can at least send messages that are received on the other end. I still need to work through and test the remaining commands.

2 Likes
#24

This looks nice Unfortunately I had to sell mine because it was just too hard to update it. I may buy it again now that already has 2.0 load up on it.

#26

Is it possible to create a Hz/V - V/Oct converter using Crow? It would be nice to connect my MS10…

#27

I’m not super familiar with the Korg Hz/V specs, but if it fits within the -10v to 10v range, I don’t see why not. Even it doesn’t, you can probably just put an attenuator + offset in front of it.

#28

The Keyboard CV Out reads 0-8V. Can I just try to scale the voltage or do I need to use more to correct the range. Reading about log amps and so on which are used in converters, going from linear to exponential, but perhaps I’m making this overcomplicated :slight_smile:

#29

Excellent. Linear to exponential sounds right. I’m not sure exactly how the math works out but it’s probably something involving log, division, and a constant offset. If I was doing this, I would probably check at least 3 voltages at octave distances (i.e. lowest C, the C one octave up, and the C two octaves up), and just crunch the numbers until those inputs output 1V apart on the other side. There’s probably not much code to it.

The druid REPL lets you grab input voltages and try out the math really easily. This will probably come in handy too:

2 Likes
#30

Thanks for this, very helpful!

1 Like
#32

Crossposted from i2c thread - can anyone help?

Still having issues with i2c chain

I have:
Ansible
Crow
Just Friends
W/
DistingEX
Sweet Sixteen

All connected to TxB so each device is attached to a separate group on the TxB

So from top down

connection
blank 3 pins
connection
blank 3 pins

etc

Ansible and W/ refuse to work but everything else seems to play together fine. This happened the same when I was piggybacking - thought the TxB would help so must be something else.

I clearly have the cables connected okay as Crow gives errors if that isn’t the case.

Any ideas?

#33

Anyone here using a chromebook to host their druid environment? Or does anyone have one willing try it out? Still can’t get mine to work and it would be helpful to know I’m not the only person here having no luck with this OS w/ druid.

#34

Hi All-

Would it be possible to alter the the outs–>clock m4L device to have an option to hold a gate high when the transport is running? Similar to the way Ableton’s CV Clock Out amxd device does?

Essentially I want to use crow to send a run gate to Pam’s from my computer. It’s early and I’m under caffeinated and likely overthinking this.

4 Likes