No

[thermionic]

@Lwhdrmnjyr

Do you believe an attack control function/portamento would be very CPU intensive? Seems like extremely simple features. I can see how having an extra LFO or slide trigs could get tricky but these are more complex things (at least the way I see it from a clueless PoV lol).

I also read that the digi and the models utilize the same CPU so I guess it could make the function port a bit easier than it seems?

Model:Cycles Q & A with Ess

The CPU is a Coldfire MCF5441 with up to 385 dhrystone 2.1 MIPS @ 250 MHz … Same one as in our other current lineup of products sans the Octatrack. (But before anyone asks - no that doesn’t mean we can run anything on everything, it’s a general purpose CPU and it does very different things across all machines.) All DSP is done in assembler. Our process for this project was that first I made prototypes in Max which I made Max4live Devices out of and sent out to all my colleagues. We then collec…

Two Coldfire MCF5441’s inside

this means what in regards to “CPU” Horsepower vs. other CPU/DSP thingys around ? and what vs. DT ? DT has the same ? whats the price for such thing ? edit: Up to 385 Dhrystone 2.1 MIPS @ 250 MHz

I don’t really know how the Models are optimized and how much resources are remaining for that CPU, I was thinking more of the extra LFO and slide trigs for what might run into constraints.

Redoing the Models UI at this stage around the one knob per function ethos seems the less likely of the reasons, and “we ran out of time” doesn’t necessarily mean that it was ever ready to go in shippable state.

I’d be happy if there were any late updates, perhaps before they go EOL we’ll see a series of smaller fixes for the patient but I do not expect anything offhand. Certainly with dev effort that would not necessarily be backported to the Digitone/Digitakt or Syntakt.

In a world of infinite possibilities and far fewer guarantees, embrace limitations, accept the character of and optimize for what you have today and in front of you!