#669

Nope. I asked for the same thing.

1 Like
#670

by slewing do you mean have it change the waveform gradually when you assign a new value to it? you could do something similar by updating it from a really fast metro script.

2 Likes
#672

This might be a stupid question but this thread is really long and I couldnā€™t find the info anywhere : are these modules available for sale anywhere or is it strictly DIY at this point ?

Thereā€™s a Teletype in my future and having at least a Txi with it would be quite useful I thinkā€¦

1 Like
#673

Itā€™s never been stricly DIY, as @bpcmusic made them all.
I would contact him to know. Good luck !

#674

yeah itā€™d be cool if there was a built in slew similar to other parameters, but not sure if it can handle thatā€¦ i did get good results using a fast metro script reading from ansible levels and using it to update wave shape.

#675

Not at the moment. It shouldnā€™t be super hard to fit in (though we are pretty much out of CPU headroom - see below). Iā€™ve put it on the top of my to-do list. :slight_smile:

Thatā€™s the rub. With 4 oscillators, envelopes, pitch slew, and waveform morphing all going at the same time, we are well beyond the capacity of the little Teensy. Iā€™ve done a lot of optimization to get us this far by doing a lot of ugly fixed-point implementations that perform orders of magnitude faster than their floating point counterparts. There might be some things that can be done around processing rate for different things - though my past experiments left me less than enthusiastic.

Iā€™ve sold out of my run and my backup reserve units. I have a small number Iā€™ve promised out to some folks using reserve components and PCBs - but Iā€™ve been focusing on some life catch-up things and summer travel and havenā€™t gotten to them yet. Might be a few leftover if the folks Iā€™ve promised them to change their mind.

Iā€™ve also mostly costed out what doing a manufactured production run of the Telex would be. Iā€™ve figured most of the details out with a manufacturer/assembler, just need to see if there is enough demand that it would make sense pulling the trigger.

7 Likes
#677

Both TX modules have been my second and third SMD project after the Music Thing Simple EQ (which I can recommend for first trying it out - itā€™s named for a reason and a great module too for a delay feedback path!) Both are working fine and I am very happy that I dared to do it. So donā€™t be shyā€¦just do the impossibleā€¦
:muscle::sunglasses::+1:

https://www.youtube.com/watch?v=7YkbgvRMpW0

2 Likes
#678

Haha, I used to do quite a lot of circuit bending ages ago and have some soldering background (though Iā€™ve never been that good at it) but I have a baby at home and thus not a lot of free time now. DIY modules are definitely cool but itā€™s not something I can afford time-wise these days. :pensive:

Thanks for the answers, I contacted bpcmusic just in case a module becomes available.

1 Like
#679

need a little bit help with troubleshooting my TelexO.
The main functionality is ok, but what really confusing me are the behavior of the LEDs.
If I use 10k cureent limiting resistors, the LEDs are too dark (means not really visible). If I use 100Ohm Resistors the brightness is ok, but if more then 3 LEDs on at the same time, the fuse set off.

Any ideas?

#680

100 ohm is much too low!

Assuming a 5V LED power supply, thatā€™s about 33mA per LED (5V - 1.7Vled / 100 = .033A)ā€“probably the max current those LEDs can handle.

10k is too high: .33mA, which is practically nothing even for very high brightness parts.

Iā€™d try something in the 510 ohm to 1k range (6.5mA-3.3mA).

#681

Hi jnoble

I was confused too by the 10k resistors, but thats written in the BOM.

Regarding the 100 Ohm, I think itā€™s not to less, because the Teensy Vout is 3.3V.
I use yellow LEDs with If 18mA and Vf 2.0 Volt.
=> (3,3V - 2,0) / 0,018 = 72 Ohm

For sure, with low current LEDs, the Resistor is way too low. But in any case 10k doesnā€™t make sense

Maybe @bpcmusic can explain why he choose this value.

#682

The LEDs that I used had very high Luminous Intensity (MCD) (Yellow at 2-3k; White at 14-16k) for the build. This allowed me to keep the overall power draw for the module down when all LEDs were lit.

The parts that I used are here:

