Change default settings for EVERY new project?

Herr_Rausch · 2015-05-08T17:35:59.000Z

Hi,

I am wondering if it is possible to change the default settings in such a manner, that every new project you create has your preferred settings.

For example by default all the tracks are static machines and the scale mode is set to normal. But I want all machines to be Flex machines and the 8th to be the Master track, also the scale mode should be set to “per track” every time.

As a workaround I made a Template Set with all my prefered settings and whenever I want to start a new project, I first load that Template Project and then save to new. But thats pretty cumbersome actually.

Does anybody have an idea? It would be such an improvement of workflow!

Thanks in advance guys.

PeterHanes · 2015-05-08T17:44:07.000Z

[quote=““Herr Rausch””]
…

As a workaround I made a Template Set with all my prefered settings and whenever I want to start a new project, I first load that Template Project and then save to new.

…
[/quote]

That’s the best way to do it.

Herr_Rausch · 2015-05-08T17:57:16.000Z

Come on there must be another solution, its such a pain in the ass to do that every time

Zymos · 2015-05-08T18:03:50.000Z

??? The idea of a template is that you just do it ONE time…

Rusty · 2015-05-08T21:53:53.000Z

I’m afraid those settings are stored at the code level in the Octatrack OS, and the ability to modify them are not exposed via the OS.

From a development point of view, you would not want users to have the ability to change these, because then you have various people having various settings… that and these settings were hardcoded 5 plus years ago during the OT’s development. when all there was were Static machines, there was no Master track, and there was no flexible scales; i.e. the base values only.

I know a few workarounds… one is the one you mentioned, and well, there are others.

Herr_Rausch · 2015-05-08T22:57:12.000Z

@Zymos: I mean the act of first loading the template project and then saving it to new. the problem with that is that you save every project right in the beginning (with a rather random name, because you dont know what its goin to sound like later). but most projects in the end are not worth saving and you end up having lots of randomly named projects you dont need. and I like to keep it tidy

@Rusty: would you be so noble to share your other workarounds with me?

PeterHanes · 2015-05-09T00:01:57.000Z

[quote=““Herr Rausch””]
…

but most projects in the end are not worth saving and you end up having lots of randomly named projects you dont need. and I like to keep it tidy

…
[/quote]

You could delete them.

Rusty · 2015-05-09T04:33:29.000Z

[quote=““Herr Rausch””]
@Rusty: would you be so noble to share your other workarounds with me?
[/quote]

I think it is quite obvious, no?

Herr_Rausch · 2015-05-09T08:33:15.000Z

@PeterHanes: well thats what i do, still annoying

@Rusty: sorry I dont get it

rozzbud · 2015-05-09T11:40:53.000Z

i think rusty talks about his sofware

To expand upon the thread, what are you templates of choice/ideas? Preferably how would you optimize 16 banks?

ex:

1 bank for preset fills

-1 bank with full 6 tracks x 32 trigs of one shots ready to be copied to 7 and recorded on 8.

1 banks of 4 parts of 2 preset fx chains
1 bank for “quantized” (4 parts= 4 scales) polyphony. 5xsame flex sample+ bussing to an fx track via cue on 6+neighbour on 7+recorder on 8.

-1 bank dedicated to midi feedback

Herr_Rausch · 2015-05-09T15:21:40.000Z

I just own it since like a month now, I havent even gotten into working with more then one bank