Chordprogressor (CP) has a carefully chosen and developed feature set, but it also comes with two properties which could be considered as quirks:
a) there is no undo, except for a few dialogs, which restore the previous state if left with cancel
b) the overall realtime performance most likely can't rival the one of your favourite digital audio workstation which employs more low level programming.
Why that? (Warning: it'll get quite some technically here)
a) An undo function for an application or plugin with a rich set of realtime controllers which can be changed intuitively by the user is likely to generate substancial undo data, which has to be stored somewhere. To make ChordPorgressor usable on as many platforms as possible while at the same time keeping the development expenses in a reasonable bandwidth, JAVA was chosen as the development platform. While JAVA takes care of all the memory handling which eases the development process significantly, this at the same time means, you don't have much control over when it handles the memory management. But when it does, it might seriously interfere with other processes going on. This means: at that point in time usually the timing goes down the drain. So one development aim was to keep the memory impact as low as possible. Which unfortunately is diametrical to a detailed undo functionality. Additionally the implementation of an application wide undo is anything but trivial and will therefor eat up substancial development time. So ChordProgressor was chosen to work like the real life: no undo.
b) As described above JAVA has been chosen as development platform, which is indeed a bit adventurous when it comes to realtime requirements. So some of the initial concerns proved to be right, but in the end a workable solution was found. There seems to be another possible option for the heartbeat of the sequencing engine in CP in JAVA, but that would have meant that CP wouldn't work on older operating / JAVA systems lacking the javax realtime support. The result of this tradeoff is, that CP's timing is mostly decent, with a few hickups here and there depending on how much pressure you put on your system, while running CP.
So if you consider either a) or b) a show stopper for your needs, ChordProgressor is likely to be not the right companion for you.
To get a more into depth overview on ChordProgressor, please download the manual of ChordProgressor here:
ChordProgressor Manual (PDF)
a) there is no undo, except for a few dialogs, which restore the previous state if left with cancel
b) the overall realtime performance most likely can't rival the one of your favourite digital audio workstation which employs more low level programming.
Why that? (Warning: it'll get quite some technically here)
a) An undo function for an application or plugin with a rich set of realtime controllers which can be changed intuitively by the user is likely to generate substancial undo data, which has to be stored somewhere. To make ChordPorgressor usable on as many platforms as possible while at the same time keeping the development expenses in a reasonable bandwidth, JAVA was chosen as the development platform. While JAVA takes care of all the memory handling which eases the development process significantly, this at the same time means, you don't have much control over when it handles the memory management. But when it does, it might seriously interfere with other processes going on. This means: at that point in time usually the timing goes down the drain. So one development aim was to keep the memory impact as low as possible. Which unfortunately is diametrical to a detailed undo functionality. Additionally the implementation of an application wide undo is anything but trivial and will therefor eat up substancial development time. So ChordProgressor was chosen to work like the real life: no undo.
b) As described above JAVA has been chosen as development platform, which is indeed a bit adventurous when it comes to realtime requirements. So some of the initial concerns proved to be right, but in the end a workable solution was found. There seems to be another possible option for the heartbeat of the sequencing engine in CP in JAVA, but that would have meant that CP wouldn't work on older operating / JAVA systems lacking the javax realtime support. The result of this tradeoff is, that CP's timing is mostly decent, with a few hickups here and there depending on how much pressure you put on your system, while running CP.
So if you consider either a) or b) a show stopper for your needs, ChordProgressor is likely to be not the right companion for you.
To get a more into depth overview on ChordProgressor, please download the manual of ChordProgressor here:
ChordProgressor Manual (PDF)