#20

Yes range of 32 works fine as is but I thought you were suggesting dead zones as a fix for jitter at the maximum, non-scaled range. (I would prefer stability at a range of 1024 at the very least! Ideally 4096.)

I must have skipped the section of the pdf where CTRL in the Tracker was mentioned. I’ll double-check any further bugs! Cheers!

1 Like
#21

One thing I wished I had the time to do when I re-wrote the cut and paste code was to display the contents of scripts on the preset load screen and add support for copying the contents.

If you’ve got the headspace for it (and especially with the multi-line changes) it would be a real timesaver.

1 Like
#22

I’ll add my support for this idea. I find that I often want scripts for other scenes as part of something I’m working on… i.e. I have a quad lfo script that I’d love to be able to copy into any new scene that I’m working on.

3 Likes
#23

i don’t think the technique would work well for full range, you’d want it to be smooth. for scene selection though it makes sense.

do you mean displaying full content as one page right after the scene description part? that might be simple enough to do, i’ll take a look. not sure how this aligns with the proposal for new scene loading/saving though, i wasn’t following that discussion closely.

1 Like
#24

Yeah basically that. IIRC you should be able to call print_command (from src/command.c) to get the string out easily enough. The trickier prospect is deciding how to manage the output buffer. (i.e. convert all 10 scripts and store them in a temp buffer, or convert each line on demand as it’s needed). Other minor complexities include dealing with blank script lines.

AFAIK that only concerns serialisation to/from text files on USB, the on flash storage format will still be in the ‘compiled’ op codes that we currently use. Hopefully by using print_command you’ll be isolated from any changes in the underlying representation anyway.

1 Like
#25

probably just enough to hold 7 lines and just update it dynamically when it’s scrolled up/down. can just ignore blank lines. another question is how to treat selection - for multi line implementation i changed the copy/paste buffer to be able to hold up to 32 lines (thinking this would be needed in case you want to copy/paste a scene description). i think i’ll leave it at that, and if you copy more than what a script can hold it will just shift everything down and discard any lines after 6 (which is how multi line copy/pasting works right now).

of course, there is a temptation to allow editing in this mode as well, so then you can edit all scripts together on one screen… :slight_smile: just a though really as this would require its own screen and proper script validation etc. i do think that multi line editing will be super handy whenever we get to the timeline feature (especially moving lines up/down - i imagine you’d do that often when editing the timeline).

i meant this thread: (Teletype) USB Disk Mode Interface it mentions script copying among other things.

Teletype v2 proposals
#26

The key combos for manual execution of scripts don’t seem to be working for me.

I’ve tried every combo of Win / Fn / Ctrl / Alt / Shft + a number / an F key.

Only Fn + F3 and Fn + F4 work - triggering Scripts 3 and 4, as expected.

I can’t trigger any other numbered script or “I” using any combo I’ve been able to find documented in previous versions.

EDIT: OK - I now see F1, F2, F3, F4 and F10 work without a key combo - but F5, F6, F7, F8 don’t. I hope I haven’t added to the confusion. Basically - there should be one key combo that works for each script - and that isn’t the case currently

Mutes all work - except for Ctrl + F9 for M, which is intermittent - ie. If I hold Ctrl and repeatedly press F9 (not too fast), it doesn’t always toggle the mute status of M. (Also the small letter M in the bottom left corner of the Mute Script screen does not reflect its Mute status as the similar numbers on other Script pages do.)

I’m on the stock chiclet keyboard.

Am I missing something?

Regarding the ALT + UP black screen of death - it happened once today in about 3hrs of Teletyping. I was on a blank line on the 6th row of a 5 line script. After re-booting, I reloaded the script and tried to repeat the crash - but no such luck.

#27

i just tried triggering scripts with F keys and it works fine. could you try it with older firmware and see if you can reproduce? i have a feeling there is something else going on. also try replugging the keyboard several times.

#28

I was editing my post as you replied, I think.

Does F5 to F8 work for you, to trigger the relevant scripts?

EDIT: OK, they seem to be working now. I think I may have a problem with my chiclet! I’ve had other intermittent problems with it… I’ll grab another USB keyboard to see if that is the problem. Thanks for your patience.

#29

