#692

Hi there
First post (cheers to all of you) and a newbie question
I’m diving into teletype and Just Friends for a few days
Is it possible to slew internaly the pattern ?
I’m reading P0 to transpose JF is it possible to slew JF.SHIFT or do i have to use the CV outpout to do this ?

#693

If you don’t use 0 in your sequence you can use if directly on the retrieved value, since it returns true for nonzero values…

#694

It’s not possible directly to slew JF.SHIFT. If you are happy to run the metro script pretty fast, you could approximate this by repeatedly calling JF.SHIFT VV X and incrementing X by a small amount. You’d of course need some additional logic to figure out how to start and stop slewing, but a DIY solution is possible that way.

I suppose it’s worth pointing out you could accomplish this much easier with a slewed CV out to Just Friends’ FM in :joy:

1 Like
#695

For people using a 16n faderbank in slave mode with a Teletype: At which rate do you set the metronome reading the values from the faders ?

I’m experiencing difficulties with my Teletype + 16n faderbank & ER-301 I2C setup.

After 20 minutes approximately, the connection becomes sluggish, some triggers are delayed, there’s a a kind of lag. I’m suspecting the metro rate. Mine was set at 25ms. Even at 50ms, same result.

I’ve made this simple test several times:

First script of TT reads the faders of the 16n and sends them to the ER-301.

L 1 16: SC.CV I FB I

It is driven by a metro set at 25ms (also tried at 50ms)

For this test, a second script triggered by an external source (PNW) sends a SC.TR.P to the 301 triggering a Varispeed player. (120bpm x4)

After 20 minutes approximately it becomes sluggish and some of the SC.TR.P are delayed. The ER-301 plays a hi-hat so it’s easy to hear that there’s a problem. On top of that, the 301 indicates the frequency at which the gate is triggered and i can monitor some abrupt changes.

There doesn’t seem to be a problem with the values of the 16n, they’re still being sent.

I’m trying to troubleshoot this issue at the moment: There are also two TXo on the same bus, I could try to disconnect them maybe…

De-activating the metronome on the Teletype stops the triggers sent to the ER-301 during a second then everything goes back to normal without lag this time.

(Not sure if this question should be posted in this thread or in one of the 16n threads, sorry…)

Teletype possible bug: delaying triggers over i2c
#696

I’ve been using 25ms (and 25ms of slew on the SC.CV) with no problems, but admittedly, I haven’t also been sending SC.TR simultaneously.
Nor do I have anything else connected via i2c.

1 Like
#697

Thanks for your reply.

After a few more tests, now I’m not sure the issue comes from the Teletype…

I’ve just noticed something interesting:

I’ve deactivated the internal metro and now I’m triggering both script 1 (faders) and script 3 (SC.TR.P) with two outputs from Pamela’s New Workout. Each one at a different rate. I’m trying various rates. I even tried very high rates but that created a weird issue:

I have no idea why this happened but now, If I modify the rate of the trigger n°1 (supposed to read the faders) this also affects the rate of the SC.TR.P which is in SCRIPT 3.
If I disconnect the cable triggering the Script 1, Script 3 also stops. Very hard to explain, sorry. :flushed:
If I comment out the line reading the faders in Script 1, the script 3 goes back to its regular duties, at the correct rate.

I’ve also added a TR.P to script 3 in order to be able to monitor the output of Script 3 directly on the Teletype. and this TR is still reflecting the correct rate.

I’d need to do more tests but I think that the ER-301 has its share of responsibility in this situation. Maybe it’s flooded with informations, I don’t know. I should try with a stable release of the 301 firmware and see if it’s happening.

It will probably be hard to reproduce this issue… Could be the I2C bus, or Teletype or ER-301. I’m gonna have to modify my setup ^^

Btw, I’m using the TT beta E27F640 and ER_301 0.4.16

#698

Thanks alanza I’m going to use a slewed CV hardware output :wink:

#699

I’m curious about people’s favorite pairings for teletype. I noticed a few comments above pairing it with pamela’s which seems logical, but my first instinct is that that kind of interaction leads down the path of one-to-one even-to-cause correlation (which is not bad) but is different than the position I want teletype to hold in my li’l system – I’m more interested in creating an eco-system of interaction which it seems like a lot of people are having success at. I’m drawn to the new nonlinear circuits module as a potential way to have a master clock coming from teletype but have manipulatable triggers feeding back into it. Is this kind of clock manipulation something other people are having success with? I’m enjoying swimming thru the murky waters of TT which are so far out of my comfort zone, but am also trying to find my way back to land eventually :stuck_out_tongue:

