#370

You only really need the Teletype. I’m including three-wire i2c jumpers with the Telex (if you do both the TXi and TXo I am including a long and a short one). These are different than what ships with the Teletype in that they only take up half of the ports and are designed to hop between modules point-to-point. The bus board should not be necessary - unless you are using the two-row connector across both rows to connect to the Trilogy modules. Even then, you could jumper that off of one of the TELEX i2c ports - they are spaced out a bit so that it is easier to put two connectors on them.

I will say that the bus board does make things easier – especially if you have a complex set up.

Photo was a net grab. There is a whole set of sweater penguins to make your brain melt.

Yeah - I might have to schedule more time in the summer to go see the Penguins when I’m back (if I go back this year - it is a long flight from LA). :wink:

TELEX HANDY LINKS
Module Descriptions | Ordering Process Details | Open Source Repository | Printable Command Reference

1 Like
#371

I figured it wasn’t yours; thanks!

I don’t know if I need to seek them out per se. It’s cooler when things serendipitously cross my path, as this one did.

Have a great trip!

1 Like
#372

@bpcmusic:

Looking at the command ref, I see that LFOs are set in mHz, which is SO awesome!

TO.OSC.LFO 1-n α targets oscillation to frequency α in mHz

For the micro-tuners among us, I’m curious how hard it would be to support similar precision for TO.OSC commands?

1 Like
#373

@ppqq - All Hail the MicroTuners!!!

It depends. What sort of precision would you like?

Right now you can set oscillation in mHz, Hz and the Teletype native integer range (0 to 16383). You can also use the quantizer which supports precise microtunings using floating point tables.

The built-in microtuning support in the quantizer gives you a lot of precision in the output (scales are listed in the Printable Command Reference.) The internal digital oscillators should be quite accurate. As a control voltage source, it is really good - but subject to the variability of the downstream hardware.

Check out the scales in-situ:

You can easily customize the internal scales. I have some python scripts that I use to convert Scala files into the format that the TELEX needs. I’ll get them into the repo at some point soon if folks are interested.

ASIDE
For those that are wondering, I’m doing it this way for performance. We are up against some serious limitations trying to get four oscillators running on the device - which required some serious optimizations. While I could compute the notes from a far smaller set of data (the basic Scala data), in my tests it was far faster to lookup and quantize using these lookup tables. It also avoided processing spikes when switching between scales.

Both the TXi and TXo use these scales, which allows the Teletype to deal simply with note numbers but keep crazy precision from the input to the output.

Let me know if you have other needs or ideas. :slight_smile:

TELEX HANDY LINKS
Module Descriptions | Ordering Process Details | Open Source Repository | Printable Command Reference

5 Likes
#374

Ok, wow. So this all looks really good. For me mHz are probably fine enough but I’ll do some experimenting in Max to be sure — I do this all by ear so don’t actually know! :blush:

Cheers and happy travels!

#375

Timeframe Update

Some folks have been asking the age-old question "are we there yet?” I figured that a good general update was in order so as to properly set expectations.

I’m only at the beginning of the process to get these to your doors. Estimates are tough because things usually take longer than you think they will. Boxing the BETA units was eye opening as to how long that process takes (and what it adds to the cost - but I’m still needing to wait on the final price estimates). I’ve included my punch list below so you can get some idea as to where I am when I announce things on the forum.

This is a very arts and crafts process for me. That is on purpose. I know I could subcontract out of this work to folks and possibly skip some of the steps, but that wasn’t what I wanted to do when I made the decision to approach this project craftsman style. I’m quite enjoying it. :slight_smile: (Besides - I looked into some of that and it was prohibitively expensive at this volume.)

So - how long till the TELEX ships?

Gut estimates here. I have a feeling I can keep pace with reflowing one board a week. So, that is three weeks left just for doing the boards. Maybe three weeks to do the assembly. A week for testing and week to do the accessorizing and boxing. Then, I’ll start gathering shipping details and payments and sending them out the door.

So…the earliest I can imagine is eight weeks from now (that includes the week that I’ll be in Australia). That would put us at 3 April. This is right along with my initial plan (I estimated 8 weeks from the point that I received the PCBs and Panels) - which is why some of you have noted that I’m pretty optimistic.

