#36

the latest 2.3 beta (or rather a release candidate) now includes w/ ops: Teletype 3.0

5 Likes
#37

I agree. I do like how the existing “play” command decouples the “play” state from the module’s mode, though, and it would be interesting if we could find a way to do something similar with some of the this and that functions.

#38

Seconding this. Also, just output volume control would be good for mixing scenarios, and also shaping via Teletype “envelope” or LFO.

Another idea: a TW mode which pairs or groups multiple W/s together so they can be addressed simultaneously. Good for stereo scenarios, or recording multiple voices at once to create ‘stems’ that can then be manipulated independently.

Even cooler would be if the grouping mode also applied to physical controls, so that once say 2 W/s are paired they can be controlled from the switch and buttons together. This would make for a playable stereo pair. I don’t know if this is possible with sample accuracy over i2c (or at W/s subdivision rate) but it would be neat.

1 Like
#39

There is some control over output volume in live mode via negative offset into that! (and possibly recording nothing)

I’m actually pulling hard for the opposite use case—being able to address multiple W/'s separately over I2C, but I also would appreciate synchronicity.

I keep feeling like a great level-up idea for W/ Type is on the tip of my tongue lately…

1 Like
#40

This is good! I would love for it to be decoupled from mode though and also directly addressable.

Oh I would definitely want that and I guess, since I don’t yet have multiple W/, asks a question: is that what happens now if you have multiple W/ on your network? I.e. ws.play -1 sets all your networked W/s running backwards?

#41

that would be my guess, since every module on the I2C bus sees every message, each W/ ought to think the messages are meant for it

#42

correct; they’re all set to the same mode/direction.

my w/ firmware wishlist for teletype control:

  1. address multiple individual w/ units
    • e.g. WS.1, WS.2. or W1, W2 to keep down character count.
  2. insert cue points
    • e.g. WS.CUE.ADD
    • example: begin recording audio in, adding cue points along the way. as rec finishes and the loop begins, triggers from meadowphysics add more cue points, while the playhead moves between these new points via motion/jumps generated by other mp triggers, or teletype randomness. the audio cascade grows ever denser. would likely need something like a delete cue point operator (WS.CUE.DEL) to reign in the chaos.
  3. absolute cue point navigation
    • e.g. WS.CNAV x
    • example: jump to cue point 12 (of e.g. 20, no matter the previous cue location). instant nonlinear navigation much like mlr/mlrv sample-cutting! though this is a bit outside the linear nature of tape that w/ emulates. would probably be tricky to implement, as the number of cue points might be unknown & variable.
  4. clear current tape
  5. switch tapes
    • example: see #4 above. useful in a live performance context between songs, or even within a song. after doing a lot of destructive overwriting or looping, switch to a clean tape, work up a different set of sound manipulations, then return to the earlier version on the first tape.
  6. set exact tape speed
    • example: the current choice of forward, reverse, or stopped is decently norns-mlr-like, but being able to easily set any desired speed in either play direction would open up so many new sounds.
  7. “user mode”
    • example: create a desired configuration of w/, such as a gritty delay. load this delay via teletype, so that any audio fed in is immediately output as a thick, decaying echo. THIS and THAT inputs either work as expected from other modes, or are user-assignable, e.g. controlling decay length, grit/worn tape, etc.
    • separately control THIS/THAT via teletype, independent of w/ mode.

if THIS/THAT and the joystick actions had w/-type equivalents, i think most or all of this wishlist would be fulfilled. thanks for your consideration!

7 Likes
#43

Yes! I’m particularly keen on point 6 but I could immediately benefit from 2 and your second point in 7 - I imagine that control of the tape speed would be a TT command for THAT

#44

#2,3 & 4 would be great. The ability to add more precise cues would help keep things in sync.

#45

1, 2, 3 and 4 sound really great!

Outside of THIS and THAT being user-assignable, 7 just sounds like loading a TT scene. :slight_smile:

#46

As THIS and THAT have different effect (speed, overdub, etc) depending on W/'s current mode, it would be simpler and less redundant for Teletype to directly target the properties you want to change. This would open up new possibilities that wouldn’t be achievable using only THIS and THAT.

Certain properties, such as speed, could greatly benefit from a dedicated operator, as we could give them a unique, tailored way of reacting to the numbers we pass them. We could for example have speed be interpreted in the 1v/oct standard used by Teletype’s voltage outputs (1V = 1638), which would enable us to use the same operators we use with Teletype outputs for setting speed (conversely pitch):

  • V for octaves (1 volt = 1 octave = 2x speed)
  • N for transposition in notes (1 semitone = 1,0594x speed)
  • JI for frequency/speed ratios (3 over 2 means 1,5x speed or a perfect fifth, the ratio could be anything else)

This would open up possibilities for pitched sample playback, half/double speed/octave manipulation, just intonation and polyrhythms.

I know I’ve already said this earlier in the thread, but I can’t get over how useful and fun this would be.

5 Likes
#47

Given that the firmware now seems much much more stable, is it worth bumping this thread?

2 Likes
#48

Given the recent slow down in beta releases, i was under the impression that a final 1.1 firmware would be released soon with more w/ type ops. these are all assumptions tho

1 Like
#49

hi all

i just got a ii cable for my w/ and a walk, which means i’m finally ready to write a scene to create the most esoteric loop pedal of all time! since setting up a mic in my apartment a few months ago i’ve been experimenting with trumpet, guitar, whistling, clapping, snapping, etc into my w/ and i’m so excited to do it in a hands-free way.

has anyone else tried this? it looks like i’d have to set the cue points manually before playing, but could use a single script to go back to the first cue point in a loop, turn record on/off (with an EVERY), and stop/start playing. i’m so excited for more w/type features, especially around THIS and THAT.

update: this is really fun! i’m going to try to get something recorded this weekend and i’ll post the results.

6 Likes
#50

A very simple idea derived from the newly added features: how about a few utility operators for choosing the functions of THIS and THAT? Something like WS.THIS.DUB, WS.THAT.TRANSPORT, etc. It seems to me that using these from Teletype’s live mode would be a very convenient way to switch modes. I am sure this could be used creatively within scripts too.

9 Likes
#51

Did anyone take a crack at it?

I would like to help with the visualization part. Let me know if anyone is interested in making this happen…

4 Likes
#52

w/ as an external mlr track, controlled via crow :heart_eyes::heart_eyes::heart_eyes:

4 Likes
#53

After spending some time with TT + W// today, I really support this suggestion. Being able to engage record or reverse etc… on one/the other/both W/ would be wonderful for stereo stuff!

Edit: I’ve been spending a lot of time with Cocoquantus :sweat_smile:

5 Likes
#54

Might be better implemented as WS.THIS.MODE, WS.THAT.MODE with a numerical arg to switch between TRANSPORT/SIGNAL/DUB/CAPTION/SAMPLE.

2 Likes
#55

Agree for numerical arg as it would aid brevity

Edit - thinking a little further, considering RMODE syntax for Just Type, maybe there could be something like WS.TMODE 0 1 setting the numerical args for both THIS and THAT simultaneously. This could be more in line with TT syntax and also more similar to standard W/ use.

2 Likes