Beta 9 released: The Audio Rate Edition
Firmware available in the first post
Changes since beta 8.
- Audio rate triggers no longer crash the system (including when the triggered script sends
i2c messages). Your Teletype may become unresponsive with audio rate triggers, just slow them down or unpatch the cable to regain control.
- Increased system responsiveness under audio rate triggers
PARAM will still update when on the pattern editor screen
- Long OP names don't crash the system when missing parameters
Also from @bpcmusic
- TELEX Aliases:
TO.TR.PULSE (plus all sub-commands) and
TI.PARAM (plus all sub-commands)
- TELEX initialization commands:
TI.IN.INIT n, and
High tempo. long running metro scripts can still lead to problems (I think). Although I've been trying to get something to break with a Teletype and an Ansible and I can't.
If someone can knock up a script that does, that would be fab.
In theory, it's not the Teletype crashing, but rather the keyboard and screen handling code being starved on time on the CPU. In essence you can't turn the metro off.
Otherwise, it will be time to start declaring release candidates soon.
edit: have managed to crash the Teletype/Ansible with crazy metro i2c stuff, interestingly I think it might be Ansible that crashed, and thus took out the Teletype (via the i2c code), if only I could reproduce it more reliably. I'm wondering if the fixes I made to Teletype may also fix some things on Ansible.
Here we go, put this in your metro
L 1 100: STATE 9
Make it go fast with
M 10. Wait a few seconds. Crash (if you've got a serial port you can see that the event queue starts overflowing indefinitely)
What's interesting is that if you have a reset switch on your Teletype, you can reboot just the Teletype. If you do, it works fine.... until you try to communicate with any i2c command (even to non-existent devices).