Problem with Save as New Template

[Killahurts]

I created a somewhat large template (about 30 Virtual Instruments) as a document, then I saved it as a new template. If I try to create a new project from that template, DP crashes every time, just after "reading project" bar finishes.

I can still load the project the template was created from without a problem, and I've tried saving as template multiple times, always the same problem. When it finishes reading the project, it begins to load the virtual instruments, but quickly crashes with a blank (black) Kontakt load window. Probably 3/4 of the VIs are Kontakt instances.

I've tried rearranging the VI tracks order, rearranging track folders, etc. It always gets stuck at the exact same place.

Again, if I go to the project that created the template, which has the exact same saved content, it opens without a hitch every time. I can see how a virtual instrument might be responsible for crashes on startup, but why would it only crash on a new document from a template, and be fine otherwise?

[wvandyck]

No harm in following process (1) outlined in the link below.
https://motu.com/techsupport/technotes/ ... 20Glitches

Once loaded into the empty project, try saving that as your template.
If the template opens, then your previous template was corrupt.

[FMiguelez]

What does Console say it happened when DP crashes?

Check it out. It may give you a hint of what's going on.
By your description, it sounds to me DP is looking for something it doesn't find or it found duplicates and doesn't know what to do with them (a library or file in Mac HD>..../Plugins or User.../plugins. This accounts for 80% of my crashes when I get them. I hate it.

[bayswater]

If one of the VIs is the culprit, you could try loading the project that still works, turning all the VIs off, saving as a template, then starting a new project with the template. If it still crashes, maybe it wasn't the VIs. If it loads OK, you can turn on the VIs one at a time and see which one is the problem.

Either way, it would still be a mystery why the project works, and the template from it doesn't. Something to report to MOTU, and maybe NI.

[Killahurts]

Either way, it would still be a mystery why the project works, and the template from it doesn't. Something to report to MOTU, and maybe NI.

That's the weird part for me. Why would it do that? The only difference is, the new template is creating/writing a new project, while the project it came from is just reading/loading from saved.. but still.

Thanks to everyone for the responses! I'm going to try Bay's idea first, make a new template with all the VIs disabled and turn them on one at a time.

[Gabe S.]

Don't make the session a template. I have always had problems with that feature.

Here's what you do:
-Create a session with all the settings you want and Save it.
-Do a "Get Info" on that session file. (Command-I)
-Click the Stationary Pad option in the Get Info window. The file is now going to act like a template.
-However, you cannot just double-click on the file to launch your template. You have to do one of two things---1. You can either drag the "template" file onto the DP icon in your doc. Or 2. You can drag the file onto your doc and make an alias of it on the doc, and then click the doc alias of that template. Either of these methods will properly open a window and let you create a new session from that file.

If you need to edit your Stationary Pad template, do a Get Info on the file and then unclick Stationary pad and then double-click the file to open it. Do your edits and save it. And then check the Stationary Pad box again.

I have worked this way for many years with DP.

[Killahurts]

Here's what you do:
-Create a session with all the settings you want and Save it.
-Do a "Get Info" on that session file. (Command-I)
-Click the Stationary Pad option in the Get Info window. The file is now going to act like a template.
-However, you cannot just double-click on the file to launch your template. You have to do one of two things---1. You can either drag the "template" file onto the DP icon in your doc. Or 2. You can drag the file onto your doc and make an alias of it on the doc, and then click the doc alias of that template. Either of these methods will properly open a window and let you create a new session from that file.

This absolutely works like a charm, thanks for posting it Gabe!

I tried to make the DP template work by not enabling the VIs until I have the new document up and running, which worked.. except then it wouldn't remember my MIDI device groups, which I need.

I'm convinced this is a bug in DP, and until it gets fixed this is the most elegant solution.. in fact, I like it so much I may continue to work this way permanently, like Gabe.

[Gabe S.]

This absolutely works like a charm, thanks for posting it Gabe!

I tried to make the DP template work by not enabling the VIs until I have the new document up and running, which worked.. except then it wouldn't remember my MIDI device groups, which I need.

I'm convinced this is a bug in DP, and until it gets fixed this is the most elegant solution.. in fact, I like it so much I may continue to work this way permanently, like Gabe.

Great! Yeah you can have everything you want fully setup and enabled this way.

Whatever problem DP has with templates has been there for a very long time. I would not be holding my breath for a fix.

Honestly, there's really no downside to this way of working---at least I haven't found one yet, and I've been doing it this way for a long time. The only minor hiccup is if you double-click the stationary pad file by accident.

-g

[HCMarkus]

I don't even bother with stationary. I just open my "template" file and immediately "Save As" in the desired location. A couple of copies of the template are always handy just in case I get carried away and start a project in the template file itself.