This said, something could go tragically wrong that throws my work way, way off track. So, I want to reiterate, there are no promises here. This is why I’m not taking payment until things are in boxes and ready to go out the door. I’m a goofball sometimes and could have missed something important or totally boff a part of the assembly process. :slight_smile:

All that said, I can’t wait till these units are in your hands. It is an amazing motivator!

BPCMUSIC’S DETAILED AND LONG-ASS TELEX PUNCH LIST

Updated 29 April 2017

Pre-Build Prep Tasks [DONE]:

  • Separate and Shrink-Wrap i2c Cables [DONE]
  • Paint i2c Cable Sides [DONE]
  • Pre-Cut Teensy Headers [DONE]
  • Pre-Cut Board to Board Headers [DONE]
  • Cut Europower Headers [DONE]
  • Cut i2c Headers [DONE]
  • Cut Jumper Headers [DONE]
  • Panel Prep [DONE]
  • Teensy Prep [DONE]
  • Build Eurorack Power Cables [DONE]
  • Test Eurorack Power Cables [DONE]
  • Fill Little Bags with Screws, Washers and Jumpers [DONE]
  • Print, Cut, Bind, and Fold Documentation [DONE]
  • Stamp my Chicken-Turkey on the Boxes [DONE]
  • Print Box Labels to Keep Stuff Straight [DONE]

Build Tasks [DONE]

  • Prep, Paste and Reflow [DONE]:

    • TXi Top Bottom [DONE]
    • TXo Top Bottom [DONE]
    • TXo Top Top [DONE]
    • TXi Bottom Top [DONE]
    • TXi Bottom Bottom [DONE]
    • TXo Bottom Top [DONE]
    • TXo Bottom Bottom [DONE]

  • Assembly [DONE]:

    • TXo Front Jacks and LEDs [DONE]
    • TXo Mount Panel [DONE]
    • TXo Board-to-Board Connectors [DONE]
    • TXo Bottom Headers [DONE]
    • TXo Teensy Mount [DONE]
    • TXi Board-to-Board Connectors [DONE]
    • TXi Jacks and Pots [DONE]
    • TXi Mount Panel [DONE]
    • TXi Bottom Headers [DONE]
    • TXi Teensy Mount [DONE]

  • Plug-In and Test Each Unit [DONE]

Boxing Tasks [DONE]

  • Anti-Static Package the Unit [DONE]
  • Wrap Units in Padding [DONE]
  • Fill Box With Accessories [DONE]
  • Close Box [DONE]
  • Label Box [DONE]

Delivery Tasks [PENDING]

For each reserved user [PENDING]:

  • Gather Shipping Details
  • Collect Payment
  • Create + Print Shipping Label
  • Fill Out Customs Forms (for International)
  • Arrange for Extra Shipping (for International)
  • Put Units in Shipping Box with Padding
  • Label the Box
  • Take Boxes to the Shipping Center

Firmware Tasks Remaining [DONE]

  • Finalize Module Initial Firmware [DONE]
  • Finalize Teletype Operators [DONE]
  • Pull Request on Teletype Code [DONE]

Bus Board Tasks [DONE]

  • Order Trial Boards from OSH [DONE]
  • Assemble and Test Trials [DONE]
  • Order Production Boards [DONE]
  • Order Regulators and Resistors [DONE]
  • Order Shrouded Headers [DONE]
  • SMD Boards [DONE]
  • Attach Headers to Boards [DONE]

TELEX HANDY LINKS
Module Descriptions | Ordering Process Details | Open Source Repository | Printable Command Reference

10 Likes
#376

Thanks for update, so far everything looks good.
I was about to start hunting for NLC sloths but now seeing that TT can do 0.001hz… This will save me some money and hp.
Also feel inspired by @bpcmusic approach and “journey” so far, feel like I will get into diy stuff myself pretty soon, at the moment its mostly time issue, there’s only 24 hours a day :slight_smile:

2 Likes
#377

Not to dissuade you, but have you seen the new version of Sloth? Pretty amazing.

And who doesn’t need a module with functions Apathy, Inertia, and Torpor?

I have the earlier version of it right here:

