VI's in Templates

[DP Fan]

This is going to be hard to explain, but I'll try. Any help would be great.

Basically, if I make a template that includes third party VI's (mainly Kontakt), when I create a file based on that template the outputs to the MIDI tracks are in italics and I have to reassign them with Studio Menu > Remap MIDI Devices. This is a fine work around...but I'd rather not work around.

For instance...

I open a brand new file. I create a Kontakt Inst track. I load 16 samples. I make 16 MIDI tracks with outputs going to Kontakt 3 channels 1-16. Everything works wonderfully. I choose Save As Template and name it "Kontakt Sounds". I close this file.

Then...I go to New > Kontakt Sounds, give the file a name and open it. When it opens, everything else loads fine except for the outputs to the MIDI tracks...which are in italics and don't work. If I go to Remap MIDI Devices, I can reassign them all at once...but does anyone know how I can get it so that I won't have to do that?

I'm running DP6.02 and OSX 10.5.6.

Thanks all...

[balord]

I get this same behavior with SampleTank, Stylus RMX, and Omnisphere. I thought at first it was an issue with SampleTank, or with Ableton Live publishing its Rewire inputs to the Bundles > Instruments window.

I also thought it might have been a corrupt template file, since that file has been brought forward since DP 3. So, after painstakingly rebuilding our template from a brand-new 6.02 file, I narrowed it down to the actual Template function itself. The source file would reopen flawlessly until we saved as a Template and then opened a new file from the template. That new file would have a variety of issues, but most often the bundles were unset or worse the actual bundle inputs would be out of order. MIDI channel assignments would often appear forgotten and have to be remapped. It doesn't matter if you fix things and save it either. Once a file is created thru the New from Template function, it's going to be bad forever.

Similar behaviors to this from these posts, too:
http://www.motunation.com/forum/viewtop ... te#p301501
http://www.motunation.com/forum/viewtop ... te#p303258

Something is happening in the template-making process that is causing corrupt bundles or something. Thoroughly frustrating, but I'm just glad it's not a problem with one of the VI's themselves. We're not always the highest priority platform for these developers.

My workaround is to never ever use the New from Template menu item. My template is an empty project file that I locked in the Finder. The Project folder is locked as well. That way, if you forget to Save As... when you open, DP can't save to the file or folder anyway (it's locked) and prompts you to save it somewhere.

Good enuf for now.

[Frodo]

Yeah-- when this happens, I always go to my saved blank project which I happen to call "template". In fact, I have several custom non-menu "templates" stored in a folder on my HD.

There is something about Leopard that can be described as "forgettable". A number of VIs de-authorize themselves from time to time.

The only other thing I can suggest is to try the same "templates" with Garage Band. Perhaps it's a DP issue. Perhaps it's a 10.5 issue. Not sure. Distinguishing between the two is, without a doubt, a challenge. Didn't have this problem with 10.4.

[mike_o]

was just going to post about this, just switched to 10.5.7 and this is bugging the hell out of me, I'll try the custom template file method for now.

[itsthenoise]

I've just had to re-install a whole new hard drive because my previous [ snow leopard 10.6.3 ] one can't remember it's plugin authorizations.

Does anyone have the following bits of kit attached to their computers?

Euphonix MC Mix
Powercore Firewire
or
Motu 424 soundcard?

Wondering whether these are the offenders?

[AnthonyS]

I get this same behavior with SampleTank, Stylus RMX, and Omnisphere. I thought at first it was an issue with SampleTank, or with Ableton Live publishing its Rewire inputs to the Bundles > Instruments window.

I also thought it might have been a corrupt template file, since that file has been brought forward since DP 3. So, after painstakingly rebuilding our template from a brand-new 6.02 file, I narrowed it down to the actual Template function itself. The source file would reopen flawlessly until we saved as a Template and then opened a new file from the template. That new file would have a variety of issues, but most often the bundles were unset or worse the actual bundle inputs would be out of order. MIDI channel assignments would often appear forgotten and have to be remapped. It doesn't matter if you fix things and save it either. Once a file is created thru the New from Template function, it's going to be bad forever.

Similar behaviors to this from these posts, too:
viewtopic.php?f=1&t=36730&p=301501&hilit=template#p301501
viewtopic.php?f=24&t=37095&p=303258&hilit=template#p303258

Something is happening in the template-making process that is causing corrupt bundles or something. Thoroughly frustrating, but I'm just glad it's not a problem with one of the VI's themselves. We're not always the highest priority platform for these developers.

My workaround is to never ever use the New from Template menu item. My template is an empty project file that I locked in the Finder. The Project folder is locked as well. That way, if you forget to Save As... when you open, DP can't save to the file or folder anyway (it's locked) and prompts you to save it somewhere.

Good enuf for now.

Glad i saw this. I thought I was the only one. It also happens for me with MachFive 2 sometimes, and Ivory. Just a mater of reassigning, but it does take away from the spontaneity a bit.

[FMiguelez]

.

This issue has to be reported to MOTU. I've been experiencing the same thing now.
And it's kind of KILLING me because most of my Clippings are not working as they should, and it's defeating the purpose of Clippings and Templates.

This ought to be a NUMBER ONE priority for MOTU to fix.

[Shooshie]

I guess the reason I haven't noticed this is that my "templates" come from existing files. No, I don't make templates out of them. I find myself working in a new chunk copied from an existing one, creating a new song as inspiration hits me, and then I just "save as" the new song, deleting the old chunks in the process. Thus my projects kind of metamorphose from one to the next, acting as templates for each other but never actually going to the templates menu.

It's an old way of working for me. I used it in the late 1980s and later, but I switched to templates in about 2004, and I've been backsliding of the past year or two into my old way. So, it may be a workaround for some. It feels kinda like home to me.

Shoosh