One difference that might be worth mentioning is that the newer version can apparently handle keyboards with backlighting (lots of mechanical keyboards have backlighting and it’s a bit harder to find one without), whereas the older version tends to crash with backlighting on.

That obviously doesn’t change anything if you’re not planning on using anything else than the default keyboard :slight_smile:.

1 Like

Hello all! A quick question as I can’t seem to solve this on my end:

Is there a way how to set a vertical fader that has zero value at the bottom, and the maximum value at the top? I can’t seem to find a way to work this out using the command

G.FDR id x y w h type level script

Thank you for your help!

that’s how it should work for faders by default, zero value is at the bottom, max value is at the top (assuming you’re using G.FDR.N to get values, with G.FDR.V you can flip it by setting the fader range appropriately).

in general, for both fine and coarse faders G.FDR.V / G.FDRV uses the range defined with G.GFDR.RN op (it’s shared by all faders within the specified group). this is convenient when you want to use fader values for a specific range, this way you don’t have to scale it each time. by default this range is 0…16383.

G.FDR.N / G.FDRN also return a fader value but the range is defined as:

  • for coarse faders it’s 0…width/height-1 (so if you have a 5 button wide fader the range will be 0…4)
  • for fine faders it’s 0…L where L is the maximum level set when you define a fader with G.FDR.
2 Likes

Sorry to be sophomoric but… Ouch?!?

4 Likes

I had an alarming thing happen when updating my TT to 3.1 last night. After finishing the install, I power-cycled my system with my computer still connected to the TT via USB. This was apparently a bad thing to do, as the lights on all of my modules freaked out! I panicked and flipped my system off but all of the modules stayed on in their freaking out state. I pulled the USB cable and everything shut off. It appears that everything is working fine, but I was very scared that I fried my whole system, and am still worried that things might be damaged in ways that aren’t immediately apparent.

Is this a “of course you shouldn’t have done that” common sense thing? I feel like a couple sentences added to the firmware install instructions could be beneficial here, especially if there’s risk of damaging modules.

Question–is teletype slew curved?
I’ve got a half-decent granular MLR running (thanks to @scanner_darkly’s script of course!) using TT+Grid+STS by 4ms. I use the grid to set a base CV output and then send out some slewed CV over a few seconds to scrub through a “slice” of the song, and then sequence that sixteen times for the whole song… speed of slew determines how fast playback speed will be. It’s pretty effective!
Only little bug is that whenever I jump to an earlier position in the song, it stutters on one position for a second before continuing to move through the sample again. I was curious if this was a problem with sending too fine a CV message (0-.3v over 6 seconds is what I’m in the area of right now) for the STS input to read, or if there’s a little curve at the beginning of a slewed CV signal from Teletype that the STS is getting caught up on. So far I’ve found the STS to be pretty consistent for the most part…

little demo/showin off the bug:

1 Like

I was just looking through the Marbles thread with the idea of transposing its sequences in my head and since I already have a TT and I figured I’d ask here about that process.

