#97

A couple of retrospects on Episode 8.

  • I’m not sure I explained the fader type as well as I wanted to - why fader type 0 was my choice for the faders in this script. For more info on this, have a look at the grid operators github page @scanner_darkly put together. It lists out all of the available choices for fader type.

  • In the metro script, we used a global variable X to store the last known value of the param knob for comparison to the current value. I believe metro also has its own local variables I, J, and K. We probably could have used one of those locals and conserved a global. The variable is not used by any other scripts. Maybe not a big deal since we still had plenty of globals available. On the other hand, there are two empty scripts left in this scene, and all of the patterns are empty! So there’s room to add more to this scene.

#M
IF NE X PARAM: $ 1
X PARAM
2 Likes
#98

I just started watching Joe’s video series. Excellent so far!

Do new teletypes from monome.org come with the i2c board/connectors?

Are they in stock at monome.org now?

Thanks.

1 Like
#99

The newer revision of Teletype has 2 I2C headers. There is no additional board required, and further devices on the I2C bus are typically daisy chained.

The older revision of Teletype needed an additional pull-up resistor “backpack” board to help stabilize the I2C bus.

#100

Meaning the newer versions are less reliable?

#101

No, quite the opposite. Pardon the unclear phrasing.

1 Like
#102

Thanks again for this amazing series Joe! Just wondering: in episode 6 with the binary operators… why “L 0 7: $ 1”? I understand you’re calling script 1 7 times in a row, but I cannot figure out why 7 times… What’s the significance of that number?

PS if you’re taking requests, turtle ops is something I have not been able to figure out :stuck_out_tongue: These 8 episodes are already a treasure trove, you’re the best ! <3

#103

Glad they’re useful!

L 0 7
actually calls script 1 eight times. Does that help? If not I can take a closer look. Just can’t remember exactly what I did in that episode off the top of my head.

I am planning to make some more of these as soon as time permits, so I’ll take the turtle suggestion into consideration! Thanks for the idea.

2 Likes
#104

Right, thats what I meant to say! Doesn’t help clear it up tho haha, if i call it 7 times (L 0 6) or 9 times, 22 times etc theres no noticeable difference but if i only call it two or three times it doesnt work.

I’m guessing this is somehow related to binary digits: every call fills in one of the binary digits so you need to call as many outputs as you have basically? If you’re only using the 4 trigger outs you on the TT then you only need to call it 4 times and you can use numbers up to 15 (which would trigger all 4), but you would not be able to use 16 to trigger a 5th event because you’re only using 4 binary digits… I don’t know if I’m using the correct words to describe these things, I hope I’m somewhat clear—is that what’s happening?

#105

Yes, you’ve got it right.

L 0 7: $ 1 calls script 1 eight times. Eight in this case is the total or maximum number of kit pieces or trigger outputs. Each time we call script 1, it is evaluating a different bit of the value in the same pattern location. If that bit is set, we send a pulse to the corresponding output which triggers that kit piece.

So, yes, using only Teletype you max out at 4 (although you could potentially go up to 8 with a little extra code by using the CV ports to send triggers like I showed in Episode 1). Or if you had ansible connected in teletype mode, you could use the script as is and ansible’s 4 digital outs would respond to TR.P 5-8. Or with a little extra code you could also use TXo for 4 additional outs.

1 Like
#106

@EqualTemperament just wanted to let you know i have been going over your video tutorials over the holidays. Really enjoying the learning process. I think im going to make some great space saving replacing modules in my case with my teletypes :slight_smile: Thanks again!

2 Likes
#107

Got back from holidays…updated my teletype, and like an idiot i deleted all the work from the last 3 weeks.
Feel like crying?
Fark

2 Likes
#108

Had the same experience one :slight_smile: But turned out, it’s a good chance to refresh everything you learned again!

1 Like
#109

thanks @woofy

Nothing i can do now, so i have to let it be really.

Sucks because i had made quite a few sequencers i was looking to integrate with the big cases :frowning:

Ok, so lesson learned !

#110

sorry about that - understandably very frustrating!

i’ve moved the warning closer to the actual firmware files to make it more noticeable.

2 Likes
#111

thanks for the cheer up @scanner_darkly scanner!

So should i just keep a memory stick for each teletype as a backup before updating?

Thanks

#112

yeah, just back it up to a USB stick before flashing and then restore after. also good to periodically save just in case.

2 Likes
#113

posted a suggestion on how we can help preventing accidentally deleting scenes when flashing a new firmware version: Teletype 3.2+ feature requests and discussions

#114

Thanks @scanner_darkly !

Much appreciated.

Worst off all is i kept on telling myself dont screw up…and then …well i screwed.

#115

I’m currently building a TT and I have an er301 and a Just Friends, am I able to hook up and communicate with both simultaneously or only one at a time?

#116

You should be able to talk to both.