Jump to content

Recommended Posts

Posted

I've recently been overhauling and re-organising my entire VI collection after acquiring a larger SSD. A useful exercise! I've had to give a lot of thought to how I use all forms of templates when working with OM.

 

It might be useful to collect various template use options together. By 'template', we could mean any of the following:

 

a) DAW or VI host templates

b) instrument-set and sound-set templates in OM

c) OM code templates

 

I'm interested to find out what other users are doing.

 

I think a) is well discussed in many contexts. There are hundreds of posts on VI Control forum about this and Stephane has also posted on the OM forum and shared examples and has a really helpful course on Composer Workshop too. I think for standard instrumentation (fixed orchestral or chamber ensembles) this is obviously a good option for most use cases.

 

However, as I develop my own OM workflow, I think that there are alternatives to the standard 'one big' DAW/host template approach when working with OM due to the flexibility on how one can define multiple instrument-sets and sound-sets. This is particularly the case when combining standard ensembles with other sound design considerations or when wanting to try non-standard groupings or to improvise. In those instances, I want more fluid interaction with both code and sound sources. 

 

I have been developing an approach using Reaper (DAW) template tracks and track groups -then further nested in templates for projects - linked to very flexible multiple  instrument-set/sound-set definitions/files that allow for iterative work 'on-the-fly'. This permits a really open-ended way of working while also having access to all the power of cc definitions, key switches linked to OMN articulations and so on. It's a work in progress but will share when the re-organisation is finished as it will likely cross-reference to other DAW/hosts. My other main sound-design/composition tools are Bitwig Studio and Usine HH and this template approach also works in those.

 

For c), what sorts of OM code templates are most useful and what are people commonly using, other than OM's built in template def-score templates?

 

best wishes

 

Andrew

 

 

 

 

  • 4 weeks later...
Posted

It's a massive task and still a work in progress but there is progress nonetheless! Will post more when things are sufficiently developed. I can confirm though that OM and Reaper make for a really powerful combination leveraging their respective strengths of soundsets/instrument sets linked to template tracks rather than a large template of everything in fixed format. I now have it set up with 48 ports of 16 channels each via virtual MIDI and it works flawlessly linked to multiple instrument set definitions. The only fixed 'wiring' is the template track ports-channels and their respective instrument set port-channels and everything else can be used on a case-by-case basis. Extremely flexible.

 

I spotted that a few other Reaper users on VI Control do something similar to this, so have been learning from their suggestions. I presume that other DAWs could replicate this way of working but Reaper is something of a maverick so it might not be quite as straightforward on other platforms. I understand that Cubase track presets might offer similar options but not being a Cubase/Nuendo user I cannot confirm.

 

Andrew

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

Terms of Use Privacy Policy