Yes indeed! The rear connectors are laid out identically with this in mind.
Unfortunately this is a DIY-only for now. The reality is, ‘available for purchase’ means I DIY one and send it to you 
. I am 100% happy for someone else to provide these to the community (with whatever markup you feel appropriate).
You can reliably stream every 5ms to a remote host on both channels simultaneously, down to ~2ms if there’s not much else going on.
This is something that requires some design work for the i2c framework. I’d love to see proposals for what that sc.lua file should look like to support the other addresses in crow. Also, how you’d like the function calls to work in the crow: ii.sc[1].cv(2,3) or ii.sc.cv(1,2,3) or `ii.sc1.cv(2,3)? How many people have multiple er301s anyway?
(sidenote: for those asking, this is the same question re: multiple jf modules. it makes the interface more complicated even for those with only 1 unit)
Small note - we specifically decided to avoid too many abbreviations in crow as the primary coding environment is a desktop computer screen where character limit is not a limitation. I’m unsure why er301 is shortened to sc, but could it not be confused with supercollider (especially in the norns context)?
This functionality is forthcoming, though we have yet to finish designing just how it should work.
These are some of the scripts that will be provided with druid as an introduction!
Very clean & precise. It’s a DAC (not an audio codec), so there’s no anti-aliasing filters which typically cause these problems. All the outputs can switch their functionality on the fly.
Absolutely. Crow talks ‘volts’ but with decimals, so you can easily make custom scales:
twelvetone = {0,1,2,3,4,5,6,7,8,9,10,11}
output[1].volts = twelvetone[note]/12
microtonal = {0, 0.1, 0.121, 0.999}
output[1].volts = microtonal[note]
justint = {1/1, 4/3, 3/2, 15/8}
output[1].volts = justint[note] - 1.0
