What's new

A different take on Cubase templates

so I had few people reaching out and asking questions about the process. I realize that it might not be that convenient to go through the thread and read the wall of texts on how it works. So I made a quick overview video on how I'm using it right now. Excuse the accent. English is not my mother language. ;)
Hope it's gonna be useful to some.
Cheers


0:00 Quick Intro
0:37 The template
2:36 Adding a track preset
5:20 Creating a track preset
9:13 A workaround for route/send
10:10 The Media Bay
11:50 How to get just YOUR instrument in the browser
15:00 How to disable the previewer
17:32 Using the right pane
19:58 Quick words on the different templates approaches I used before.
 
Last edited:
Dear Grizzlymv! Thanks for the great video! I have a question. How do you manage to save the send slots in the track preset? When I save a preset track, this information is not saved.
 
Dear Grizzlymv! Thanks for the great video! I have a question. How do you manage to save the send slots in the track preset? When I save a preset track, this information is not saved.
Just to clarify, it doesn't set any Sends you had configured in your track. It just automatically reconnect, in a disabled state, all sends from your project. To enable this, open the Cubase preferences. Under VST, you'll have a "Connect Sends Automatically for Each Newly Created Channel". Just ensure the checkbox is checked and voila. ;)

1623445850243.png
 
I ran some tests to keep the send slots. If a track preset contains information in the first slot (for example, a reverb track), then when this preset is placed in a new project, the first existing track with an effect is substituted into the first send slot of the track being created. Is that correct? And this only works if the "Connect Sends Automatically for Each Newly Created Channel" option is enabled in Cubase. But what if my empty template has separate effects for different groups of instruments (xBRASS VERB, xWW VERB, xSTR VERB and so on)?
 
This is very intriguing and wonderful idea @Grizzlymv.

Believe it or not! I dumped the whole "template" idea and I decided to always start from a blank canvas. And I haven't been happier. Adding tracks as I go with composing is like painting and I focus more in creativity than the office work of creating/organizing/maintaining templates or even track presets. I mean it's all about a fast workflow right? ... I really don't see the 15 seconds of adding a track and selecting an instrument is a major issue. And I still use macros triggered by my Elgato stream deck to provide speed in creating those tracks, put them in Group and FX channels. And yeah, I don't get bothered from inserting EQ and effects manually in each project.

I really get the same speed result which is finishing a track (song) in 8 hours balanced, mixed and mastered. I honestly get that feeling that "templates" is more of a Buzz word and hype that every composer dream of to get as fast as possible with projects. The truth is, you're not getting any faster with templates. Or maybe it's just me who is bloody fast with empty canvases? :)
Do you use expression maps?
 
Do you use expression maps?
I rarely use a patch with multiple articulations. I always use a single articulation per track. But If I use a multi articulations patch, I use keyswitches very easily since I am a keyboardist in the first place. It may be hard for many composers.
 
The system of building templates from track presets is, of course, very convenient. But what to do in a situation when an update of some library appears? Every preset has to be redone!
 
The system of building templates from track presets is, of course, very convenient. But what to do in a situation when an update of some library appears? Every preset has to be redone!
Well, that depends on the hosts, but if something like Kontakt, yes unfortunately. However, the same issue happen with a disabled track template or if using a VEP template so it's not so different from that point. That being said, what I would usually do is to update them as I load/need a track preset. That way I get annoyed only when I try to load a track preset which need an update, rather than be forced to update all instances at once. I wish there would be a smoother update process with Kontakt, but so far, I had that issue with all template approach I used over the time. The only difference I see with track presets is that since it's quite easy and convenient to create those, you may end up with more instances than in a typical template over time, so more updates to do. ;)

Here there's still several presets that hasn't been updated yet, some for quite some time, but been able to work with that hybrid mode without issues. In the end, I have updates to do here and there, and for those I haven't updated yet, maybe it's more a question of, do I still need that preset after all? ahah.
 
Hey bro, are you still getting along with this method? Any additional pros & cons? I've had similar experiences and feelings about the whole template thingy.
 
Hey bro, are you still getting along with this method? Any additional pros & cons? I've had similar experiences and feelings about the whole template thingy.
More than ever yes. I can't see myself working without this. I did tweaked this a bit over time. I now have a small template for my core orchestral instruments (strings, brass, perc and woods). They are pre-arranged in VEP and loaded as MIDI track in my template. Everything else remain track presets and I just love it that way.

