robert_e_bone
Would it work for you to create a number of Track Templates - one for each soft synth you regularly use, where the template contained an instance of that synth already inserted, WITH the check box for Enable MIDI Output cleared, and audio track(s) inserted and routed to pick up the output from that synth instance (either 1 stereo track or a left and right audio track), as well as a MIDI track already set to send data to that synth instance?
 
You could even get more granular and set up such a track template for each triggering keyboard/controller you use, with the differences noted in the template naming.  That would also take care of panning, and assignment of input device, as well as the audio and midi track insertions and associations/assignments for those tracks, not to mention always having that Enable MIDI Output cleared every time, through the template.
 
This would seem like other than some minor but simple work to create track templates per the above characteristics, it would for the long haul save you LOADS of keystrokes to do all of the above manually.
 
Just a thought,
 
Bob Bone

SilverBlueMedallion

SquireBum

SilverBlueMedallion
Now, why have a check mark in the "Insert Synth Properties" Dialog box that does nothing?

Because fixing "critical" defects (crashes and bugs without workarounds) and providing enhancements provides a better return for a development team's time investment.  Every development team is under time and money pressures and that is a fact of life.
 
-- Ron

 
Sure, just looking for Anderton or other naysayers to tell me this isn't a bug or poor implementation, to have a check mark that does nothing.
 
But I will add this... I will still stand by this being a bug, here is why.

ANY MOUSE CLICK CAN BE AUTOMATED BY SOFTWARE!

(sorry not, yelling, just showing the point)
 
so... if you have to be asked every time to uncheck "Enable MIDI Output", what the logic SHOULD be and easily CAN be... instead of having a checkbox that does NOTHING, you can build a simple line of code that says... "If 'Enable MIDI Output' is unchecked in dialog prompt, disable it before inserting any softsynth' - this can be inserted after the Enable MIDI Output flag by the VST is being sent to the host!

This way, the "Enable MIDI Output" checkmark in the default dialog box will follow the logic that all the other checkmarks do, such as "Simple Instrument Track" or "Track Folder".  They don't need to be asked every time to work, they just follow the logic.  So should everything in that window if the product is interested in keeping logic consistent within its modules.

If a user never wants MIDI output enabled, they should be able to program it in with a simple line of code that follows this logic:

"If Enable MIDI Output is unchecked in the default dialog box, -> send a disable flag after VST sends an Enable MIDI output flag".

Hell, this logic already exists with the other checkmarks int he dialog box (track folder, simple instrument track, all stereo outputs, etc...)