Hello Everyone,
Is there a way if I use a project template or something that I can always feel safe that when I insert a new softsynth that "enable midi out" is not enabled by default (if the softsynth supports it)?

It is really screwing me up.
 
Thank You,
alewgro

Yes, both track and project templates save the state of "Enable MIDI Output" for plug-ins, so they could be used to override the default value.

I understand for track templates, but how do you do it for "Project Templates"?

Load the synths into a project, then use the "Save As" function. In the "Save As" dialog set "Save as type" to Template and "Go to Folder" as "Templates (CWT, TPL)". The Normal.cwt is the default template. I always rename the original Normal.cwt and modify Normal.cwt for my needs. Templates can have any name you wish though. FWIW, if this was an issue for me, I would use track templates.

New project with project template. Change the setting. Save the project template overwriting the original (or create new project template).

This doesn't work.  I've tried making new project templates and going into the synth options.  It is DISABLED by default.   Problem is, when you add a softsynth it enables it.   Seems like no matter what I do, I cant get this thing diasabled :(

The state of the "Enable MIDI Output" would only be saved for the plug-in instances saved in the template, not for new instances of the plug-ins. This is why I would use track templates to add the synths rather than load them up in a project template.
 
The "Enable MIDI Output" setting is based on the value of generateEvents in the VST Inventory entry for each plug-in. With X3 the value defaults on if generateEvents is 1, prior versions would only enable the check box. The generateEvents value is set during the plug-in scanning process. Other than editing the registry and changing the generateEvents values to 0 for the plug-ins that have the value set to 1, I know of no way to alter the default "Enable MIDI Output" behavior when adding new instances of plug-ins. Of course, anytime the VST Inventory is reset&rescanned or a plug-in is updated triggering rescanning for the plug-in, the generateEvents would need to be edited again.

oh that is terrible... I dont want preloaded synths in my templates.
 
I do see them in the registry though.  I will probably change them in there :)    Thanks for the reply scook!!!!
 
alewgro
 
 
 

The registry hack does work but I would recommend using track templates for this issue. One track template per synth, configured as needed. Then build projects from the track templates. I believe it is fairly common to have synths in track templates. SONAR comes with quite a few predefined track templates containing synths.

True!  I can do that!  Thank you!!