#31

I had trouble too. It took me a lot of fiddling to get the volume right. As the doc states I had to attenuate my euro signal to a bit less than 1/4 volume. For some reason it didn’t like the file playback from Cubase but it worked from Live as well. That part is a head scratcher, but maybe it will help.

#32

Thanks for the tip. It was just weird because it always made it all the way through to the end and just never rebooted properly. It took a few redownloads and trashing of the files and luck to get it. I think…haven’t tested the new features so I’m not sure if it took. Fingers crossed.

1 Like
#33

This is completely amazing! I have just one question (as i got slightly confused) — should we expect new Just Type commands in one of the upcoming TT betas?

#34

No one has assembled these commands yet, to my knowledge. I just got JF 4.0 installed last night so I might get inspired to make the OPs but please don’t count on that as I am quite busy these days. In the meantime you might check out @scanner_darkly’s generic I2C OPs which should let you manually define your TT messages.

#35

thanks! i didn’t even realize i could do that. will look into that tonight!

#36

i’ll see if i can add it quickly - but i’d say we should concentrate on reducing the number of betas we currently have first (we have 6).

there are several ways to go about it, here are some things to consider.

  • backwards compatibility must be ensured, so yeah i don’t think we should modify any existing ops in a way that would make them incompatible with older scripts

  • for ops that take a voice or output index as a parameter i suggest modifying them to address 1st JF for voices 1-6 and 2nd JF for voices 7-12 - this way you could easily write loops that would address both. we’ll need to think what to do with the special value of 0 (all voices) - should that affect both units? just 1st? should another special value be introduced to address all voices on all units?

  • we could have an op to specify the current unit: JF unit would set the current unit and all subsequent JF ops will address that, JF would return the currently selected unit. this has the benefit of not having to modify the script if you want to change the unit. i did this for disting, and i found i wanted an easy way to temporarily address a unit different from the current unit…

  • for that we could introduce a special pre: JF1: ... and JF2: ... - anything following that would address the specified unit regardless of the currently selected one.

4 Likes
Teletype 3.2+ feature requests and discussions
#37

A big thumbs up from me for reducing the number of betas and consolidating things a bit with teletype. All the new stuff is very exciting but I’ve found myself sitting back and waiting a little for things to settle down because with a module as rich and complex as teletype I really want things to feel consistent across the language. (And, to be honest, I’ve also found the blizzard of updates a little confusing to stay on top of! Of course an embarrassment of riches is a nice problem to have…)

4 Likes
#38

This is probably the biggest change to the monome family of products since the introduction of variable brightness with the grids. Things are popping off and it’s hard to keep it all straight. I’ve got my TT taking a bit of a nap waiting for the changes to be consolidated too.

2 Likes
#39

Totally agree with that — I’m keeping it on the “official” beta build till things settle down.

1 Like
#40

yeah i was afraid it would be a side effect of having too many betas - i would say though if you can pick any new feature and help with testing it, it would really help us consolidate new features quicker - one of the reasons we have so many betas is because we want to hear feedback from teletype users before merging them.

4 Likes
#41

Oh I really like this idea. And index 0 should only target all channels on the one “active” JF.
L 1 2: JF I; JF.NOTE 0 X Y still fits on one line anyway.

Dittoed for truth. If anything under development looks interesting don’t hesitate to reach out with feedback or questions! The beta thread looks wild right now because there’s a lot more detail in there than any TT user needs and the action keeps bumping it up. We could also do a TT dev discord or something but I honestly always loved seeing the action from the sidelines and weighing in.

I think to help with engagement I will take a page from scanner’s book and start posting little video snippets with my TT experiments.

3 Likes
#42

I’m having a hard time updating my JF… as soon as i turn on my case (in boatload) identity lights up & 6n is pulsating. when i run the audiofile, nothing… I’ve tried Quicktime, logic, audacity from my mac ( with & without sound card ) different levels. & I’ve tried to run it from my iPhone with no luck. when i run the signal to hot I get a steady signal from 3n…

#44

I was having a difficult time myself. Tried it with my iphone, no signal registering at max volume. Tried it in Logic, no dice again, trouble getting the sampling rate correct and volume issues. It finally worked routing Ableton through my ES-9 with the volume turned down to -30db. Hope you’re able to find the winning combo with the gear that you have.

1 Like
#45

I can’t get mine to get to bootloader mode at the moment. Followed the instructions to the letter, but when I turn my case on all the outputs are dancing away like normal, no slow pulse on 6n. Hmm…

edit - I managed to resolve this by turning the case on once set to shape and cycle, turning off again, and resetting shape to sound. The same with both my JFs. Had no issues updating whilst playing back the update from Live at 3/4 volume, with a patch cable from the headphone jack of a laptop

#46

Did you turn all the knobs fully counterclockwise?

That was one I nearly missed!

1 Like
#47

I’m not sure what it was! I managed to persuade it to get to bootloader anyway

#48

My identity light is on before I send any audio to the run jack, (as soon as I turn on the case) Is this right?

#49

I had this, and it updated fine for me.

2 Likes
#50

I’ve just updated this beloved module. But there is some strange behaviour every there and then. When starting the system, and not playing it for half an hour, to warm up some analog VCO’s, it freezes. Or hanging notes, that just a command from teletype can stop…I have this experience with sending notes from ansible via iibus, and also teletype is on the playground. Am I doing something wrong, or are there others with the same experiences and solutions?

2 Likes
#51

Now that you mention it: I have not used my JF 4.0 much but I am getting many failures to boot up. It is on a bus with Teletype and F8R so I thought it was a I2C issue, but the timing is suspicious. I have not used any I2C commands for it yet since the update. About 50% of the time it does not boot, and I’m also unable up read F8R over I2C, so maybe it is holding the bus.