Template Sets workflow?

[braduro]

Greetings!
I could have sworn that templates were now available on push3s.
I see the "save set as default" option.
And I see the templates folder in my Push user library (which I think is actually a dubious place to find it.)
And I can load a project which I've saved from within that user library folder, Templates.

But it's not a template. It's not opening a copy of that set.

Now that I've performed within it and pressed "Save" it's not assigning a new name and putting it with other projects. It's just saving what was the template and now putting music that I've made in it. It's a project, not a template.

I can save a new self contained duplicate of the project by pressing Duplicate+Save BEFORE I start working on this project. But that will just carry over EVERY sample, every track, every bit of content from within the original folder, which would cause bloat both in terms of storage AND time.
AND for every dial I turn or sequence I make, the "default" that I thought I was referring to would then be marred with my music.

What am I missing here, do you know?
Cheers to you

[braduro]

Found it under release notes:

Save Default Sets or Templates: In the Sets menu, press Current Set using the upper display buttons to show a new list of options similar to what you would find in the File menu on a computer. This menu includes new actions to save your current Set as the default Set or as a template Set.

So one takeaway is that moving projects to the Templates folder via file transfer is not the same result. So I'll report where the current set is then saved and where to transfer your template candidates if you so choose to make one in Live.

[braduro]

you can leave the project in the Templates folder, but when it opens a set, you will go to Current Set under files and save it as a Template, as indicated. However, the template will be saved untitled in the same Templates folder in the User Library. You can then go in and give it a name, keeping "template" in the name is something I'd recommend, along with the fact that it will distinguish it from the session that had been left in place after the transfer, if you went about it as I have done.

What to make of this? If your Template has lots of samples, I'd recommend foregoing this entirely and just using the Save As feature of the project in order to save a new set in place, within the same folder. This will save memory and assure that anything you make will already be self contained. Furthermore, saving it will take a fraction of the time it would if you were to create new projects each time from a large template project.

So after all is said and done, SHIFT+SAVE will save a new version of a regular project, and I think that's a better practice than getting Templates to work with big files, IMHO
You just have to remember to create this key combination as soon as you open the original project.
And on the day that you forget, no biggie. You then have however many new drafts of the project with actual worked material. Transfer them over, delete the copy from the Push, and restore a fresh default project from your computer.