Cannot record multiple takes on MIDI tracks when looping

Cubase
,
1

Hi,

I am recording on a MIDI/instrument track. I want to loop a few bars and record multiple takes, then check the takes and pick the best one. After I stop the recording, only the last take will be there, and all the other takes are gone. Is this the normal behavior?

When recording audio tracks everything works as it should, and after recording the loop I can pick any take I want.

I already tried googling for solution, asking AI, I even tried it on a different computer and different version.

I am using Cubase Elements 13 on a Windows 10 PC, Focusrite Scarlett 8i6. MIDI record modes are New parts and Keep last.

Is it just not possible to do what I think should be possible? Or is there some setting that I am missing?

image
image492×564 11.4 KB

Here is a video of how I am doing it.

Thank you for any help!

2

Hi, @Vinkler.Radomir

I would suggest, first, to activate the lanes visibility with the Show Lanes button in the track header (you can set a shortcut for the Edit > Show Lanes command, if needed). This, to see what is going on.

After this, sadly and contrarily to the Pro version, in Elements, there is no Stacked option among the MIDI Cycle Record Mode available ones. So, and AFAICS, the only way to record multiple takes with your Cubase version is to :

  • Activate the Cycle mode.
  • Use the punch-in/out feature, with the Punch-in point set JUST AFTER the position of your left locator, i.e., set it at 1.2.4.1 if the latter is at 1.2.4.0. Otherwise the same lane will be used for all your recording passes.
  • Consequently to the Punch-In/Out activation, launch the record with the Play control in the transport bar.

Not ideal, but it’s the only way I see to approach Cubase Pro behavior, when its Stacked option is activated. But maybe someone else with the Elements version will have a better suggestion.

3

Hi, @cubic13

Thank you very much for the suggestions. I didn’t know that Stacked option is available only in the Pro version, that is probably the problem.

Thanks for the workaround, I will try it later and see if it at least helps with the issue.