Closed for Company Meetings: Between September 18 (5pm PDT) and September 22 (12pm PDT), Support and Sales requests will be delayed. Only time-sensitive issues will be addressed during that time. Thanks for your patience.
Yes, I'd definitely like to. I'd prefer to wait for Max6 for MaxForLive is standard, as I've been able to replace the sequencer with gen~ code which improves the performance quite a bit. IIRC the version here has the old sequencer which, like the analog original, is a series of distributed steps (check out the bpatchers with the knobs in the step sequencer), but it's a thoroughly weird design in Max as it uses feedback, which limits the maximum speed of the sequencer when you use it as an (!) oscillator. (max freq = samplerate / (vectorsize * 24))
My main hitch with doing Max4Live is what to do about tempo? I'm guessing that the easiest thing is just to have an auto-sync of sorts that resets the sequence every n measures, though people would also probably want more clearly defined rhythmic steps. You can do it now, but it's not the most obvious way. Rather than a thousand knobs like the original, I'm guessing I might want to use some hybrid of live.step for the sequence controls.
Also on my to-do list is to replace some of the oscillators. I'm upsampling saw~ to help with FM, but I'm considering replacing it with something different because saw~ isn't great with FM. (but this is also gen~ territory)
The original EML isn't set up for keyboard control at all, but this is probably something people would be interested in, so I might see if there's a way of incorporating that.