#1

I got my teletype yesterday and have had a chance to play with it.

I’ve noticed some timing issues:

  1. When clocked by the internal metronome, the tempo changes noticeably when the mode switches between tracker and edit/live modes–it’s not a glitch, the tempo changes enough to cause very audible timing issues when running through a delay.

1a) When in tracker mode, scrolling down through the values causes tempo glitches while scrolling.

  1. There is a significant and jittery lag between the trigger output and CV output. I tested with the onboard “4TRACK” scene and observed c. 700us-5ms of lag between the trigger output going high and the CV output changing. See attached scope trace. I verified that slew is off, which is confirmed by the very crisp CV trace.

I only got out the scope to confirm what I was hearing: small but pretty obvious glissandos at the beginning of some notes.

The other attached image shows the rest of the patch, namely a Model 37 LFO clocking the teletype and no other connections.

Any ideas? Thanks!

20161223_112938.jpg3264×1836 1.34 MB
20161223_114236.jpg1836×3264 1.63 MB

#2

thanks for the heads up-- i hadn’t seen this issues before, and they may have been introduced with firmware upgrades over the many months. will do some testing-- after taking a little break.

1 Like
#3

Was timing tested with previous firmware versions?

1 Like
#4

with initial versions of TT i certainly did not notice timing inconsistencies.

1 Like
#5

Another data point.

Latency from trigger 1 in -> TR A out is excellent at about 50us, and quite jitter-free.

But pulse time is quite variable (see first pic, persistance is turned on): when commanded to TR.TIME A 5, it’s anywhere from 1 to 10ms. When commanded to TR.TIME A 50 (second pic), it’s 40-50ms.

20161226_120109.jpg3264×1836 1.23 MB
20161226_120721.jpg3264×1836 1.5 MB

#6

Might this be connected to the lost command issues of teletype remote?

#7

If the incoming trigger period is less than (TR.TIME - 10ms), the teletype’s trigger output never goes low (or I just can’t see it because it’s so narrow).

In the range of (TR.TIME - 10ms) to (TR.TIME), the trigger output looks inconsistent/glitchy.

Edit: increasing the incoming clock period (i.e. slowing it down) has no effect on the 10ms variation in pulse output time.

#8

watching with interest. . keep up the good investigative work john!

1 Like
#9

More data to support (1) in my original post:

Using the “Triangle Mountain” scene, PARAM knob full CW, trigger out A shows the same duration jitter and runs at about 16.7Hz in edit and live modes (and scene select), and 15.7Hz in tracker mode.

1 Like
#10

This isn’t timing related, but it appears a slowly changing trigger input will fire the input again as the voltage goes back down. I discovered this while attempting to use my Pressure Points’ channel pressure outputs as trigger sources: they reliably trigger the teletype but give a second trigger upon release.

I confirmed the behavior by sweeping a voltage source into the teletype’s trigger input: it always triggers on the up and down slopes.

1 Like
#11

Science!

:sunglasses:

Watching with interest.

1 Like