#16

I second all these emotions. Many thanks!

1 Like
#17

Very excited to try this out tonight. Much thanks to all involved.

1 Like
#18

@sam, I realized I was actually just building the html docs before…trying to build the PDFs caused some issues. I’ve opened a pr to monome/master with some fixes (and mention within the PR of a weird issue I can’t figure out).

1 Like
#19

Right I’m a bit tired, mainly due to a thunderstorm rather than the baby!

Thanks for the PR @jlmitch5, I’ve commented a bit there, but I thought I’d discuss the Latex issues here.

If you’re trying to diagnose Latex errors it can be much easier to manually run the (Xe)Latex step, like so:

cd <your teletype dir>
cd docs
../utils/docs.py teletype.tex
xelatex teletype.tex
xelatex teletype.tex  # if the first step has no errors

If you get errors xelatex will inform you interactively (type X at the interactive prompt to exit).

Paste the errors somewhere (gist?) along with info about your Python version, Pandoc version and you Tex distro and I will try and help diagnose.

You will also end up with a large quantity of build artefacts, I find a quick rm teletype.* in the docs directory sorts things out once you’ve finished.

Once my life calms down a bit… and I’m in a masochistic mood, I will try and get PDF generation tested in our Travis CI script.

2 Likes
#20

Quick update. Trying to diagnose the Latex errors following your explanation, I realised the issue was a lack of a path separator so it was trying to find the fonts here:
../utils/fontsroboto-hinted/Roboto-Regular.ttf]

The fix would be to add the missing slash like so:
- Path={{fonts_dir}}/roboto-hinted/

That builds perfectly fine for me at least. Hope this helps.

2 Likes
#21

I’d like to second what everyone has stated about the efforts that @sam put into this firmware release … and especially those of @scanner_darkly:

This work has made the TT firmware a much better place for the community to continue to contribute to and extend the platform. This work usually isn’t fun or sexy to do, but all future contributions will owe a debt of gratitude to @sam’s impressive efforts. It certainly made my job of adding the TELEX operators trivial.

Thanks again, @sam. You are a rock-star!

13 Likes
#22

Jeeze, @sam, two babies in one week! Congrats, and thanks for your hard work!

1 Like
#23

@jlmitch5 and @capleniz thanks for your input, I’ve opened up a new PR for the PDF tweaks, the Latex errors were not just the font paths, but also missing new lines at the end of the latex_preamble file.

Thanks everyone for the kind words…

Continuing on from what @bpcmusic and @scanner_darkly mentioned about the under the hood stuff…

One of the biggest invisible things that’s changed is the modularisation of the front end / UI code. This should hopefully make it a lot easier to tweak or add new display modes to the Teletype.

Before I share some of the ideas I’ve had, firstly the USB loading and saving code does need to be rewritten before much else can be done. I’ve sketched out how I think it should be done (separate the pure parts from the impure, I can talk about it more if someone wants to volunteer to do the work?), once that’s done I think we should reduce the number of scene description lines to 16 (from 32) to free up some more flash.

Otherwise interesting new features…

  • Increase the number of pattern from 4 to 8. The pattern editor code is on it’s own in one file, so it should be quite straightforward to do this. We’d probably want to add a permanent set of row headers if we did and it would look a bit too much like a spreadsheet… (An extra 4 patterns is almost exactly the same amount of flash as reducing the scene description by 16 lines.)

  • A settings mode. Just to allow you to make some global behavioural changes, ideas include:

    • PARAM, IN and CV calibration data
    • Remap CAPSLOCK to CTRL (this one is just for me!)
    • Switch A, B, C and D to defaulting to 0, rather than 1-4

    Personally, only the first has real value, and in general I don’t like the idea of too much choice with these things.

  • An actually UI for USB disk load and saving, maybe an “are you sure” prompt, or even individual loading and saving of scenes. (Remember we can only use the param knob and the front panel button as the keyboard will be disconnected!)

Naturally I have no idea when I’d have time to do any of these things (if I ever do at all). But I’d be more than willing to help out with advice and guidance if anyone else wishes to volunteer.

4 Likes
#24

Big +1 to that!!!

This would also be great! Also a way to update the firmware from an USB stick would be great, but I guess that would involve a lot more coding, wouldn’t it?

1 Like
#25

So excited to try this out! As I consolidate my setup, the TT is becoming more and more central, and these new tweaks will help a lot.

Also, congrats on the amazing work from the community that went into this, and into maintaining and improving the whole Monome related module suite.

1 Like
#26

Watching from the sideline. All this work is truly impressive.

I’m an occasional TT user and I probably wouldn’t utilize a fraction of what it’s capable of. But I’m so fascinated by the concept that I purchased a used one a while back. And I’m super impressed with what you wonderful humans come up with.

Hi fives and hugs! //Carl-Mikael

1 Like
#27

That would be cool wouldn’t it. I think it’s technically possible but… not that straightforward. The Teletype usually executes it’s code from flash ROM, but if we’re about to overwrite the flash we can’t run code from there any longer! So we’d need to copy some code to RAM to run the updater, which isn’t as easy as it sounds.

The other alternative is to try to add a second bootloader for flashing from USB stick (the first bootloader allows for flashing from USB cable and can’t be overwritten by end users). This is probably easier for us to do as the Aleph uses a similar technique except it uses SD cards instead of USB sticks.

Anyway, I don’t think it’s something that I’d want to do!

#28

I don’t have a Teletype (yet) but this kind of things make me want one even more :slight_smile:.

2 Likes
#29

This is fantastic!
Thank you to all involved: looking forward to digging in!

1 Like
#30

very excited to dig into this. thx to all who made this happen, wow.

1 Like
#31

On vacation right now, first time to dive into TT 2.0.0 – what can I say? This is awesome, such a huge leap, thank you so much for making all this happen!

3 Likes
#32

I just updated today to V2. Backed up my presets before updated. After rebooting i tried installing my old presets. Read/Write works but Teletype overwrites and wiped my existing presets (i still have them saved on my computer so not 100% lost). Any workarounds for this? Seems like Teletype is writing first to usb before reading the usb.

#33

did you delete the “s” at the end of the filename? reading works only if the file name is as such : tt??.txt

1 Like
#34

No i didn’t and now i have and it works fine! Thanks for that. Much appreciated. Saved me alot of time having to retype everything :slight_smile:

#35

hello, i have two request with teletype, two things i miss a lot since i used it :slightly_frowning_face:

with white whale, i would love to have a read position script, there’s actually only “cue to postion” (WW.POS) . with that, you will be able to synchronise trackers positions with white whale positions, So more CV OUT to white whale, it’s just an exemple…

and with ansible, i would love to be able to change the Edit position of LEVEL, like when you push buton 1 on the module.
actualy there’s only a read postion with LV.POS. So with that new script, you will be able to use walk instead of pushing this small button 1 on the module.

is it diifuculte to add thoes ? i don’t have any skill on coding…
thanks