Tests seem to show that not all user files overwrite the quick setup templates. I gave a template a new name and then created a user file. Loading the Example.X7U user file does NOT overwrite the quick setup templates. Either that user file doesn't have any quick setup data or it has the data but it isn't used to overwrite the existing templates when the user file is loaded.

Background:

A recent thread was discussing a question about using the 'Arp Record to DAW' quick setup template - https://yamahasynth.com/community/montage-series-synthesizers/external-midi-note-from-daw-doesnt-trigger-arpeggio-thru-midi-arpeggio-record-to-daw/#post-126488

I checked my M8X (the question was for classic Montage/Modx) and found that it doesn't even have that template. I discovered that the M8X doesn't even have the 'Arp MIDI Out' parameter that the Montage/Modx have and that is saved as part of the template.

P.169 of the Montage reference shows the 'Arp MIDI Out' parameter and p.167 shows that the 'Arp Record To DAW' template persists that setting.

The M doesn't have the parameter or a template with that name. And although the M has an 'Arp Bypass' parameter (as do the classic Montage and Modx) that parameter not only affects the entire instrument and not just MIDI recording.

Tests: 

My tests showed that the 'Arp Bypass' parameter isn't persisted with the quick setup templates anyway so I haven't found a way to create a template that performs the same function as the 'Arp Record to DAW' template in previous models.

The docs for all three instruments (Montage M, montage classic, Mod) indicate that Quick Setup data is stored as part of User Files. See p.177 of the Montage ref.

But I discovered as a side effect of my 'template persistance' tests that loading a user file doesn't always seem to overwrite the current quick setup template data.

1. factory reset

2. modified the 'With Plugin Host App' template #3 to change the name to 'atest'

3. exited the utility area to save the edit (some changes to utility screens are lost if you don't exit the utility area before saving a performance)

4. saved the performance with a new name

5. shutdown and power up

6. template #3 still had the name 'atest'

7. loaded 'EXAMPLES.X7U' file from Bad Mister's mastering montage super knob article - https://yamahasynth.com/learn/montage-series-synthesizers/mastering-montage-1-super-knob/

8. template #3 still had the name 'atest'

9. loaded 'M8X_USER1.Y2U' file - note the file extension is different for the M models as they can be split into two pieces.

10. template #3 name is now 'With Plugin Host App'

My hypothesis is that loading user files from previous instruments isn't loading the Quick Setup template info from them. I'd be surprised if tests on a classic Montage or Modx manifest the problem but it is possible.

Restoring the default template settings requires you to 'Initialize All Settings' which isn't restricted to just the template settings.

Here's the problem: if you load a user file and it loads its own stored version of templates how are you supposed to know if the load changed any template-related data without manually checking all of the things it might have changed.

I would note that there doesn't appear to be a complete list of EXACTLY which parameters are persisted as part of a quick setup template.

Although the template info is persisted in user files once loaded it is GLOBAL to the instrument and is in effect for any preset, library or user performance or object that is used.

Summary:

If you are recording to a DAW on the M models be aware of the missing 'Arp MIDI Out' parameter' and the issue with loading previous user files (including 3rd party) that may have had modified quick setup template data in them.