gbevin / miditaperecorder Goto Github PK

If I'm recording, and i get to bar 60 (or 160) and that's where I do something I'd like to loop, I have to scroll right back to the beginning to drag the in marker all the way right... would it be possible to, wherever you are, grab the left (or right) edge of the timeline to make the drag start there without scrolling? (if you have it, this is how Koala works when you're zoomed into a sample)
(pinch zoom could/would also help with this)
Thanks Geert!

Would be cool. Thanks for sharing the code / idea openly here. Merry Christmas!

Scenes function where user can record and store multiple scenes (song parts)

This looks incredible – been looking for something like this for a long time!

Maybe you can think about colouring a bit?

For example something like this?

Looking forward testing it!

Cheers!

Record function stays ON when looping even after initial midi data entry.

On output MIDI note data optionally modified from what is on recorded loop to “match” loop playback speed. For example if loop set to playback at half speed outgoing note data optionally shifted down by one octave. Playback speed choice settings would have scale matched “set” points if modify note output is set to on.

Increments or decrements by a set amount per loop to individually selected CC values. For example CC 56 could be set do decrement by an additional 5 (or whatever is chosen) steps for each consecutive loop while CC 57 could at the same time be set to increment by 2 each consecutive loop. Optionally limits for each designated CC could be set such that they could not increment or decrement beyond that regardless of the loop playback counter. The recorder MIDI loop data remains exactly as recorded just like now; the only thing that changes is a counter for number of loop playbacks adds or subtracts the increment or decrement to each specified CC each time the loop is played. Ideally the desired CC number and increments/decrements per loop could be configured for a loop before recording it.

It would be great to have exclusive solo/track switching, in my case I'm using MTR as a CC Looper and would like to approach each of the four tracks as a saparate part, for the purpose of each MTR track is sending out the same CC numbers/values but with a recorded variation per track. many thanks ahead!

If it was possible it would be good to be able to loop each track independently of the others so that a bass line or sequence could be looped rather than having to record it fully in real time along whole length of the recording.

Or even if you could cut and paste sections would be a benefit.

Also like Fugue Machine, independent track play speeds would be nice

plugin opens full screen + not resizable
macos 13.0.0+13.0.1 - ableton live 11.2.6

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)

Thanks for this very useful midi recorder @gbevin
I know that this is not main usage of the tool, but it is also super convenient to listen to midi files.
When I select a midi file, it goes back to the main screen. If I want to listen to another midi file, I have to click on the top right, then on the blue arrow, to open another file.
I'd like to have the possibility to stay in the file manager in order to listen to another midi file easily. Maybe the file manager could stay open, only take half the window and be closed automatically if I touch outside of the file manager? (or any other method that facilitates the preview of midi files).

Hey! It would be fantastic if the ruler on the top was bar based not beat based, the numbers become impossible to follow fast in my personal experience.

Keep up the good work!

Loop playback speed and direction. Ideally both could be controlled by incoming MIDI CC messages and/or could be set statically before recording a loop. For example one could set up to play loop back at half speed reverse immediately after recording concludes.

thanks for this awesome audio unit and thanks that you share your work as open source project. would you consider in the next version an option of disabling auto disarming recording to let endlessly overwrite content of the recorded track in loop? the issue with the current behavior is that during jam it's not always easy to begin recording from the zero point, that causes empty part in the begging of the track. If you don't consider this option as a part of next releases how hard is this to disable it on my own in the code?

Overdub existing MIDI information