Issues with MIDI Replace

[Cwilliams]

Hi, I'm having trouble understanding exactly how the midi replace mode works.  I have reviewed the manual but the program behavior doesn't match my expectations.  

What I would like to do is replace midi within a single region, and only the steps that are overdubbed.  I would think that when replace mode is off my incoming midi will merge, and when it is on my incoming midi will overwrite the existing midi.  

So I identify a region I'd like to overdub, set a cycle range, turn on replace mode, and start recording.  But what results seems unpredictable.  Sometimes it will work just fine.  Sometimes it erases much more of the region than I overdubbed.  Sometimes it merges the contents instead of replacing it.  Sometimes it adds additional regions rather than merging.  Sometimes it will only playback the new overdub while the existing region is silent.  And it will do all of these things over multiple takes without changing settings. 

I've spent some time now attempting to clarify the settings I need by changing "Overlapping MIDI Recording" preferences in all manner of ways but I don't see any consistency.  I've actually been confused about this for years so I've always just worked around it.    

Any insight or thoughts on what might be happening?  Or how to get consistent overwriting results when cycling?

Thanks! 

~ Cole  

[Atlas007]

AFAIU, when Replace mode is enabled, it supersedes the Cycle On/Off modes.

Those Replace mode options referring to Region will create (a) new region(s) while those mode options referring to Content will keep the existing region(s).

Those Replace mode options referring to Erase will erase while  Record is enabled, and those mode options referring to Punch will overwrite only when there's incoming MIDI.

 

[Cwilliams]

Thank you, I was wondering whether the replace mode superseded cycle modes. 

And I now wonder if the program tends to error incoming midi over multiple cycles?  Perhaps this is why it starts to error when cycling, because something about cycling affects it?  I've noticed for example that even on my 2020 M1 Mac, over multiple cycles it can't display the graphics properly and becomes glitchy!  I find that interesting.  

[Atlas007]

3 minutes ago, Cwilliams said:

I've noticed for example that even on my 2020 M1 Mac, over multiple cycles it can't display the graphics properly and becomes glitchy!  I find that interesting

I am not experiencing this over here, but I have a different setup than yours...

 

[polanoid]

25 minutes ago, Cwilliams said:

Thank you, I was wondering whether the replace mode superseded cycle modes. 

And I now wonder if the program tends to error incoming midi over multiple cycles?  Perhaps this is why it starts to error when cycling, because something about cycling affects it?  I've noticed for example that even on my 2020 M1 Mac, over multiple cycles it can't display the graphics properly and becomes glitchy!  I find that interesting.  

Can you upload a video of that happening?

[Cwilliams]

Well...I would but I'm not quite so technically savvy, as you might have guessed!  

After some experimentation I think that perhaps there is some tendency for the system to get confused (or maybe I'm the one who's confused) while continuously cycling, as for the most part the replace behavior works predictably over single, discreet passes, especially if I restart the recording on each pass.  

Anyway it seems these issues are not particularly common so I'll keep messing with it.  Thanks again!