[FIXED] MIDI recording extend previously recorded item

[Daodan]

Loop MIDI recording extend previously recorded item if that item was recorded in MIDI: Overdub mode.

How to reproduce:
-Create track and set it to MIDI: Overdub mode
-Record short midi item (item_1)
-Create time selection around item_1
-Enable repeat
-Create second track and record another midi item in time selection (item_2). Important: Don't stop recording until the end of time selection.
-Reaper extend right edge of item_1 to the end of time selection.



Expected behavior: recording one track doesn't affect items on other track.

If you glue item_1 than everything fine:



Tested in my Reaper 6.28 config and also in clean portable 6.28, 6.25, 6.12 and even 5.32🙂
----------------------
fixed in 6.55 THANKS!

[Synthezx]

I would like to add information on this issue.
This works great if you choose the input as: Record input (audio or midi), in which case the midi will not propagate until the end of the loop either. But i like work with "Overdub" input.

It's very complicated to write my next midi item through my midi keyboard with a loop (I work a lot with a loop)

[Daodan]

bump 001

[Daodan]

Should I post it in Dstruct's Casa De Nitpicks?

[Daodan]

bump.

[Daodan]

no one can reproduce?

[Daodan]

June Bump

[Daodan]

6.31 bump

[zookthespook]

confirming the issue. I have been having this since 5.xx versions

https://i.imgur.com/CnAx4BY.gif

[Daodan]

Originally Posted by zookthespook

confirming the issue. I have been having this since 5.xx versions

https://i.imgur.com/CnAx4BY.gif

Nice, thank you.

[mccrabney]

seems that this only happens when you've got "All MIDI inputs" selected.

i had a hard time reproducing this until i noticed that part of Daodan's original post. my default project template has each MIDI channel from my melodic controller as its own armed track, and i was unable to reproduce this issue using that setup.

[mccrabney]

nope, now i'm seeing the same behavior with Virtual MIDI keyboard inputs on ch 1.

maybe it's not the MIDI input, but the process of track creation? i was able to reproduce by duplicating the first recording track, disarming it, and recording on the second track...

edit, yes, that's definitely it. here, i have my default template's ch1 MIDI input track in overdub mode. i record some MIDI, disarm/duplicate the track, arm the duplicate, record in the time selection, and watch the MIDI item in the disarmed track lengthen automatically.

[Daodan]

Originally Posted by mccrabney

nope, now i'm seeing the same behavior with Virtual MIDI keyboard inputs on ch 1.

maybe it's not the MIDI input, but the process of track creation? i was able to reproduce by duplicating the first recording track, disarming it, and recording on the second track...

edit, yes, that's definitely it. here, i have my default template's ch1 MIDI input track in overdub mode. i record some MIDI, disarm/duplicate the track, arm the duplicate, record in the time selection, and watch the MIDI item in the disarmed track lengthen automatically.

Thanks, Mccrabney. Idk but I create tracks with default action just by doube click in TCP. Also same happens if last recorded track not in overdub mode. Previous should be.


project attached

[Daodan]

Bump for 6.40

[Kicks]

I confirm I have this exact same bug since I use Reaper. So its here for at least 2 years.

It would be awesome to fix that because it is quiet frustrating, that prevents us to record freely. I dont know why there isnt more people complaining about it? are they using midi packs?? hihi

I checked in my Action list if i didnt change something, there is indeed an option called : loop recording always add takes to newly recorded items
But it wasnt that...

[Daodan]

Originally Posted by Kicks

I dont know why there isnt more people complaining about it?

Idk. Maybe overdub mode not so popular?

[Kicks]

What OS are you on Daodan?

By the way, thanks for doing all the reporting and video. Im gonna help you bump the topic ahah

[Daodan]

Originally Posted by Kicks

What OS are you on Daodan?

By the way, thanks for doing all the reporting and video. Im gonna help you bump the topic ahah

Thanks you! I’m on Win 10

[Kicks]

OK, I'm on Win7, so the bug is not OS relative

[Kicks]

bumb!

[Kicks]

bump!
reminder (as the title isnt complete) : it happens only on Midi Overdub mode

[Kicks]

Bump!

[Kicks]

Here is the result :

[zookthespook]

@justin frankel please fix this .
It has caused some serious damage on project s while working

[Kicks]

UP! this huge bug is still not fixed

[Daodan]

Yup

[Denys]

I've always had this issue and kind of got used to it to the extent that every time I record MIDI, I stop playing before the cursor goes back to the beginning of the loop. If I don't do so, it's overlap festival in my project.


But as usual, I've tweaked so many parameters in Reaper that I can't say for sure I didn't change a setting by mistale.


If it's a bug: massive +1.

[zookthespook]

Because of this bug , i have stopped loop recording.
Moved to reaper in 2014 , i really did miss the retrospective recording feature. I understand,reaper being the mega monster that it is , i didn't care about the small barter ,but loop recording is a core feature of Daws and electronic sequencing hardware since the 80s , let's not turn that into a barter now. There are always workarounds but non buggy loop record mode is the least one can ask for from a DAW.

[schwa]

Finally reproduced, fixing!

[Daodan]

Yay! Thank you!

[Kicks]

Awesome !