Notifications
Clear all
MONTAGE Series Synthesizers
3
Posts
2
Users
0
Reactions
1,415
Views
Topic starter
I spent some time today working with the new pattern feature. I got it to work, but I ran into something odd.
I was working with Cubase 10 Pro. I had three MIDI tracks in Cubase that I wanted to simultaneously record into the pattern. So I would set things up and hit "play" in Cubase. The tracks would play for the number of bars I set on the Montage, but sometimes nothing would get recorded in the pattern.
It took me a while to figure out what the crucial thing was. In the pattern, I had the three parts I wanted to record into set with KBD CTL on. I was under the impression that this was all it took, but I was wrong. In addition, one of those parts needs to be selected (i.e. hilited). Once I had that figured out, everything worked.
This extra thing seems superfluous to me. I've already got KBD CTL set on the parts, why does one of them have to be selected? Is there a good reason for this? If not, I think it would be good to just allow KBD CTL to control this, without the extra step. If that's how things were, it would have saved me an hour or so of doing various experiments to work out what was going on.
Posted : 07/10/2019 1:33 am
Topic starter
Once I got my pattern working, I wanted to "associate" it with the performance. I couldn't find the control to do that with.
But then I remembered that I had loaded the performance into the Montage using the Melas Total Librarian. So the performance was sitting in the Montage edit buffer, and it makes sense to me that there would be no way to link a performance from there to anything, including a pattern. So I stored the performance into an available slot and then I was able to do the link.
Posted : 07/10/2019 1:51 am
It took me a while to figure out what the crucial thing was. In the pattern, I had the three parts I wanted to record into set with KBD CTL on. I was under the impression that this was all it took, but I was wrong. In addition, one of those parts needs to be selected (i.e. hilited). Once I had that figured out, everything worked.
This extra thing seems superfluous to me. I've already got KBD CTL set on the parts, why does one of them have to be selected? Is there a good reason for this? If not, I think it would be good to just allow KBD CTL to control this, without the extra step. If that's how things were, it would have saved me an hour or so of doing various experiments to work out what was going on.
It is not KBD CTRL that determines what gets recorded. We go over this in the article. It is a Performance Recorder, it records what you perform.
Performance basics apply. If you have 2 Parts linked by KBD CTRL and 14 Parts individually setup as your 16 Part Performance, in order to play the two linked Parts you must either *select* one of them or place the cursor in a “Common” area (for example, highlighting the Performance Name on the HOME screen). If you select one of the Single Parts you are set to record it. The KBD CTRL Parts stay paired, but you select some other non-linked Part.
Your statement “I was under the impression that this was all it took...” is incorrect. What you *select* is what you hear, and what you hear is what is recorded. It’s a Performance Recorder. If you switch your selected Part during Record, the Performance Recorder will Record that you did that.
Call up a Multi Part Factory Performance, add a couple of non-KBD CTRL linked Parts. Discover how and when you are playing the linked Parts and how and when you are playing the individual Parts. Same as it always has been.
Selecting any one of the KBD CTRL Parts is to select the group.
Extra Credit: Recommended Reading
OS v3.0 Pattern Workflow
See the paragraph “Important things to know”
Posted : 07/10/2019 5:43 am