On the Pro side, I'd say that having moved from Cubase 11 to 12 without issue was quite a relief.
Then I also realized that it encouraged me to do more of my own design/experiments by quickly saving variation of a source, with some fx or merged libraries. In the end, I end up slowly creating my colors and less relying on out of the box presets from a library like I used to do.

On the Con side, 2 things I'd mention. One is if you or update a library that has significant change, then you'll have to re-save your preset with the new path otherwise you'll get nagged by a prompt to local the samples every time you load it. But that's mainly because of my laziness.. :P

All in all, the pros still outweighs big time the cons for me so I don't see myself moving away from this way of working anytime soon.

Hope this helps.
 
Track Presets are great! Excellent workflow!

We are having an issue with certain tracks (not all, only a select few) not retaining the correct Expression Map when imported from a Track Preset. Curious if you have seen/had this issue? If so, have you found a solution? Thanks.
 
Track Presets are great! Excellent workflow!

We are having an issue with certain tracks (not all, only a select few) not retaining the correct Expression Map when imported from a Track Preset. Curious if you have seen/had this issue? If so, have you found a solution? Thanks.
Personally, I haven't seen that issue so far. But then again, I use expression maps mainly on my orchestral libs (CSS, CSB, CSW, MSS, MSB, LASS3) so it's not a super wide range. That being said, the file I'm importing the track presets in is usually the same one that was used to create the track preset, so maybe that help? Also, the core of my orchestral tracks are in my default template as disabled tracks, so while I do have to load extra tracks as track presets, it's not something I have to do often for my orchestral instruments mentioned above. So maybe I do have the issue too, but just haven't experienced yet due to the fact I don't have to load those with exp maps too often.
 
Track Presets are great! Excellent workflow!

We are having an issue with certain tracks (not all, only a select few) not retaining the correct Expression Map when imported from a Track Preset. Curious if you have seen/had this issue? If so, have you found a solution? Thanks.
After exploring this issue further, we have learned that the Expression Maps that are not returning correctly are those that have identical keyswitch data but with different names. For example, in the Spitfire Studio Strings, many of the patches (Violins 1 (16), Violins 1 (3A), Violins 1 (3B), etc.) all have the same articulation sets and keyswitches. Identical Expression Maps were created and named for each patch - Violins 1 (16) has it's own expression map as does Violins (3A) and Violins (3B) even though the data in the Expression Maps are identical.

Cubase is somehow only saving one of these identical patches with the Track Presets even though they are all assigned. The net result is that the Expression Maps work fine (because they are identical), the names just don't match the patches (i.e. the Exp Map for Violins 1 (16) shows up for Violins 1 (3A), Violins 1 (3B), etc.).

In the end, not a huge problem, just confusing when you first discover it.
 
After exploring this issue further, we have learned that the Expression Maps that are not returning correctly are those that have identical keyswitch data but with different names. For example, in the Spitfire Studio Strings, many of the patches (Violins 1 (16), Violins 1 (3A), Violins 1 (3B), etc.) all have the same articulation sets and keyswitches. Identical Expression Maps were created and named for each patch - Violins 1 (16) has it's own expression map as does Violins (3A) and Violins (3B) even though the data in the Expression Maps are identical.

Cubase is somehow only saving one of these identical patches with the Track Presets even though they are all assigned. The net result is that the Expression Maps work fine (because they are identical), the names just don't match the patches (i.e. the Exp Map for Violins 1 (16) shows up for Violins 1 (3A), Violins 1 (3B), etc.).

In the end, not a huge problem, just confusing when you first discover it.
My workaround to this bug is this:
If I (for example) have an Expression map where I switch between the articulations using keyswitches, I change the "Data 2" value for one of the keyswitch notes in "Output Mapping" section, so it's slightly different, even though the functionality is the same.

