#93

done! https://github.com/monome/teletype/issues/144

3 Likes
#94

Just a little behavior report…I have a pretty slim Scene running using the turtle function. Outputting info to an Ansible in Teletype mode. (Also have Telex and ER301 attached. After running for about 10 minutes, the scene stops accessing the CV info. Trigger’s keep happening and the unit does NOT freeze, but the CV no longer works. I can reload the Scene, but the CV is still inoperable. A restart gets things working again.

#95

you mean it stops updating the CV outputs? does it only affect ansible outputs or teletype as well? also, if you could test it with the official 2.2 version and see if you get the same behaviour that would be hugely helpful.

#96

I will explore your suggestions further this weekend. Thanks!

While I have you here…when addressing Kria from Teletype, are the patterns and positions addressed starting at zero or 1?

#97

looks like it’s 0 based

#98

Hello. FYI, I’ve released a new ER-301 firmware (v0.3.19) that silences all of the UART/I2C chatter that I possibly can. Unfortunately there is still a tiny bit of chatter remaining, right at the beginning of the boot up which I can do nothing about because it is burnt into the ROM factory boot code of the AM3352 CPU in the ER-301.

When powered on, the AM3352 starts executing boot code from ROM that brings up the SD card and searches it for a bootloader. During this process it sends the following message to the shared UART/I2C port:

Detected SD Card version : 2, High Capacity
bus width: 4-bit
bus freq: 25MHz

Other than that there is no activity on the lines. My preliminary tests show that the Teletype does not freeze during the ER-301 startup but I would like some confirmation please.

7 Likes
Teletype, er, emergency!
#99

great, thanks brian! i’m planning to bring a small system with er-301 and teletype to seattle synth meet next week, so this is great timing. i should be able to test it this weekend. worst case scenario i could implement a delay for i2c commands on startup.

3 Likes
#100

updated the firmware and did a quick test, looks like it still freezes if any i2c commands are executed within ~1 sec from turning it on (i tried 1.5 sec delay and that works, so the delay needs to be somewhere in the 1-1.5 sec range).

the proper solution would be to make the i2c code more resilient, but that’s a significant change that will have to happen at some later point. for now i could simply add a delay to the teletype bootup sequence. i think this is an acceptable solution, but curious what others think.

8 Likes
#101

I agree about it being the acceptable solution!
And thank you for tracking this down!

#102

I have a feature request for the Kria commands: would it be possible to create a couple of commands to define the beginning and end of Loop slots while in Meta mode? Asking for a friend…

#103

for kria requests you probably want one of these threads:

#104

Please do, it’s the best thing that can be done for now…

#109

Are the w/ ops in this beta?

#110

no - the w/ code hasn’t been merged to teletype master yet. once it’s merged i’ll post a new beta shortly after.

2 Likes
#111

I keep forgetting to mention this …

I am on the previous build (B537759) and can’t upgrade for a couple of days due to being in the middle of a patch, but I wanted to report an issue I ran across last week that I have not seen anyone mention before: when in the pattern screen, pressing CTRL immediately puts a value of “31” in the current position. I found through use of the CTRL-Fx trigger muting command.

It’s possible this was noticed and fixed in the latest build–if so, sorry about the obsolete bug report! Thanks again for all the wonderful work. :slight_smile:

#112

Was your Param knob all of the way CW? :slight_smile:

Pressing CTRL while in Pattern view inputs the current position of the Param knob, scaled 0-31. Or at least that is what it is doing on my TT. Though, I can’t find any mention of it in the docs… and I am not sure why it is 0-31.

#113

yeah it caught me off guard too! it was added a long time ago actually. iirc CTRL will set the current pattern value to PARAM knob scaled to 0-31 and CTRL-SHIFT will set to PARAM without scaling.

2 Likes
#114

Yes! I just tested it with the param knob in various positions and it behaves as @scanner_darkly describes above.

We appear to have a keystroke collision here! Muting is super valuable, maybe move it to shift-Fx? Shift keys are larger than CTRL keys, so this would be helpful.

#115

that’s a bigger change in behaviour - it probably makes more sense to use different key combos for tracker instead. maybe instead of CTRL make it CTRL-ALT?

4 Likes
#116

EXTREMELY IMPORTANT

for folks who want to try grid integration - do not connect your grid directly to teletype!!! doing so might result in damage to your teletype and/or grid! grid MUST be powered externally!!!

5 Likes