It’s driving me crazy. After all these years I couldn’t make Cubase create Parts that automatically resize to the containing events when recording. I remember this was working perfectly well in Emagic Logic on the good old Atari.
In Cubase however, it’s a mess since Cubase creates a huge Part even if you record just a few notes. So it’s a lot of work everytime you record something to remove the empty areas.
I tried to find a solution for this but I failed. And I have to say I hate Cubase’s behaviour to death. It really tries my nerves. The longer the more.
Tell me there’s a hidden feature to enable automatic fitting of Parts according to the events.
The part follows the song lenght from the start to the end, if you play the first note in a particular track at bar 12 you will get 11 bars empty before, and after in case of silence with the relative rests.
Not sure but I think that you can get the part resized if you crop the track and select it before opening that score.
This is not exactly what I want. I expect Cubase to recognise the first note played and when the last ends and size the part accordingly without me doing anything about it. I mean Logic was capable of this 30 years ago, way ahead of anything AI. And Cubase still behaves like a stupid and generates a whole track for some bits of MIDI notes forcing me to cut/crop. This isn’t real.
If you are recording and then stop, that should be the end of the part. Are you suggesting the part continues after pressing stop? Since you said note, I’m assuming midi and not audio?
Can you further explain this? Are CC’s being generated after you stop playing notes? If so, then yes the part continues until there are no further midi notes including any cc data.
I understand your need and honestly it would be helpful to be able to narrow down individual tracks in a score with just one click. Though I found this:
Set the left and right locators to surround the part you want to see.
Thanks for your suggestion, but to be honest, this requires me to deal with locators all the time. Let’s assume I am just collecting ideas through improvisation and experimenting, this would cause me to know the outcome already. It’s just not convenient. Workarounds are always what they are: work. Additional work, that’s not required because things could be simple, easy and convenient.
True, if I hit the stop button, the part ends. However, depending on the position, it will put a huge empty area in front of what you record. For no reason. I often put something on cycle and I really don’t want to deal with locators all the time.
And yes, I am talking about MIDI/VSTi-Tracks here. And no, no further CC’s are generated. But that wouldn’t be a problem because that data would be part of the recording anyways.
Yes, it’s a question of convenience. But it also speeds up the workflow if you don’t have to shape every single Part manually. I simply can’t believe this is no option in the preferences.
I have no clue if Logic still does this right, but I guess so. It would make sense.
When you press record regardless of midi or audio, it should start exactly where your cursor is. No empty area in front. However in settings, you can arrange it to start prior to where your cursor is. I’m not in my studio atm so I can’t remember, but I’m sure someone will chime in soon.
In Safe Mode, with user preferences disabled, do you get this same behavior?
It depends whether Cycle is on or off. If it’s on, it’ll create a huge Part. If it’s off, it doesn’t. This doesn’t make sense.
Still, if you don’t start playing something immediately, it will still create a big empty area in front of it - depending on how long you wait until you play something. If you start recording and don’t play anything, it will not create a part at all. So Cubase can recognise whether something is played or not. So why not WHEN and for how long? This feels wrong.
As you already noticed during cycle recording the part length equals the duration between the locators.
Additionally there is a preference whether part boundaries should always be set to full bars or not.
Other than that, you should issue a feature request. You might not believe it but this is not a very common request. In fact I can remember only one occurence where this was requested before.
You said you don’t want to have to do anything in order to trim the parts. In case a key command is okay for you I created two macros for trimming parts. It should be possible to combine them.
I’ll vote for this if the OP makes it a feature request. I’ve also missed this having used Logic, and snapping MIDI parts to bars is not really the same. I thought Logic achieved this via some no overlap setting, but I could be wrong. When MIDI regions overlap (compared to when they don’t), various functions in DAWs do not work the same way, i.e., some functions don’t work as expected when regions overlap. I would prefer to optionally glue sparse regions together instead of being forced to split overlapping regions because the DAW applies the same “tape recorder” model for recording audio when it comes to recording MIDI.