My OCD way of doing it is this:
If I setup Expression maps for lets say (Vn I / Vn II / Vla / Vc / Cb) I set it up as follows:
Vn I
Data 1 (C0), Data 2 (1)
Data 1 (C#0), Data 2 (120)


Vn II
Data 1 (C0), Data 2 (2)
Data 1 (C#0), Data 2 (120)


Vla
Data 1 (C0), Data 2 (3)
Data 1 (C#0), Data 2 (120)


Vc
Data 1 (C6), Data 2 (4)
Data 1 (C#6), Data 2 (120)


Cb
Data 1 (C6), Data 2 (5)
Data 1 (C#6), Data 2 (120)


Since Data 2 value represents velocity of the keyswitch note, it doesn't matter if it's 120 or 1, 2, 3, 4, 5 etc.

This way I don't have to check whether two Expression maps are the same and they load correctly while using Track presets, since they are not identical anymore.

Hope it helps!
 
AT LAST! @Grizzlymv ils t'ont écouté!

June 28, 2023 – The Cubase 12.0.70 maintenance update is now available. The main purpose of this maintenance update is the support of the improvements in the VST 3 SDK for plug-in developers. In addition to this, we integrated some fixes for the track import and the MIDI Remote areas, and added support for the Spatial Connect plug-in by our friends from Dear Reality.

The update is immediately available for download via the Steinberg Download Assistant.

We have improved the following features and functionality
VST 3

Support of the new plug-in replacement process of the VST SDK 3.7.8 has been added.

Track Import

Send FX connections are now working correctly when importing tracks via "Import Tracks from Project" and Track Archives.

MIDI output ports are now correctly set when importing tracks via "Import Tracks from Project" and Track Archives.

Routings to group channels are now properly working when importing tracks via "Import Tracks from Project" and track archives.


MIDI Remote

Mappings for Device Surfaces which have "Label Fields" assigned for the "Piano Keys" item are now persistent.

Stability

We have improved the stability when importing track archives using HALion Sonic with content without valid licenses.

We have improved the stability when drawing into the waveform image with multiple clips open in the Sample Editor.

3rd party

Support for the Spatial Connect plug-in by Dear Reality has been added.
 
AT LAST! @Grizzlymv ils t'ont écouté!

June 28, 2023 – The Cubase 12.0.70 maintenance update is now available. The main purpose of this maintenance update is the support of the improvements in the VST 3 SDK for plug-in developers. In addition to this, we integrated some fixes for the track import and the MIDI Remote areas, and added support for the Spatial Connect plug-in by our friends from Dear Reality.

The update is immediately available for download via the Steinberg Download Assistant.

We have improved the following features and functionality
VST 3

Support of the new plug-in replacement process of the VST SDK 3.7.8 has been added.

Track Import

Send FX connections are now working correctly when importing tracks via "Import Tracks from Project" and Track Archives.

MIDI output ports are now correctly set when importing tracks via "Import Tracks from Project" and Track Archives.

Routings to group channels are now properly working when importing tracks via "Import Tracks from Project" and track archives.


MIDI Remote

Mappings for Device Surfaces which have "Label Fields" assigned for the "Piano Keys" item are now persistent.

Stability

We have improved the stability when importing track archives using HALion Sonic with content without valid licenses.

We have improved the stability when drawing into the waveform image with multiple clips open in the Sample Editor.

3rd party

Support for the Spatial Connect plug-in by Dear Reality has been added.
Nice!! However according to the release notes, it's for the import track from project and track archive. I hope they will eventually bring it to track preset as well. But there's hope. ;)
 
AT LAST! @Grizzlymv ils t'ont écouté!

June 28, 2023 – The Cubase 12.0.70 maintenance update is now available. The main purpose of this maintenance update is the support of the improvements in the VST 3 SDK for plug-in developers. In addition to this, we integrated some fixes for the track import and the MIDI Remote areas, and added support for the Spatial Connect plug-in by our friends from Dear Reality.

The update is immediately available for download via the Steinberg Download Assistant.

We have improved the following features and functionality
VST 3

Support of the new plug-in replacement process of the VST SDK 3.7.8 has been added.

Track Import

Send FX connections are now working correctly when importing tracks via "Import Tracks from Project" and Track Archives.

MIDI output ports are now correctly set when importing tracks via "Import Tracks from Project" and Track Archives.

Routings to group channels are now properly working when importing tracks via "Import Tracks from Project" and track archives.


MIDI Remote

Mappings for Device Surfaces which have "Label Fields" assigned for the "Piano Keys" item are now persistent.

Stability

We have improved the stability when importing track archives using HALion Sonic with content without valid licenses.

We have improved the stability when drawing into the waveform image with multiple clips open in the Sample Editor.

3rd party

Support for the Spatial Connect plug-in by Dear Reality has been added.
Actually I did test it with track presets and sadly, still not working. Hopefully in a future update. 🤞
 
Top Bottom