#247

… and it’s now a 100 commit branch

100commits

(no particular significance to the number other than indicating that it’s going to be a huge PR… which is not necessarily a good thing. but good to be getting close!)

2 Likes
#248

as of my branch the docs match what you say. I can add the two other shortcuts if they’re not there when I fetch.

1 Like
#249

i can add those, that’s a small change.

@freqout which doc did you use to check the pattern shortcuts? https://monome.org/docs/modular/teletype/TT_keys_card_1.3.pdf - this one? want to make sure there aren’t any other places where we have outdated info.

#250

this is where i ended up looking… forgot there was a key-specific doc…

https://monome.org/docs/modular/teletype/manual/#patterns

#251

Yeah, I was just gonna call that out as where you might have looked. There is more detailed information elsewhere in the same docs, which should be correct. This bit isn’t wrong, it just may misleadinglessly suggest that that’s all in terms of features and/or documentation.

1 Like
#252

that section doesn’t have the shortcuts though… i only see it here: https://monome.org/docs/modular/teletype/manual/#tracker-mode-1 which seems to include the latest with the exception of the 2 shortcuts to enter the knob value.

edit: ah i see where it is: https://monome.org/docs/modular/teletype/manual/#tracker-mode
we should add a distinct looking note there with a link to the full section. this ought to be done for all sections under Quick Start probably… which would address this:

the one i linked is terribly outdated and should be removed (you can still see 1.3 version in the filename too). @tehn when you get a chance could you update the main teletype page to remove PDF key reference that links to https://monome.org/docs/modular/teletype/TT_keys_card_1.3.pdf?

asked in the doc thread if we can autogenerate a new key reference.

2 Likes
#253

(Cheering y’all on :slight_smile: )

2 Likes
#254

@scanner_darkly Hey sorry to be nosy, but I was wondering what is meant by TIME and LAST now being 1ms accurate? Isn’t the Scene State TIME variable still incremented by the clockTimer callback?

#255

what you describe was the previous implementation. my change was to use the global ticks variable that gets updated on each tick instead (tick is 1ms). the internal time variable is still used to allow setting TIME and to keep the last TIME value when you stop the clock with TIME.ACT 0.

here is the complete fix:

https://github.com/scanner-darkly/teletype/commit/c29a0466d3a602ef930dff103400b9946fab20a2

#256

Right, my apologies I was looking at the master branch.

#257

grid visualizer and grid control mode pages are now fully documented:

grid visualizer
grid control mode

the last remaining task is updating the teletype documentation. almost there.

8 Likes
#258

Kinda curious, is it possible to implement ansible control via virtual grid from teletype? Could make much more sense of having ansible without physical grid/arc

#259

would be certainly interesting to try… this would require a two way i2c communication though, which is not currently supported.

#260

well, i think we are in the home stretch now. the only remaining task for me before submitting a PR is to add a grid section to the manual, all the other docs have been updated.

also as you might’ve noticed the version number has been changed to 3.0 - sorry in advance about the confusion it might cause! it was agreed there were enough changes and new features to warrant updating the major number.

with this i introduce hopefully the last release candidate. the only change from RC4 was replacing the shortcuts to insert a scaled knob value in tracker (instead of ctrl and shift it’s now ctrl-alt and ctrl-shift).

release candidate 5 july 12the
3.0 RC5

teletype.zip (162.3 KB)
teletype.hex (549.4 KB)

exciting times!

29 Likes
#261

I definitely think it feels like a 3.0-level change! cheers!

2 Likes
#262

TT 3.0 FTW! Great work, @scanner_darkly!

3 Likes
#263

I feel like 3.0 is merited as well. The teletype has been revolutionized again! Thanks to you and everyone who contributed to this release, as well everyone who has contributed through the teletype lifecycle. What a truly amazing thing it has become.

PS - so far, so good on whatever fixes you made to the slowdowns I was encountering. I’ll keep testing on RC5 and let you know if they crop back up again.

2 Likes
#264

Go team. You’re all stars.

We really should try and get together that definitive shared library of TT scripts once 3.0 is out in the wild. I just tried to load all my 2.x scripts via USB with no luck, so need to start fixing them all up. Probably just minor syntax changes (some of the scripts probably date by to 1.x as well, haven’t checked yet).

1 Like
#265

Oh, shouldn’t the firwares be compatible?

#266

Not sure TBH. Haven’t had the time to keep up with the forum lately. For all I know I’m just doing something stupid.