With so many different generators running at the same time, I do believe an early warning system about CPU/SD speed limit could be a lifesaver during live performances.
I like the idea. I would like to design it to be fault tolerant enough to not need it, but I think having some high level metrics available somewhere would be useful.
The button layout seems a bit problematic. The most important buttons are hidden behind the data knob. And with two hands it’s too easy to accidental start stop as the shift button is right behind it. Better get a bigger shift and fool proof start / stop buttons. Not to bash your product. The spec seems amazing. The components too. But from a HCI / Interaction pov I see this as a problem.
This tune deserves a release!
Hitting that drexciya vibe sick af
With so many different generators running at the same time, I do believe an early warning system about CPU/SD speed limit could be a lifesaver during live performances.
OTOH that might cost too many computons and make it all more fragile?
I like the idea. I would like to design it to be fault tolerant enough to not need it, but I think having some high level metrics available somewhere would be useful.
It should not be possible. What are you gonna do when the warning comes up on a peak moment. Let it cool down? 😂
@@MultiMam12345optional water-cooling module!
Where can we find out more about/ support ?
@@violetceles8849 I have a signup page at audioenjoyer dot com
whats going to be the max polyphony of a dexed voice?
There are currently 4 instances of the dexed engine running on the xr-1, each with 4-voices of polyphony available.
The button layout seems a bit problematic. The most important buttons are hidden behind the data knob. And with two hands it’s too easy to accidental start stop as the shift button is right behind it. Better get a bigger shift and fool proof start / stop buttons. Not to bash your product. The spec seems amazing. The components too. But from a HCI / Interaction pov I see this as a problem.