WW/MP/ES teletype updates

tehn · 2015-07-13T15:16:54.954Z

laborcamp:

Do you think that whatever causes the slowdown on ES is also causing the TT crashes? Or are these issues unrelated, based on your expertise?

it seems like the slowdown issues in ES could cause some TT crashing, though it seems difficult to imagine. if ES is hanging somehow, TT should abort the II transfer.

do you get TT crashes arbitrarily when connected to ES without using the II command? i’m unfortunately reaching a point of data overload when it comes to bug reporting. i’ll start doing a better job logging issues into github.

edit: added issue here:

github.com/tehn/mod

ES slowdown

opened 03:19PM - 13 Jul 15 UTC

closed 05:32PM - 19 Mar 16 UTC

tehn

general slowdown over time, noticeable in pattern playback. sometimes results in unresponsive grid. may be related to TT crash

EARTHSEA bug

feel free to add information on the issue directly. i’m hoping to solve the ES issue before tackling a new revision of TT.

laborcamp · 2015-07-13T15:29:45.605Z

@greenanother What you are describing is the slowdown issue. I have now seen it many times and it always works out the same way. The patterns begins to slow down, grid becomes totally unresponsive, eventually grid freezes completely, the whole thing seems frozen, but eventually it accelerates back up. I think most of the time it does not quite reach back the proper speed though.

In any case: you are experiencing exact same thing I see in my setup.

laborcamp · 2015-07-13T15:34:48.922Z

After several instances I think that the TT crashes happen when it receives the trigger that executes a script with a II command.

Up till yesterday it was always related (in my case) to ES being connected.

But yesterday this happened when I tried using WW II command (sent you a PM with that), so that changed the picture a bit from my vantage point as not just ES problem, but something that has to do with the II functionality.

greenanother · 2015-07-13T16:58:47.905Z

Ok @laborcamp looks like we’re getting warmer. I believe @tehn will get to the bottom of this. I accept that these issues will come up when there are so many variables involved (with devices that do things no other device can). I’m just glad the issues aren’t power related.

tehn · 2015-07-13T21:14:49.430Z

laborcamp:

I went ahead and connected ES with newest firmware to the TT and the rst of trilogy. I initiated the factory scene for ES control, and changed one line to control transposition with the PARAM knob as follows:

X RSH PARAM 10
II ES.TRANS X

and connected a slow clock to input 5 to trigger the script.Teletype froze immediately.I could still control ES manually from the grid, but TT is frozen. And, as I type this message the Earthsea exhibits the slowdown symptom once more…

ok-- i have frustrating news. i simply cannot reproduce the “slow-down” issue. my steps:

cold start modular
ES record pattern, turn on transpose, play it
TT load ES REMOTE scene
turn PARAM knob, hit WIN-6 to execute, works fine
add patch to TT input 6, works fine
tweak everything possible in an attempt to crash, still working. triple shape triggering with tons of slew while II messaging CLOCK and TRANS, really!

can i see a method for consistent crash/slowdown behavior? there’s nothing special about my hardware-- it’s the same batch that we send out to everyone else.

please post to this new thread:

ES debugging (back to it) Monome

please post here with your recipe to achieve the “slowdown” bug with earthsea. please let me know which grid you have and if you’re II connected to TT.