Hi all, back from my family holiday. Let’s go…
Known issue… sorry! It’s a bit too complicated to explain. It’s nothing to worry about and it’s been done for a good reason, but it probably won’t fixed properly till 2.1 (courtesy of @scanner_darkly).
As far as I know that’s the same speed it was before.
Whoops, I’ll try to get that fixed. If it hasn’t been by the next beta, remind me please!
It will be related to loading preset 31 from USB. Known issue, not sure if I’ve got time to fix it (the USB disk code is pretty hairy!).
I’m not sure how I feel about the loop around for preset navigation… thoughts anyone else?
Ah. The age old battle between engineers (0 indexing) and mathematicians (1 indexing). I think it’s always been 0. If it hasn’t I’ll change it.
Having flashed my Teletype more times than I’d care for… most important is to make sure the USB A-A cable is disconnected when powering off your modular. If it’s connected before you power off, the Teletype won’t fully turn off (as it draws power over the USB cable).
Yes it is a good idea. Even if it’s only in there for a few versions before being removed.
I might see if I can add a
II op that does nothing to aid transition for that too. (It might not be possible, so don’t get your hopes up everyone!)
I haven’t got the brain space for this just now, I’m trying to get back into the swing of things again. Could you prod me to look at again in a few days (if I haven’t already)?
If you ever learnt a bit of code, you could probably add as many as you could think up names for… (although the computer scientist feels compelled to note that variables are the source of many bugs… anytime you can do something without them, do!)
Otherwise… yes use
D. In fact IMO we should entirely stop using
D to refer to the TR outputs and all docs should be changed to reflect that. New hardware ditches it too.
If anyone wants to volunteer to rewrite the Teletype studies series to reflect 2.0 and the current consensus for the best way to do things please shout out!
I’m not surprised by this sadly. Could you try on 1.4 (or 1.4.1) and tell me if that has the same behaviour?