@set Thanks. I'll admit I never heard of Vegas Pro Edit or Vegas Edit, and after the recent Magix upset, I was afraid it was another bait & switch. No knowing that, I can try to expand on my question... Since I'm a new Vegas Pro 18+19 customer, why am I getting a download of Vegas Edit when what I want is Vegas Pro? Does Vegas Edit include Vegas Pro?

@vkmast, thank you and @set my apologies for missing your obvious answer!
"BLUSH"!
 

For those of you thinking or planning to move from VMS17 Platinum to Pro 18 or Pro 19, which I did, I asked the question if all 3 will co-reside and was assured they would at least in two topics. We'll in my first brief use of Pro 18 and Pro 19, I see that they both picked up my VMS17P MAGIX AVC/AAC MP4 custom Render Templates. So (a) What if I delete or modify templates, will that affect the other two editors? and (b) What else might they affect/clobber? So I'm not sure they are isolated from one another.  

@robbif2 I've no experience with Vegas Pro but with Movie Studio versions the only item I have found that they share is custom render templates. These are in your User\AppData\Roaming\Vegas\Render Templates. This folder also contains your Favorites settings. That's the templates you have "starred" as favorites. If whilst using VMS16 I modify a render template then when I open VMS17 the template appears with the modification.

I don't know how it works with Pro versions and between Pro and VMS. But from your experience it appears they share.

So to answer your questions:

(a) Yes it will affect them
(b) To my knowledge there is nothing else that is shared that could affect/clobber but it would be helpful if this could be clarified. @VEGASDerek

@robbif2 I've also just remembered that with VMS any OFX custom presets you create are available to all versions of VMS. They are stored in your Users\User Name\Documents\OFX Presets folder.

Besides the two items Eric has mentioned, I am not aware of anything else that should "conflict" between the two products. I have Movie Studio (both Platinum and Basic) 13 through 17 currently installed on my system along with VEGAS 13 through 19 installed...and they all live happily together.

@EricLNZ So I assume that does mean any one of the editors could modify or delete any of the presets the other ones use. I wonder if I could create unique Presets folders for each editor and point to them in a Preference.
I suppose I could create 1 folder for each editor with temporary names and a DOS batch file that copies or renames the folder to OFX Presets for the particular editor about to start.

@robbif2 I'm puzzled as to why you need different versions of a preset for different VMS versions. But anyway I would adopt an easier method to your suggestion.

When you create a preset include in its name the version it is for. For example XXXXX(16) and XXXXX(17). With each VMS version both presets will appear and you simply select the one you wish to use which is applicable to the version you have open.

@EricLNZ First, thinking worst case, what if I deleted a post while in Pro, and went back to VMS to find it gone?

I know, I know, it's still me using both!

Second, good (now obvious) suggestion for naming presents. I already create a certain Bump Map preset tailored for each band I record, and name each one after the band.

Also, I'm glad my data backup script includes those presets.

EDIT: DoctorZen pointed out that also, "Render templates are shared in the Windows Users "Roaming" folder".