Chord:
It iterates through all elements in the order they were added.
You hear the result momentarily, and then press the note for the element you want to work on.
It is for EDITING, not for PLAYBACK.
I've implemented the button.
The button doesn't work in LV2; I have no idea why.
On the desktop version, relying on QObject::connect drastically affects performance.
Without the button, it works in both environments and performance is good, but it's designed for editing, not for live playing...
In fact, who plays back audio with the GUI open?
There must be a solution to these issues... that is the core concept.
Chord:
It iterates through all elements in the order they were added.
You hear the result momentarily, and then press the note for the element you want to work on.
It is for EDITING, not for PLAYBACK.
I've implemented the button.
The button doesn't work in LV2; I have no idea why.
On the desktop version, relying on
QObject::connectdrastically affects performance.Without the button, it works in both environments and performance is good, but it's designed for editing, not for live playing...
In fact, who plays back audio with the GUI open?
There must be a solution to these issues... that is the core concept.
And it can be tested with just two lines:
pDrumkUi->setCurrentElement(key);
activateElement();
And the concept is the difference between suffering while editing and enjoying it.
So, I maintain that the functionality is worth it.
It just needs to be made efficient.