#1370

Update for my previous post about TELEXi param knobs returning values that are jumping around: @bpcmusic suggested that the pins might not be making great contact in the header. So I pulled it apart, bent all the pins slightly to make sure they were actually contacting the sides of the female side, and voilaā€¦ seems to be fixed! Thanks again, Brendon!

4 Likes
#1371

Any thoughts about crow expanders? 8 cv outs which can also be triggers and gates? Both 3u and 1u?

I have no idea how to make this, but would love to help if thereā€™s anything I can do.

1 Like
#1372

Crow can speak i2c, so the TXi/o can likely already be used.

2 Likes
#1373

Yes it seems it would only need a Lua file like @ioflow did for the 301, something like to.lua with the right commands :slight_smile:

2 Likes
#1374

Seems there is already TXi support

2 Likes
#1375

I understand that Brian from Orthogonal Devices used the commands of the TXo as a model when he implemented the Teletype protocol for the 301 so it might be very easy to create a TXo.lua based on what @ioflow has done. Just replacing the name and address in er301.lua maybe ? . Tehn wrote that TXo support would be easy to add :slight_smile:

#1376

Iā€™ve read that itā€™s possible with the existing TXi and TXo, but with the same DAC as in the crow you can have the distribution of trigger and cv outs as you like. With a 8 output module, you can have 1 trigger and 7 cv outs, and in the next patch have 5 triggers and 3 cv outs. This is instead of being tied to 4 cv and 4 triggers. This could save space in a small setup, especially in a 1u module, where the teensy have more space to hide.

To shorten it: A CXo would be a lot more flexible.

Is this possible or am I just dreaming of something unachievable? I have a small setup with not so much real estateā€¦

1 Like
#1377

Ah I understand now. I imagine such a device based on a Teensy is technically feasible, it would be nice to have this, specially in a 1u module. I have no idea how they managed to create these versatile outputs. I donā€™t know which DAC Crow uses but having the possibility to switch between trigger output and cv output is truly great and innovative. In the meantime Iā€™ll use one or two TXo along with Crow. Perhaps Iā€™ll have 1 or 2 1u panels made for the TXo and thatā€™ll do the job :slight_smile:

#1378

actually, there is no TXi supportā€¦yet. as i wrote over on the er301 forum, there is a stub placeholder file, but no actual support/ops in it. but it also shouldnā€™t be too hard to add support for TXi/TXo.

4 Likes
#1379

I used crow for the first time today. Promising, but I would certainly benefit from the additional ins and outs using my TXi / TXo.

#1380

@bpcmusic Any chance of a run for TXi and TXo with crow surfacing?

5 Likes
#1381

Was just about to ask the same thing :slight_smile:

1 Like
#1382

Just got my Crow ā€¦ but havenā€™t been home to experiment. All the posts are killing me!! :wink:

Iā€™m not personally planning another run of the TXo/TXi at this time.

Iā€™ve fiddled with a revised, ready-for-manufacture design that, if enough demand builds, Iā€™d consider commissioning a run. Wonā€™t likely be until next year.

13 Likes
#1383

There is ongoing effort to support TXi at a minimum. I donā€™t personally have any TXo hardware to test with so if TXi support is figured out TXo should be doable with community effort.

Unfortunately TX* support is a bit more involved than simply adding Lua code to describe the parameters. There is a GH issue tracking the topic: https://github.com/monome/crow/issues/198

3 Likes
#1384

Maybe we should resort to begging

1 Like
#1385

Would a TXo be possible in 2hp?

2 Likes
#1386

Maybe if it was redone with a microcontroller chip directly on the pcb - as opposed to using a teensy

But thatā€™s probably mean a bit of a code rewrite as well

#1387

that is what iā€™ve been fiddling with. iā€™ve been going the way @okyeron is suggesting without the teensy - a fully integrated, single-side, single board. been considering putting a teensy bootloader on the thing though because i really like the idea of it continuing to be easily hacked without an elaborate toolchain. nothing definitive yet. still thinking about it. but you can imagine that my 2hp experiments (TXn and TXff) were a bit of a preludeā€¦

that said, most of the important code is not arduino but c++. easy enough to get that going without the teensy ecosystem.

no promises here, btw. just talking about what iā€™ve been fiddling with.

13 Likes
#1388

As you mention the TXff prelude - feels like a good point for transitioning into recapitulation and codaā€¦

:grinning:

1 Like
#1389

Considering doing a couple TXiā€™s the DIY route. I know I can get panels from OSHPark, but Iā€™ve never had a panel made. Can anyone point me in the right direction?