If I had one of these 3 channel precision adder with a master cv in (http://leipzigwest.org/?page_id=39), would I theoretically be able to accurately transpose in semitones (say up a fourth) by sending a TT cv value to that input?

Alternatively, I’m sure this could be done also with a TXi pretty easily as well?

Joe Filburns videos about teletype (Teletype Talk) has convinced me to jump on the teletype track.
But I have so many questions that remain unanswered. Here’s a few of them.

  1. Do Teletype come with a keyboard or do you need to buy one separately?
  2. I would like to use Teletype with JustFriends and W/ but how many I2c deviced can I connect to Teletype at the same time? Do I need a I2C-Mult? Is there such a thing?
  3. Do Teletype come with I2C cables?
  4. Is there a document/tutorial with pictures that shows how you connect other modules to Teletype with I2c cables.
  5. Is it possible to damage your modules if you connect the I2c wrong?
  6. Anyone know if any store within EU have Teletype for sale?
3 Likes

Yes, Teletype comes with a keyboard if bought new.

Generally each I2C capable device has at least two headers / two rows of pins so you can daisy chain devices arbitrarily. There is some practical limit, as each extra device and set of wires introduces a little more capacitance, but generally you can do several devices without experiencing issues. It does depend some on how many I2C messages you are trying to send at once. Newer Teletypes (black PCB) are designed to host a few more devices than the older ones (green PCB).

I haven’t had a need for this, but some larger setups I believe have seen improvement from a powered busboard. Until you are trying to do a lot of I2C devices you shouldn’t need this.

No. All you need here is some kind of jumpers for standard 2.54mm pitch pin headers. Lots of options exist for DIYing these or buying them prebuilt, see here.

Actually connecting them once you’ve got cables is very simple: just connect GND <-> GND, SDA <-> SDA, and SCL <-> SCL between each module. I’d recommend reading this thread for more info about how the whole thing works.

Really don’t think so. I don’t recommend touching anything on the back of any module while it’s powered on, since the risk of shorting something to power is increased. I2C lines themselves pose a pretty low risk as the pins are weakly pulled up to digital power when inactive, and pulled to ground to signal. So if you get the pins swapped the worst that will happen is, for example, clock is always pulled to ground and nothing can use the bus. Often if you get the pins swapped, one or more modules will freeze up when you try to use I2C and will need a power cycle.

Can’t help you there, happy hunting.

9 Likes

:grinning:
Thank you very much for answering all my questions.

No need to echo @csboling very fine answers. Just wanted to say: welcome, you’re in for a treat! Teletype is an amazing platform, totally open-ended sequencer, where you get to decide! Ask any questions, it might be a little confusing at first :slight_smile:

3 Likes

There’s one for sale in Härnösand in one of these groups if you’re being Swedish

1 Like

Pyramid Sounds has, but it’s a Norwegian shop so there might be fees: https://www.pyramidsounds.com/

Still not sure if I have understood how to connect Teletype to both a Just Friends and a W/?

@csboling: Generally each I2C capable device has at least two headers / two rows of pins so you can daisy chain devices arbitrarily.

First I thought that this meant that I could connect one row of pins to Just Friends and the other to W/?
But this seems to be contradicted by what’s written on whimsicalraps.com:

Connect your teletype & Just Friends with a 6-pin ribbon cable attached to the 2x3 pin headers on the rear of each module. These headers are marked with ‘ii’ on the rear of both modules.

So now I’m not sure.
I have never seen a Teletype in real life so I have no idea how many connection headers the module have. I can’t find a picture of the back of the module…
Could someone explain to me how to connect both Just Friends (early model) & W/ to Teletype (latest version).
@csboling mentioned “daisy chaining” I not sure what this means in practise so just consider me an idiot and explain it so even I will understand. :grinning:

Also will this type of cable work for I2C?
kabel

Yes.

There are 6 pins on the back of most i2c modules. You only need 3 of those jumper cables to send an i2c message, so the other 3 pins can be used to send the message on.

So you could attach 3 pins from Teletype to JF and then another other 3 from JF to W/ - and messages from Teletype would go to W/ via JF. Hope that makes sense!

yes , that’s make sense.
Thank you very much!

I’m not completely sure what is happening, as I’ve just hooked up a Faderbank, Teletype and 301, so sorry if this should be in a different thread. I have:

M
L 1 16: SC.CV I FB I
$ 1
EVERY 8: PN 0 0
EVERY 8: PN 1 0

I
L 1 16: SC.CV.SLEW I 100
M BPM 126
L 0 3: PN.L I 8

1
SC.TR.P 1
SC.CV 17 N PN.NEXT 1
EVERY 6: $ 2

2
SC.CV.OFF 17 N PN.NEXT 2

My problem: As soon as I include the “EVERY 6: $ 2” in script 1, there’s no trigger on the 6th time script 1 is launched. I can’t understand why. Any ideas?

Might be blocking up the I2C? Try adding a tiny delay to script 2.

Blocking the i2c is a thing? That’s good to know, thanks.

EDIT: When I say “DEL 100: SC.CV.OFF 17 N 12” in script 2, I see clearly 2 triggers (100ms apart) in SC.TR port 1 in my 301. How is that even possible? The ”SC.CV.OFF” port can seemingly be anything, with the same result.

I’m unfamiliar with the operation of SC.CV.OFF. You might need to ask at the OD forum cause it could be a bug.

1 Like