Hi,
I'm just wondering what the point of the settings.xml file is, if not all the settings are stored in it?
Eg. As far as I can tell, something as basic and fundamental as format settings for projects (ie. the parameters in the format tab in MC), are still stored in the *.avp binary project file, and not in the projects settings xml file (at least in my version:2018.12.3.51505). Is there a good reason why settings are stored in multiple locations in this way?
I understand that not all settings can be changed effectively without the possibility for errors ie. changing timebase - but still no real reason to reserve them or store these seperately in the project file?
Let's say I want to change a bunch of interlaced projects into progressive ones, or even create a bunch of projects at once, change the raster or framerate of some - can't do it by editing just the settings xml, as all these settings are hard coded into the projects .avp binary.
This means that if I want to automate this kind of thing, then I have to overwrite or bundle project files and xml's, one for each format type / configuration of settings I need. It gets really complicated fast.
Also, let's say I'm working with multiple editors. When I create a project, the basic settings such as raster and framerate are written into the avp file, and a bunch of defaults are written into the xml. When I enter the project, MC creates a user/machine folder and copies the settings and project file from the root, into the machine folder. If I edit any setting with a 'Project' status in the settings tab, then this setting is only unique for the current machine, and not global for the actual project - which you might expect might happen if you edit a 'project' setting. Surely this is a unique 'Machine Project' setting? and the User, Site and Project distinctions now become confusing and complex too.
This means then, that if I truly want these settings to be simple global settings for the project, then I have to use windows to copy the files from my machine folder into the root of the project folder and overwrite the settings and project files there.
We call this the 'Cowboy Trick' - because it is a trick for a cowboy ie. a non-prof, shabby person, doing a half hearted and bad job 
I have not yet found a tick box or setting in MC, that enables me to 'Apply project settings globally for all users' - is this at all possible?
If not, a truly external project settings xml that all users can inherit from would be a giant step, and a huge help for people like me who want to create and change lots of projects at a time for multiple users. It would be a much cleaner and tidier, better way to keep global project settings in one place.
I'm sure there are more pros than cons for most typical users if MC worked this way.
