Retrospective MIDI Record is a breakthrough tool!

[peteruno]

I don’t know why I haven’t seen widespread praise and awe for the new Retrospective MIDI Record feature!!!!!! This feels for me like a major breakthrough. I’ve only installed DP10.11 for a day and 3X already I’ve used the feature. Don’t know about you but often times I’ll get distracted from music I’m working on, field a call or do some office work and then noodle around with a patch I’ve set up in DP. Quite frequently I’ll be in the zone and am so used to magical moments returning to the gods never to be heard again that I feel like Retrospective MIDI Record is a gift from heaven!

BTW: I hope I am posting this in the proper place as I seem to have been orphaned from the motumac yahoo group. Did that actually migrate to another location?

[MIDI Life Crisis]

Can't argue with that...

viewtopic.php?p=570948#p570948

It was available to a lessor degree on my ATARI (Edit/SMPTE Track apps from Opcode). DP has a lot in common, including the ability to have multiple sequences (chunks) in a project. Major timesaver and one of the most important features in DP, IMO.

[CharlzS]

BTW: I hope I am posting this in the proper place as I seem to have been orphaned from the motumac yahoo group. Did that actually migrate to another location?

Yahoo shutdown groups and deleted the content. They still have some type of email functionality, but not sure what that is.

[HCMarkus]

welcome peteruno!

[MIDI Life Crisis]

welcome peteruno!

Welcome? He's been here longer than most of us! lol

[dix]

Has anyone worked out the deal with the Retrospective MIDI Record buffer? I was doing some exceptionally sparse noodling recently and the RMR only got the last note. I guess RMR must stop recording after a given period of inactivity, but I can’t work out exactly what it is...I think keeping the sustain pedal pressed keeps it engaged, but thinking about that sort of defeats the whole purpose.

[MIDI Life Crisis]

Good question. I suspect that every time the transport is activated the buffer clears and starts refilling.

[kinnylandrum]

I wish Retrospective MIDI Record would do what Audio record now does, which is start recording MIDI BEFORE a punch in happens. I have definitely have New York Time, and as such am slightly on top of the beat (5-10 ticks). So I've noticed that if I set a punch in, say, for a downbeat I want to start on, I have to set it a few ticks early to make sure the first chord or note gets recorded. Happens all the time. Wish I could set a punch in point for when I want to start recording, but it would actually start recording a smidge early, so I wouldn't lose the first chord. Is there anyway to set Retrospective MIDI Record to do this?

[SMS]

I wish Retrospective MIDI Record would do what Audio record now does, which is start recording MIDI BEFORE a punch in happens. I have definitely have New York Time, and as such am slightly on top of the beat (5-10 ticks). So I've noticed that if I set a punch in, say, for a downbeat I want to start on, I have to set it a few ticks early to make sure the first chord or note gets recorded. Happens all the time. Wish I could set a punch in point for when I want to start recording, but it would actually start recording a smidge early, so I wouldn't lose the first chord. Is there anyway to set Retrospective MIDI Record to do this?

So obvious this should work. I've also been suggesting to MOTU for years to have 'auto-punch' that would engage record upon receipt of a MIDI event OR EVEN audio above a threshold. If it enables a bit late, use the 'pre record buffer' feature....

[HCMarkus]

I like the "Auto Punch In on Data Received" idea. That said, punching in or out with MIDI often poses issues, particularly if one is working on a part that includes controller info, like sustain or expression or breath control. In tight spots, I have taken to simply adding a new Similar Track, erasing the "flub zone" in the original track, and recording replacement performance on the new track. It makes fixing simpler, and any adjustments that may be required on the new data, isolated on its own track, are a piece of cake. Once everything is copasetic, the new data can be combined into the original track to keep things streamlined.

[SMS]

Yes I frequently do that too, overdub on a new track... Or delete the bad section and record with the merge function on....

I don’t see why it would behave any differently then when you set a timeline based auto punch… It still has to decide how to deal with existing controllers, etc. which DP seems to do very well.

[HCMarkus]

Yes I frequently do that too, overdub on a new track... Or delete the bad section and record with the merge function on....

I don’t see why it would behave any differently then when you set a timeline based auto punch… It still has to decide how to deal with existing controllers, etc. which DP seems to do very well.

You're right; no difference to DP, but it makes it easier for me to perform whatever manipulations may be required to make the new data work properly with the preexisting data.

[SMS]

Yep

[bayswater]

I just read the manual chapter on this, and realized that it works a lot like the old MOTU Freestyle recording function. If you use it at the start of a project, it will detect the tempo of your MIDI and use that in the Conductor track.