1 Like
#700

To create an eco-system of sorts, besides the monome stuff, I would gravitate towards Random Source Serge (DUSG, NCOM, SSG) or Make Noise modules that generate gates, like Maths and Function, but also Morphagene/Phonogene.

One thing I don’t see talked about very often is the Xaoc Drezno + expanders. You can feed waveforms in and it will generate unique gate patterns.

And something like Wogglebug or an Ultra Random Analog would be fun too.

3 Likes
#701

nb: this works with TIME cv, but not the FM input - assuming you are in sound range. The FM input jack is AC-coupled in sound range (but not in shape range)

2 Likes
#702

the simplicity and patch-programmability of 1/n are what drew me to it (the serge-esqueness) and it seems like it could possibly do a lot of interesting jittery rhythmic sequences in various time signatures, especially with cold mac too. do you find random or let’s say “influenced” random more interesting to put into teletype to create a sort of self-regulating musical ecosystem? drezno does look wild, but as with random i worry about tame-ability and control – I’m not that interested in making generative music per se

#703

Teletype is event based, where triggers or the metronome cause things to happen. You can add probability and random to scripts to shake things up. I guess it depends on what kind of music you’re trying to make.

Personally, I like Teletype in small systems as putting it in a larger system makes me feel like it’s capabilities are underutilized.

Drezno creates repeatable patterns when fed a waveform. I don’t have one anymore, but the patterns it put out were somewhat unique, like an odd take on a clock divider almost…hard to describe.

1 Like
#704

Quick question…

Can you program LFOs and envelopes in the teletype?

#705

You can set a slew rate for each CV output, which can be used as a building block for creating linear envelopes and LFOs. Support for additional easing functions (slew logarithmically, cubically, etc.) has been proposed, which could have some interesting applications. The TXo expander has its own processor and supports triggerable attack-decay envelopes as well as oscillators which go from slow LFOs to well into audio range and support a range of different wave shapes.

1 Like
#706

Favorite partners for Teletype:

16n Faderbank: adding more real-time control opens things up a bit. I especially like it for sequencing, or changing probabilities. I also frequently use Teletype to just pass the fader values over i2c to ER-301, but that doesn’t really feel like using Teletype.

Strangely, despite the i2c connection I don’t feel like TT and ER-301 are especially close otherwise; once I realized I had patched analog CV between them when I could have just sent an SC.CV :blush:

The main way I use TT is a trigger stream manipulator – an algorithmic gate sequencer, divider/multiplier, etc. with occasional CV for modulation or sequencing, and sometimes using the CV input for S&H/shift register processing of another sequencer. Marbles fits into that very well and makes a good partner. To a lesser extent, other sequencers do too.

6 Likes
#707

Have you tried Triggering your teletype via your TXo? I have a similar setup, but im not triggering drums in my 301 so i might just be missing the lack of sync you’re experiencing because im in a wash of ambience. Ive been using TO.TR.M.ACT 1 1 to activate an independant metronome on TO’s first trigger, then setting it to 25ms with TO.TR.M 1 25 and connecting a cable to my teletype script that reads the 16n faders and controls all the SC.CV. Im curious if you’ve found a solution.

1 Like
#708

Does anyone know how to add a double-click functionallity to the Teletype? For example, connecting the gate out of my Beaststep Pro to script 1, and making it do something different when I double press the corresponding pad?

#709

That’s not really something that the Teletype supports. You could try to hack around it by triggering something on every alternate press, or by checking the time from the last press, and in the scripts that checking triggering a different script if that less than some value, or greater than some value.

1 Like
#710

you can almost get there with something like…

1:
X LAST $
IF < X 150: TR.P 1
ELIF > X 150: TR.P 2

Trigger 1 will only fire on quick double presses, the only problem is that trigger 2 will fire almost every time/too often.

1 Like
#711

Well, I’m now using a solution similar to the one you suggest. The script reading the faders is now triggered at a lower rate by Pamela’s New Workout and not by the internal metronome anymore. That seems to have ameliorated the overall stability and sync but of course this also means having PNW constantly running :-/ I might try using a TXo metro as you do.

1 Like