#75

hm, might’ve missed this, but does the latest release disable the shape memories? i can’t access them on this firmware.

edit: damnedest thing, they started working after a few minutes.

#76

I’m having some issues with this firmware release.

RUN 1:
-Installed firmware (no issues)
-Plugged in QuNexus. QN powers, but no response from ES.
-Switched to Grid. No response from Grid (no interface loaded).
-Power cycled.
-Still no response from Grid.

REFLASH!
RUN 2:
-Installed firmware (no issues)
-Plugged in Grid. Interface loads. Able to play notes.
-Plug in QN. QN powers up.
-Play a note on QN. Note plays, but ES locks up. Edge and Pos lights are held full.
-Unplug QN. Plug in Grid. Interface doesn’t load.
-Power cycle.
-Plug in Grid. Interface loads.
-Play a note from Grid. ES locks up again. Edge and Pos lights are held full. No new notes accepted, and Grid interface doesn’t update.

From there, I tried about three more times. Each time, the ES freezes on the first note. Anyone else try the QuNexus?

#77

be sure to use this firmware:

i just retested and had no issues with either the grid or op-1. did you have the QN working at any point previously? did you have problems with the grid prior? (i apologize for not being able to keep track of everyone independently-- i may consider setting up a bugtracking system)

#78

I used that one. I’ll redownload, reflash, and retest with my OP-1 later today.

No problems with the Grid prior. It works fine on the MP and WW when I switch back to those modules, even after an ES lockup.

I haven’t tested the QN with the ES previously. I’ve only really used it directly with my computer, or with the CV outputs->modular.

#79

i expect the grid is fine. did you have issues with the ES prior? does the ES+grid work normally without the QN? (i gathered yes from the above post, but want to confirm)

#80

No prior issues with ES + Grid, aside from the slowdown issue. After I get a chance to reflash, I’ll test it initially using only the Grid. If that goes well, I’ll move to the OP-1 in MIDI mode, and then the QN.

Earthsea - with two personalities
#81

Got a chance to test again tonight. Grid and OP-1 work fine after a reflash. QN still nukes the ES until the firmware is flashed.

#82

Anything else that I should try?

#83

Out of curiosity do you have a USB MIDI converter?

If so I’d be curious to know if the same problem occurs when you have the QN driving the ES indirectly via an intermediate pair of midi interfaces. I’m wondering if the QN generates more midi data than the ES can process (with the current timer configuration).

Given that you say you have to re flash the ES in order to get it working I’m also wondering if it is possible that the last note priority queue is overflowing and somehow corrupting memory.

As I mentioned in another thread if you could record a few seconds of midi data which would typically lockup the ES and send it to me (pm here is fine) I can try to reproduce the problem (and fix it if I can reproduce it).

#84

I had another issue tonight. I was simply playing the Earthsea like a keyboard using a Grids (not recording arps or anything).

Occasionally, the “Edge” output would get stuck in an on state (so note on triggers wouldn’t fire). After about a minute, it would wake back up, but with massive slow down. Notes would trigger half a second late or clump together in weird groups. Finally, the Edge output got stuck again and wouldn’t seem to un-trigger.

#85

I have seen this behavior on mine quite a long time ago. Do you have it connected to TT?

#86

Yes. TT wasn’t controlling anything in the patch, but it is connected by ribbon. It was just hanging out and running the Triangle Mountain preset.

#87

I am trying to transpose an arp on the ES from TT but both of them constantly freeze when the ES.TRANS parameter accidentally gets ES over an upper limit (which seems to be the first row of the grid).

Is it supposed to be like that? And what exactly is the upper limit for the ii parameters? I did not find something about that by now in the manuals.

BTW ES.CLOCK is still not working on mine…always skips single clock pulses…:joy_cat:

#88

should be an easy fix

https://github.com/monome/earthsea/issues/9

but i have an idea about this should be more generally fixed up.

https://github.com/monome/earthsea/issues/8

of course, my code todo list is piling up…

1 Like
#89

I have experienced this multiple times in the past.
Perhaps the issue persists, but I have given up on TT controlling ES partly because of this.
Would love to see a stabile ES/TT dialogue.

Having said that I have had my own insane issues with TT control in general, so this could have been related to other things?

#90

Have a couple of hours to kill tomorrow. Might take a look at that.

#91

value clamping should be one-liner easy. buffering is a little more involved-- i recently added i2c handling into the event loop for teletype, so at least there’s a model (although, tt is handling outgoing i2c in an event, not incoming).

yes, inexplicably. can you point to the other issue threads so i can use them as markers for debugging?

#92

oh, hmmm, i will try to dig it out.
though a lot of it we communicated about directly, I think?

#93

Oh…

Talking to ES was what eventually has made me getting TT cause I was afraid of the coding part before. And indeed I am struggling a bit with the syntax so I always need a lot of free time to dig into it, go through the manual and studies to find a way to work out what I planned (not that much complex stuff).
So yes, would be really great to have it stable - thanks a lot for looking at it!

:slight_smile:

How is the dialogue with Orca and MP then?

#94

this is to say-- these features work perfectly on my system. so you may have no trouble.