[mtr] and overdub


    Dec 09 2020 | 5:31 pm
    Here is a question about best practices with [mtr].
    Let's imagine I have a 1-track mtr and I want to implement a kind of overdub function. Read overdub here as in "always add data, never delete it" - this is slightly different from the "touch" built-in feature. See below the patch I came up with. Since I'm using a "touch"-based kind of trick, there is a chance that if a new event arrives at exactly the same time as a previously recorded event, the latter would be erased, right?
    In mtr, is there a way to query a track asking "what is the current time?" - in that case I could use and addevent function instead of a touch trick?
    Any advice appreciated, thanks!

    • Dec 09 2020 | 5:32 pm
      By the way, internal [transport] must be active for play to work in the attached example.
    • Sep 22 2021 | 3:55 pm
      Hi @JEAN-FRANCOIS CHARLES, did you ever figure out a way to overdub with mtr? I’m looking into the same thing.
    • Sep 22 2021 | 4:49 pm
      Yes: this patch I shared in this thread is actually NOT the best method. There are problems when you use the "touch" option this way. It is best to use the 'addevent' message. To do that, you need to query [mtr] first to get the current time, then you can use 'addevent'. Here is a version of that:
      AFAIK, this is the best option for overdubbing with [mtr] at this point.
    • Sep 22 2021 | 7:44 pm
      Alright, great thanks for sharing. I’ll test this out soon.