• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

User Template Management

THW

Member
My list of templates in the "user" template list on starting up a new project has gotten quite long over the years with different projects, experiments, and versions of S1. I'm wondering if there is a way I could better organize this list. I know I can move templates around in the file explorer, but I am a little concerned about moving templates to a new folder and creating an issue if I were to then try and open up an old project. I wonder if I made a subfolder within the templates folder, called "archived" if it would remove those older or less used templates from the user list without interfering with opening old projects?

Ideally, I'd like to clean up the number of templates I have in my "user" list, or at least be able to arrange the list in an order I'd prefer. It would be a great feature to be able to click and drag the order of templates. I'd want to put my current "master" template at the top of the list. The only way I can see to do that now would be by changing the template file name to include a number (I think it is the lower the digit, the higher up in the list). It's a very minor inconvenience having to scroll through my user list of templates to get to the one I'm after...I don't have a strict naming convention for templates (I probably should), nor do I have song ideas (I also probably should...but also know I'm not alone in that regard either lol! I do have my 2026 songs folder ready to go though!!)

Curious if anyone has thoughts on this.

Best,
THW
 
Short answer:

I know I can move templates around in the file explorer, but I am a little concerned about moving templates to a new folder and creating an issue if I were to then try and open up an old project. I wonder if I made a subfolder within the templates folder, called "archived" if it would remove those older or less used templates from the user list without interfering with opening old projects?
No, none of this should be a problem. The template files (which are essentially song files with different extensions) are only accessed when you start a new song. The new song is basically (simplified, but still...) a copy of the template. You can safely create an "archive" folder within the templates/v5 / v6 / v7 folder and move outdated templates to this folder.

I'd want to put my current "master" template at the top of the list. The only way I can see to do that now would be by changing the template file name to include a number (I think it is the lower the digit, the higher up in the list).
Renaming shouldn't be a problem either. Here is how it works:

templates-xml.png


Each template consists of multiple files. To change just the display title, you can open the [your-template-name].songtemplate file in a text editor and change the Document:Title. This will be the title that appears in the list and by adding a prefix, you can change the order.

I hope that helps.
 
I like to count things and make lists, which I suppose is an ADHD/OCD activity, and it includes keeping a running rhythm pattern with my feet and, of course, touch-typing, which is a useful skill but also is ADHD/OCD.

Making lists is like making outlines; and the key to outlining is that you need at least to have pairs, where for example if there is a Roman numeral "I", then there should be a "II".

When I first started doing software engineering, I got a job doing COBOL programming; but, even though I have a Computer Science degree, I knew nothing about COBOL programming; yet I realized (a) it was important to look busy and (b) everything in COBOL was procedures that were performed; so I would start a new program with something like the following:

PERFORM 000-INITIAL-START
PERFORM 010-INITIAL-START-SUB-000
.
.
.
PERFORM 100-PRIMARY-PROCEDURE
PERFORM 110-SECONDARY PROCEDURE

and so forth . . .

Then I would fill the first procedure with sub procedures:

PERFORM 000-INITIAL-START-SUB-001
PERFORM 000-INITIAL-START-SUB-002

I was able to look busy for days without actually doing any real work; but eventually the outline of the COBOL program would be so "complete" that it became easy to start focusing on doing things like adding, subtracting, and so forth.

Since there were daily quotas in those days for programmers (now called "software engineers" and "developers"), I always had good quota numbers and managers often remarked on what a good worker I was. 🤪

Yet, at least until I started learning how COBOL worked, I mostly was just creating, expanding, and enhancing outlines.

This strategy works nicely when you are focusing on organizing thoughts and idea; and I like to use a mind-mapping application called "SimpleMind Pro", which (a) is available for the Mac and Windows and (b) is affordable.

These are a few of the mind-maps from my ongoing books on "The Art of Digital Music Production" and are useful for visualizing lists and groups of various things that are categorized.

STRATEGY FOR STUDIO ONE TEMPLATES

Since you already have a set of templates and do not want to cause everything to stop working, you can start a new system and once it's perfected, you can start using it.

The overall structure for data in macOS and Windows is based (a) on {folders, subfolders, files} for macOS and (b) on {directories, subdirectories, and files} for Windows.

You can start by creating mind-maps to explore different ways to organize and categorize instruments, voices, and effects, as well as musical genres, styles, and so forth.

When that is working nicely, you can create a corresponding hierarchy of folders, subfolders, and files, where the files will be Studio One templates and might even be ".song" subfolders themselves. This also can include text files with information about what the various Studio One templates do.

Even when you include a virtual festival of world instruments, at a high-level instruments are grouped or categorized by the way they produce sounds, where one system groups instruments this way and is called the Hornbostel-Sachs System {Idiophones, Membranophones, Chordophones, Aerophones, Electrophones}.

(1) Idiophones are instruments that make sound by vibrating themselves, like cymbals and bells

(2) Membranophones are instruments that make sounds via stretched membranes like drums.

(3) Chordophones are instruments that make sounds by vibrating strings like guitars, concert harps, and grand pianos.

(4) Aerophones are instruments that make sounds by vibrating columns of air like pipe organs, flutes, oboes, and voices (singing).

(5) Electrophones are instruments that make sound electronically and via computer software like synthesizers and VSTi virtual instruments.

When doing digital music production using Studio One, everything ultimately is an Electrophone once it is recorded as audio on Audio Tracks.

I also like the strategy of grouping and organizing by VSTi virtual instruments, where a few popular instruments are {SampleTank, Kontakt, Opus, UVI Workstation, Falcon, and so forth}. In this strategic variation, the idea is to create a template with one instance of each of the VSTi virtual instruments you have in your collection and then to enable one when you need it, followed by cloning it to create a new instance.

This is what I do for a basic drumkit, where instead of trying to fit everything onto as few staves as possible--which is vastly cluttered and is a big mess--I put each drum, cymbal, and Latin percussion instrument on its own staff. I like to do headphone mixes where sounds move from place to place; so I usually have two kick drums and three snare drums, each on its own staff. If I need more, then I create more staves, but always one instrument per staff.

For reference, EW ComposerCloud+ (EastWest) and Sonic Pass (UVI) are available as monthly subscriptions and have everything arranged and grouped by various countries, musical genres, styles, and so forth, which makes them an excellent way to get a sense of pretty much everything that can be part of what I call the "New Modern Orchestra" or perhaps the "21st Century Orchestra", where songs can be constructed using subsets of thousands and perhaps millions of tones and textures, especially when you consider every possible sound a synthesizer can make.

You might want to explore Asian, Indian, Persian, Turkish, and Middle Eastern instruments, which in EW ComposerCloud+ are organized in the "Ra" and "Silk" collections, as well as in other related collections.

World Suite 3 (UVI) has similar types of groupings where there are subsets of six instruments in various genres, styles, and tempos; and the subsets can be used as ensembles and actually play themselves or can be used as singleton instruments, which is the way I use them for things like shakers, maracas, cowbells, and so forth.

It's a bit mind-boggling at first, but after a while (a) it starts making sense and (b) you can organize sounds by tone and textures rather than by countries, genres, styles, and so forth.

You can make mind-maps of everything, including different types and categories of harmony.



Hey thanks for sharing! I can see these mind maps as a helpful tool... in a way like scriviner is to word processing. I look forward to taking a closer look.
 
Short answer:


No, none of this should be a problem. The template files (which are essentially song files with different extensions) are only accessed when you start a new song. The new song is basically (simplified, but still...) a copy of the template. You can safely create an "archive" folder within the templates/v5 / v6 / v7 folder and move outdated templates to this folder.


Renaming shouldn't be a problem either. Here is how it works:

View attachment 2515

Each template consists of multiple files. To change just the display title, you can open the [your-template-name].songtemplate file in a text editor and change the Document:Title. This will be the title that appears in the list and by adding a prefix, you can change the order.

I hope that helps.
This is great and exactly what I want to do, but was hesitant to start moving and and possibly renaming templates. Am looking forward to cleaning up that folder. I appreciate the detailed explanation and instructions. Thank you!
 
Notion hasn't been NOTION since NOTION Music was acquired by PreSonus in 2013. The last version update, Notion 6.0, was released in August 2016 and the last sub-point update, Notion 6.8.2, was released in August 2021 - pretty much as Fender took over the company. There's unlikely to be any more updates to the desktop app; the bones of the program have been incorporated into Studio One, and the mobile app has taken on the mantle, though I question how useful that is to most Studio One users. I moved on to Dorico, which gets a lot more love!
 
[...] You also can do this in Studio One; but you need to close the current song to get the startup choices, which I suppose makes a bit of sense and is not super complex. [...]
Why not use the 'Home' button? It gives direct acces to the templates available by default or user..
home.png
 
Short answer:


No, none of this should be a problem. The template files (which are essentially song files with different extensions) are only accessed when you start a new song. The new song is basically (simplified, but still...) a copy of the template. You can safely create an "archive" folder within the templates/v5 / v6 / v7 folder and move outdated templates to this folder.


Renaming shouldn't be a problem either. Here is how it works:

View attachment 2515

Each template consists of multiple files. To change just the display title, you can open the [your-template-name].songtemplate file in a text editor and change the Document:Title. This will be the title that appears in the list and by adding a prefix, you can change the order.

I hope that helps.
Gotta love the short answer! :ROFLMAO:
 
Following @Lukas recommendations I was able to clean up my lengthy list of user templates and drill down to a handful that I routinely use. Thanks man!

This is a nice quality improvement for me!

Saving templates once I finished a project became part of my routine early on and the habit has stuck. My preference is always to start a project with some basic folders/routing/plugins I know I'll use...it really saves time and keeps me in a creative flow if I'm lucky enough to be in one at the time. And because I have explored or worked on variety of genres using Studio One, overtime I've ended up with this ridiculous number of user templates.

Now my user template list is under 10...to include a blank template w/ some basic routing, a few genre or library specific, one for recording, sound design, and a larger "master" orchestral template (most tracks load disabled).

When paired with macros and track presets -- it's a workflow I'm very happy with.
 
Back
Top