first of all thanks for your work. This plugin could be a perfect friend for live-looping performers, however it misses some key points that actually make it not usable.
I am one of those live-looping performers who decided to abandon this plugin. Here my reasons:
1) no over-dub: strangely, no option is provided to over-dub a record.
2) auto rec-off: as a consequence of 1), the plugin automatically turns off recording when the end marker is reached. Usually, this is not requested while looping is performed.
3) first (or last) event problem: usually, the first (or last) played event is not recorded, or it is recorded in a strange way
4) the "clear" button: either for a track or for the global view, the clear button is not a one-click operation, since it requires two clicks to be performed. This is extremely painful when the "clear" event must be automated from a daw/live host. I was not able to send a clear event from Mainstage to MIDITapeRecorder. I suspect it is due to this double-click implementation.
5) no midi filtering: especially in live looping, it is fundamental to filter out some midi message from being recorded, such as a subset of CC messages. in addition to that, the user should be able to decide if such filtering must be applied only to the recording (messages marked as filtered are requested to pass through, but not to be recorded) or both to the recording and to the monitoring (messages marked as filtered are not recorded neither are passed through).
Hoping this feedback helps developing a better plugin for real application in live looping.
Hi,
first of all thanks for your work. This plugin could be a perfect friend for live-looping performers, however it misses some key points that actually make it not usable.
I am one of those live-looping performers who decided to abandon this plugin. Here my reasons:
1) no over-dub: strangely, no option is provided to over-dub a record. 2) auto rec-off: as a consequence of 1), the plugin automatically turns off recording when the end marker is reached. Usually, this is not requested while looping is performed. 3) first (or last) event problem: usually, the first (or last) played event is not recorded, or it is recorded in a strange way 4) the "clear" button: either for a track or for the global view, the clear button is not a one-click operation, since it requires two clicks to be performed. This is extremely painful when the "clear" event must be automated from a daw/live host. I was not able to send a clear event from Mainstage to MIDITapeRecorder. I suspect it is due to this double-click implementation. 5) no midi filtering: especially in live looping, it is fundamental to filter out some midi message from being recorded, such as a subset of CC messages. in addition to that, the user should be able to decide if such filtering must be applied only to the recording (messages marked as filtered are requested to pass through, but not to be recorded) or both to the recording and to the monitoring (messages marked as filtered are not recorded neither are passed through).
Hoping this feedback helps developing a better plugin for real application in live looping.
Best regards, Luigi (calmo)