How does Save As Template work?

[MikePifer]

I might not be using the new Save As Template feature correctly and I want to confirm. If I create a project with the settings and routing I want to keep as a template and then choose Save As Template, it shows up in the overall project list. When I load that template for a new session and choose to save, it is overwriting the template, correct? If I had made any recordings, would those also be saved in the new template? What I have been doing instead of saving over the templates, is to just choose Save As Template again and make a new template that is actually just that project, not what I would want to be a template. In that case, do the recorded audio files save to the template?

I think maybe my confusion is that the function seems to operate as a Save As rather than how I am used to templates operating, and I'm not clear on what happens to the audio files and when/how I need to be saving across projects and templates.

Hard to explain maybe, but I'd love a quick breakdown of how this typically works.

Thanks!

[RollrightKnights]

following thread

[RC Prime]

Yes, it basically saves as a new project, minus audio files, and switches to the new project. Which is not really very template-like.

I'd like to see an actual template implementation where the templates occupy their own namespace/directory and it saves a template there without switching projects. Then, whenever creating a new project, you have a "new from template" option, or just a select menu that always appears, and you could select from a default or one of your templates.

On the other hand it's not that it really breaks my workflow in any way, it would just be a little bit clearer and more to the point.

[sirshannon]

Hard to explain maybe, but I'd love a quick breakdown of how this typically works.

That’s the great thing about not having documentation. You can’t know if it works if you don’t know how it’s supposed to work / Can’t say it is broken if you can’t say how it is supposed to work.

[Steve]

Save As... (in most software) duplicates the entire document/project/etc so you can rename without losing content. Save As Template goes a step further by also removing all of the recorded audio files associated with the original. So when you Save As Template... you are performing a Save As... operation, plus removing the previous files. The great thing bout Save As Template... is that you don't have to accumulate template files. You can create them as needed.

[Steve]

As mentioned in another thread - the updated manual is coming. Thanks for your patience.

[geogeo]

When you're loading a template, you can't save it without owerwriting the template. Hence the utility of "save as".
Or it could work if when loading a template, the bluebox would prompt you to give the project a new name and leave the template intact for future uses.

[MikePifer]

Thanks Steve, I'm looking forward to the documentation for this. This explains it a bit and helpful to know my audio files won't save.
Still not totally sure how to use this though. If I create a template that has all of my settings as I want them, and record something, I can't save the recordings unless I choose "save" which would then overwrite my template? I can see how this could work if you don't record anything, by just continuing to Save As Template so you have a number of different track configuration templates, but ideally I would be able to save my audio files across templates, or if this just worked as a regular "Save As" creating a new project.

I would love to hear how people are using this when recording, or Steve if you have a recommended workflow.

Thanks!

[virtualpt]

Yes, I think it needs a normal Save As in addition to Save As Template. I end up with lots of different ideas in one project & then sort them out on my Macbook!

[Steve]

We hear the request for Save As... The issue with Save As... is that it duplicates EVERYTHING. Bluebox projects can be huge. Save As template is a great option as it only recreates the project with settings, but leaves the audio out of the new project. Given that you can create several takes for each track, plus overdubs, projects can get unruly.

When you start a new project and you want to "clone" another project, simply open that project and select File > Save As Template... this will create your new 'working' project that you use directly. When you save, it will save. When you want to branch to a new project use Save As Template... again.

Save As Template... does not create a template file that will be cloned. It creates the clone.

We also understand that we need to address this aspect of the recording process, overall. As we add new features, there will be things we have to address for the good of the device and our community. We are not finished with the bluebox.

[Steve]

Make sure to +1 this on the wish list thread as we look there when considering the next steps.

[MikePifer]

Thanks Steve !
I'll keep an eye out for future adjustments to the saving and template workflow. I also bumped a similar thread on the wishlist.

Thanks for the work on this, loving my Black and Blue Boxes!

[jayneural]

+1 for the additional save-as

[rev-eng]

+1. Every time I think I get the Save As Template system I end up scratching my head again and heading back here!

[mschurenko]

Can it just be renamed to something else? How about something like "Create Empty Project From"? IMO the way it works is not like a template system, which is fine. It's just the usage of the term "template" that keeps tripping me up. I keep expecting to be creating an actual template form the project that I then would use to instantiate other projects from.

[jnnnik]

I have used "Save As Template" extensively over the past few weeks and absolutely love that it's a thing! Would also agree tho that the naming can be a bit confusing and would suggest calling it something like "Save As Empty" instead