yeah, all F keys work for me. CTRL-1 etc is not used anymore. are you using this key reference? https://monome.org/docs/modular/teletype/TT_keys_card_1.3.pdf

it’s outdated (ver1.3) and shouldn’t be used anymore (@tehn - the main teletype page should be probably updated to reflect that, not sure if there is a new version of key reference?). this doc should have the proper key shortcuts: https://monome.org/docs/modular/teletype/manual/#global-key-bindings

it won’t have the 2.3 shortcuts yet (there are new shortcuts for grid visualizer and multiline editing) but i think it should have the 2.2 shortcuts.

1 Like
#34

20 characters of done!

1 Like
#35

Is the 2.2 or 2.3 documentation available for review anywhere? I just spotted a couple of typos in the 2.1 commands pdf.

#36

you can see the docs for 2.2 here and for 2.3 here (no html/pdf version yet, the official doc is updated as part of a release).

since it’s in 2.1 version it should probably go to the 2.2 thread since 2.2 hasn’t been officially released yet. or better yet, if you’re comfortable with git you could fork and make the changes yourself and submit a pull request.

were you able to find a working keyboard? and have you had any more issues with Alt-<up> freezing teletype? i wonder if that was also due to the keyboard. regardless there are indeed some other bugs you mentioned, i got sidetracked by other stuff and haven’t had a chance to look into them yet. hopefully this weekend.

#37

@scanner_darkly sorry I haven’t been much help with this, too many (happy) life changes at the moment!

But, if you ever need any help getting the PDF or HTML docs running, tag me and I’ll free up some cycles for it.

1 Like
#38

Thanks - I’ll reply over there. I looked at github a few years back, became confused, gave up. I should revisit it - I’m sure there is a step-by-step guide to getting set up.

were you able to find a working keyboard?

The only other USB keyboards I have include hubs, so don’t work. I have ordered a small, mechanical replacement which arrives tomorrow.

and have you had any more issues with Alt- freezing teletype?

Yes. I now try to avoid using ALT + Up as I have lost work a few times. Hoping the new keyboard fixes it - but there do seem to be some other problems with the way the line moving / commenting works.

i got sidetracked by other stuff and haven’t had a chance to look into them yet. hopefully this weekend.

I can’t believe how much work you and others have put into this. The Teletype is becoming an even more incredible module with every new version. I’ll help where I can, even if it’s only stress-testing and proof-reading.

And good luck with the job interviews!

3 Likes
#39

just uploaded the 2.2 docs to the monome site

http://monome.org/docs/modular/teletype/manual

4 Likes
#40

i really need to get latex set up on my machine so i can post beta manuals as well… thank you, will ping you if i run into any issues!

your help is very much appreciated! maintaining documentation is one of the most difficult aspects of software development.

will be taking a close look at multi line editing, thinking about it more it doesn’t sound like a keyboard issue, i assume the module was frozen to the point where the front panel button didn’t work either.

1 Like
#41

I’ve just spent an hour playing around with Moving and Un/Commenting lines in Script Edit and there’s a bunch of funky stuff happening that is probably all related to a single section of C code.

I’ve had one freeze with the new keyboard but it wasn’t the ALT+ UP freeze - despite trying to get it to happen.

I know you are busy playing Shop :wink: but when you get a chance to look at it again, let me know and I’ll send some details of my findings in case they are of use.

1 Like
#42

A small issue I ran into the other day. Using P.HERE / PN.HERE to assign a value does not visually update on the pattern page while its value is stored correctly in TT. A simple test which illustrates this (at least on my TT):

1:
PN.HERE 0 RAND 100

2:
PN.NEXT 0 RAND 100

3:
PN 0 0 RAND 100

If you then flip to the pattern page and trigger the scripts form the keyboard Script 1 will not cause updates on the pattern page until you either flip to anotherå page and back to the pattern editor or trigger Script 2/3 which I’m assuming redraws the contents of the pattern page. In contrast, both Script 2 and 3 perform their function and provide visual feedback on the pattern page.

Not a deal break by any means, but my assumption is this is not the intended functionality as all the other pattern ops I tried visually updated immediately.

1 Like
#43

yep, it’s a bug. easy fix, will include it in the next beta!

1 Like