1 Like
#378

That new sloth looks indeed nice…
I’ll have to check my usage after I get expanders and see if new sloth would be better way to go, for things I do, thanks for info.

1 Like
#379

Funny, those are usually things I’m trying to overcome in my musicmaking :wink:

3 Likes
#380

In my opinion, a Sloth and a very low frequency periodic waveform are two very different things. The Sloths are chaotic and fairly unpredictable. They’ll roughly follow an attractor pattern but occasionally wander off and do their own thing. They also jiggle a lot while trending toward their next destination.

I frequently refer to the Stasis Sloth as “my silent collaborator”. I like to set up a patch and find a parameter that sounds good being twisted in either direction. I then plug the Sloth into that parameter and let it make the decisions while I manipulate other aspects.

The closest digital neighbor of the Sloth is the Lorenz attractor easter egg in Mutable’s Streams, which was then ported over to Ornaments + Crimes. It would actually be fairly simple to contribute something like that to the expanders after I get mine built. They’re not terribly expensive or complicated, computationally speaking.

5 Likes
#381

Amazing thanks for the update.

1 Like
#382

When considering different functions to port over to the expander, what are the considerations/parameters the team uses to evaluate them (beyond processor impact)? Not that opportunism and community-minded development are bad, but I was curious to know if there was a product roadmap that’s also being followed, against which emergent functions like this are evaluated.

2 Likes
#383

In my personal experience product roadmaps are generally an accumulation of emergent features. :wink:

Not that I’m opposed to hearing any longer-term plans that may exist!

1 Like
#384

That module looks amazing. Seriously considering putting it in queue. Thx.

Yup. TT can also do seconds and minutes for slew and envelope parameters. There is nothing quite like a six hour filter sweep. These might be good features to back-port into the Teletype, btw. I ran up against the millisecond ceiling quite frequently.

Definitely is time consuming. A lot of fun when doing it with a community. :slight_smile:

Ha! I haven’t thought about this much yet. Breaks into three categories in my mind:

  1. Bug Fixes
  2. Optimization
  3. New Features

For new features, the command list is already pretty long, but it is chunky. If you just want to use it as an extended TT - you already know the commands. If you want to do envelopes, you have a small handful to learn. Etc. We should keep it that way.

For the main-line firmware, I think we will want to evaluate additions on usefulness and impact on resources in the unit. With all of the extended features running on all four CV outputs, we are pretty maxed out. But - there is still room for optimization and still room for awesome new features. We can figure out a plan together. :slight_smile:

And, remember, the firmware is open source. So, there is nothing to stop anyone from making a personal version to do something special and even sharing that version with others. :slight_smile:

5 Likes
#385

Yes!

I should have mentioned this; they aren’t even analogous functions, between the the Sloth and LFO on TT I mean.

I use mine in a similar fashion. Just keep it patched to whatever parameter, and let it do its thing in the background.

NLC stuff is just brilliant. I have another five modules somewhere en route right now. I’m basically building a complete NLC instrument.

@bpcmusic: if you’re going to be in Sydney soon, have NLC ship you a kit or two to a local address, and save yourself a little more dough and time (he’s near Perth)!

1 Like
#386

2017-02-09 21.47.02.jpg3237×2428 2.17 MB

13 Likes
#387

I see a Feague!

And a Chopper…

…but…a FEAGUE!

Which module is the Magpie panel for?

Let us know how the TXo and TXi builds go.

1 Like
#388

The Feague would have been finished last night, but I stupidly ordered through-hole J112s instead of surface mount. Also, I ordered a surface mount 4017 for the Squid Axon instead of DIP. So close, yet so far…

The Magpie panel is the Double Neuron: http://modularaddict.com/manufacturer/magpie-modular/magpie-modular-nonlinear-circuits-dual-neuron-panel I enjoyed the single Neuron enough that I wanted two of them. Plus, it’s a great looking panel :slight_smile:

The TXi and TXo came with 3D printed tools for helping with knurled nuts and pots. This will make my life so much easier. Thanks, Brendon!

1 Like
#389

Thanks! I think someone edited your Mouser carts, though. The TelexO seems to have double the quantity for many parts (i.e. two DACs).