62

@desolationjones: Thanks for the suggestions. Setting the end first and then seeking backwards seems like a good approach however I’m still not seeing the behaviour I expected.

Here’s a video of what happens when I try the above commands: Teletype and W/2.0 Loops - YouTube

What’s confusing me is the state of the loop after those ops. You can see in the video at around 0:15 after W/T.LOOP.ACTIVE 1 the yellow loop light starts pulsing but when I press “play” the white “play” light flashes but the loop does not cycle, it just stays on the loop start point (pulsing yellow).

When I manually trigger the “loop” button after that (while playing), you can see that the loop lights cycle, indicating that there is an active loop working. I was expecting the same cycling loop lights to happen after I pressed play after running your script.

Are you seeing the same behaviour (i.e., no cycling loop lights after running script and pressing play)?

PS. I’m not really intending to repeatedly write to a small, fixed section of the tape. This is more an exercise to help me understand the mechanics of the W/T mode.

Edit: @Justmat Aha! Your W/T.SPEED 1 1 suggestion was what got things working for me. I think for some reason the tape speed must have been set to zero somehow. Once I ran that command the following script worked exactly as I had expected:

W/T.SPEED 1 1   # This is not needed after it is run once
W/T.LOOP.START
W/T.SEEK 4 0
W/T.LOOP.END    # The automatically activates the loop
W/T.PLAY 1

I still don’t fully understand why the script didn’t work but manually pressing play and setting the loop start/end markers worked even though I must have had the speed at zero, but now that I’ve set the speed both modes work much more similarly.

Thanks again!

Update

Ok, so I managed to automate periodically recording 4s loops and then playing them back reversed, which is great, but now I’ve hit a new problem.

After running the scripts that implements a set loop, record, and playback cycle a few times all output from the W/ suddenly cuts out. No pass through our recorded sound plays and the white light above the IN jack stays on at full brightness.

What is weird is that the rest of the W/ seems to be functioning normal. The yellow light on IN seems to be monitoring the input, and the loop, play and record lights are all responding normally to both manual button presses and W/T i2c commands from the Teletype.

I’ve tried send a bunch of commands to get the W/ unstuck but it stays silent. The only thing that gets it working again is a power cycle.

Has anyone else seen this sort of behaviour? I did not see it when executing simpler scripts or executing W/T ops in live mode, so maybe W/ is freaking out from receiving too many i2c commands at once?

For context, my setup is:

  • Green PCB Teletype (v4.0.0)
  • Just Friends (Gold Clouds)
  • W/ (v2.0b7)
  • i2c: TT → JF → W/
3 Likes
63

Aha. Thanks.
Strange then how 2.0 resolves the SD degradation issues if it still records to the card? I had understood the changes made in W/ 2.0 to be in response to the challenges when repeatedly accessing the same position on a card during looping playback/record.

1 Like
64

This is a little confusing, but my understanding is that the card I/O driver was rewritten as well, so this is also accurate. So it’s a two-pronged approach: first, reduce card wear directly when using tape, and second, offer an alternate delay/loop mode that doesn’t touch the card.

1 Like
65

is there any reason for W/S being the only mode with a PATCH op? seems like it would be a useful addition to w/delay and w/tape :cowboy_hat_face:

2 Likes
66

I don’t know the reasoning but it’s a limitation on the w/ side, not Teletype! I’m curious how you’re using the patch OP–remapping modulation sources on the fly?

67

i’ve just been going through all of the ops and noticed it missing from the other modes :smiley:

so far i have only played around with the op, going through all the connections randomly. though, i can see it being useful to set things up, something in the init script maybe.

68

In general it was implemented by checking what is exposed in crow W/ 2.0 integration

if there is anything missing in teletype integration from that (or other modes lua file) I could take a look later at adding it (but unfortunately as desolationjones mentioned it seems that patch is only available in synth mode).

1 Like
69

@Galapagoose i know you are pretty busy with new stuff these days, but any thoughts on having patch ops for W/tape and W/delay?

2 Likes
70

It’s absolutely possible, just a bunch of typing for me in the W/ codebase. I’m certainly not prioritizing it, but if someone has a compelling usecase for how it would be used you might bump it up in my todo list.

4 Likes
71

This sounds really interesting but I’m a little confused as to what the param argument for PATCH should be. It is an integer, right? If so, how do you know which parameter the jack is mapped to? An example of using this op would be very enlightening!

72

i don’t have a list of the parameter numbers. i was just going through sweeping an offset around ±5v.

i can say for sure 5 is lpg time, 6 is lpg symmetry, and seems like 7 is a gate input. i think 8 may be pitch? numbers up to 10 seem to work, but i can’t say exactly what’s being controlled :sweat_smile:

does anyone know what numbers map to which parameters?

73

I dug the reference list out of the long beta thread, and put it in the wiki post up top: Mannequins W/2 Beta Testing - #4 by Galapagoose

6 Likes
74

thank you so much! :smiling_face_with_three_hearts:

Screen Shot 2022-03-31 at 6.07.26 PM
Screen Shot 2022-03-31 at 6.07.26 PM1384×450 21.8 KB

4 Likes
75

I looked through the thread, and couldn’t see anything - so…

What’s the expected behaviour of you connect multiple w/ to teletype? Do they all get the same commands? Or is there some way of choosing which one to address?

:slight_smile:

1 Like
76

right now each mode has hardcoded address in teletype, so if they are in different modes they will get the commands that only address the mode their in, but if you connect two in the same mode they will get the same commands

3 Likes
77

You can do it two w/ separate with the the Same Mode

Screenshot_2022-04-03-18-52-37-558_com.android.chrome
Screenshot_2022-04-03-18-52-37-558_com.android.chrome1080×2400 227 KB

3 Likes
78

Would anybody be able to point me in the right direction in figuring out how to talk to a second w/ in the same mode? I understand setting the alternate ii address as posted above but not sure where to look to find the right commands/messages for the second w/.

1 Like
79

Did you ever figure this out? I’m having similar struggles figuring out how to use W/D.CLK.RATIO. Every combination of W/D.CLK.RATIO X Y seems to have no effect. (I’m sending W/D.CLK from my TT metro, if that makes any difference?)

80

Unfortunately I had no luck and gave up. I’m also sending W/D.CLK from my TT. I did try both clocking from TT and from the Jack input but I never got any results. I wonder if we are both doing something wrong or if the W/D.CLK.RATIO just doesn’t work?

81

@Galapagoose is it possible to have a Teletype send a W.Mode 1, W.Mode 2, W.Mode 3 for tape / synth and delay setups. It’s just really handy to be able to call modes like you can do in JF from TT especially in a live situation.

5 Likes