I started with 10k resistors and, with these LEDs, the brightness matched the TT quite closely when at full! (I did, however, ultimately implement a logarithmic lookup table in firmware so that the brightness scaled better over the range of values - but that is another story.)

To be honest, I was just getting my head around all of these details at this point in the design process. @Galapagoose was amazingly kind and helpful ā€¦ he nearly carried me through my darkest moments of confusion and ignorance. I went back through our PM thread from the time and here were his recommendations from back then (hope you donā€™t mind my sharing):

Thing is, the mA current rating isnā€™t a ā€˜recommended valueā€™ but rather just a test case at which they measure the mcd rating. 10mcd LED @20mA is the same brightness as 100mcd @2mA, but you draw one tenth the power. This is important to help keep noise low in the power system.

The LEDs you linked are 2000mcd which is super bright, so I think youā€™d be safe starting around 10k for the resistor. If youā€™re looking for a reference point, Iā€™d aim to have the LEDs be at least close to the brightness of TT just for continuity sake.

Also - think about the situation where all 8 LEDs are on full brightness at the same time. You donā€™t want 160mA (@3v3) being drawn just to indicate some levels.

These values are very easy to change after the circuit is built. The tradeoff is very simply between brightness and power draw.

Hope this helps!!!

1 Like
#683

Thanks for the clarification

#684

Whatā€™s your minimum run and retail price at that run size, if you donā€™t mind my asking?

1 Like
#685

I might have missed it, but is the quantizer scale generator code posted anywhere?

It looks like there is enough memory and flash available for hundreds of scales ā€¦

#686

Havenā€™t quite figured it out yet. My earlier pricing for the hand-built run is posted somewhere above (TXo = $175; TXi = $140; iiBackpack = $16). I wouldnā€™t want it to be too much more - but as I was doing things at cost with no labor factored in, I would imagine that pricing would go up to accommodate this.

There has been only a mild demand for additional units since the completion of my first build. With about 200 Teletypes in the wild and another 100 coming (according to @tehn in this post), it might be a while before there are enough new interested parties in the mix to make even a small production run viable. Weā€™ve already reached 40-50% of users (depending on how many are still in the retail chain).

I may not have. Iā€™ll take a look at it in the next few days and kick it out there. It is a simple little python script that takes Scala files and outputs C++ code that can be pasted into the TELEX firmware. It was quick, dirty, and way ugly if I remember correctly. :wink:

3 Likes
#687

Great, that may help some of us microtonal experimentalists. :slight_smile:

I wrote my own quicker, dirtier, and almost certainly way uglier conversion script in the meantime. :open_mouth: Iā€™m getting the same answers for 12TET you did (to 8-9 decimal places), so thatā€™s a good check for both of us. One thing I noticed is that the hints in your scales have some strange spacings. For example, 12TET goes like this: 13 (fist octave, makes sense), 12 (OK), 11(!), 12 (OK) ā€¦ and 12 from then on out. Do the hints need to merely be close? From looking at the source, it appears the answer is ā€œyes, close is fineā€.

While Iā€™m on the subject, it also appears that notes are weighted according to the size of the intervals. In other words, if we had a major triad (0,400,700,1200) the fifth would get nearly half of the notes if we threw random values at it. Or am I interpreting the algorithm incorrectly?

In my own quantizer designs, I convert the incoming CV to cents, divide that by the scaleā€™s span (usually a 1200 cent octave, but non-octave spans are OK) to get an offset, then map the remainder to the number of notes in the scale to get a scale index. The result is equal weighting and consistent execution speed (= very fast on an AVR, the ADCs on those devices are the limiting factor). Both approaches have their musical applications, and I think the ability to select either is a cool upgrade.

Thanks again for all you do! I didnā€™t know we were in such a small club. :slight_smile:

1 Like
#688

today while ordering parts for the next batch i came upon a mistake-- the original batch of TT was for 200, and we did another 100 after that. so this new batch will put it at 400 total.

2 Likes
#689

Just wanted to say: I recently got my teletype and Iā€™d absolutely be up for a TXo and TXi if you happened to do another run.

2 Likes
#690

I would absolutely buy another TXo, and possibly another TXi as well.

2 Likes