I suppose the first place to look would be a folder in UsersusernameAppDataLocal or Roaming.

Or you can use a file activity monitor app:
https://www.raymond.cc/blog/3-portable-tools-monitor-files-folders-changes/

Where are patterns saved onto the PC when using MODX Connect to get the patterns off the MODX?

Patterns and Songs are initially ‘stored’ on the MODX, not on your computer. They are automatically stored in the internal memory of the MODX. They remain in memory until you either specifically DELETE them, or you initialize all data in your MODX.

Press [UTILITY] > “Contents” > “Data Utility” > your Songs are in the folder labeled “Song” (you can store 128 Songs in the system memory).
Your Patterns are in the folder labeled “Pattern” (you can store 128 Patterns in the system memory).

Hint: It is from these internal system Folders that you can review and manage your Songs and Patterns (Rename, Delete)
Your Songs and Patterns remain in MODX memory even when you load a new User Bank — this is because, any Song and any Pattern can be linked with a Performance that is in ROM (as a Library or as a Preset) not just those currently in the User Bank.
__ when you create data using the MODX sequencer, it is automatically stored in these folders. This is true of the data you LOAD as a .mid file. A copy of it goes to either the Song or Pattern Folder. When you LOAD a .mid file to MODX, you are asked to direct it to either the Song or Pattern folder.

If you wish to copy your Songs or Patterns from the internal MODX storage area to your computer, you can:
__ Use MODX CONNECT to “drag and drop” them directly via USB connection to your computer. You can drop them to your desktop, to a specific folder, or directly into your favorite DAW. Each Song is moved individually because this is how most DAWs deal with .mid files.
Each Pattern is moved Scene-by-Scene (8), because this is how Patterns are created — each Pattern Scene is a separate .mid file, because this is how MODX deals with Scenes.

__ When you are working on a Song or Pattern, you are offered an additional option to “Save as .mid file”. This appears on the main Song screen. When you’re working with Patterns, touch “Edit/Job” > “Overview” to see the option. As you select each Pattern Scene, you are offered to “Save as .mid file”.
This is how you can backup your Songs and Patterns to external storage devices (USB stick). The USB stick can be read by your computer — and the .mid file is universally recognized by all sequencers. You would keep a copy of your Sequences on USB stick so they can travel with you.

Pattern Scenes can be 1-256 measures in Length.
Pattern Scenes can be “appended” — one can be added to the end of another increasing Length - up to a maximum 256 Measures.
Pattern Scenes can be “chained” — placed in a specific play order, then “Converted to Song”

Extra Credit:
Link — Mastering MODX: Using MODX CONNECT to Import Performance Patterns
Link — Tech Talk Live: MONTAGE/MODX Connect

When you are working on a Song or Pattern, you are offered an additional option to “Save as .mid file”. This appears on the main Song screen. When you’re working with Patterns, touch “Edit/Job” > “Overview” to see the option. As you select each Pattern Scene, you are offered to “Save as .mid file”.

This doesn't strike you as being extremely laborious when the question is about offloading every pattern?

This is how you can backup your Songs and Patterns to external storage devices (USB stick). The USB stick can be read by your computer — and the .mid file is universally recognized by all sequencers. You would keep a copy of your Sequences on USB stick so they can travel with you.

It seems there is no way to store the linked Performance with this. How do you note which patterns work with which performances, so when a Pattern is reloaded from the USB it's no trouble to hook it back up?

Pattern Scenes can be “appended” — one can be added to the end of another increasing Length - up to a maximum 256 Measures.

How is this done?
-------------

It seems very odd that it's not possible to mass offload all Patterns at once, along with at least a named reference to the Performances they are "linked" with/to.

I know about the full Backup method of doing a total backup including patterns. That's not helpful, either, as it seems impossible to extract Patterns from this file.

First, you’re welcome.

This doesn't strike you as being extremely laborious when the question is about offloading every pattern?

No. it doesn’t. It is how you create them, it is how you Save them. They Store automatically to internal memory.

It seems there is no way to store the linked Performance with this. How do you note which patterns work with which performances, so when a Pattern is reloaded from the USB it's no trouble to hook it back up?

Tap the box that says “Store Pattern & Perf Settings” this creates a link between the Performance location (Performance folder) and the Pattern (Pattern folder).
When you recall the Pattern by number 001-128, it will automatically recall the linked Performance.
See pages 26-27 for details on the Pattern main screen features/functions.

STORE = internal memory
SAVE = external storage device

How is this done?

See page 39 of the Supplementary Manual for info on Appending Pattern Scene data.

If you’ve only been making 4 and 8 measure Pattern Phrases, it might seem like a lot of work… but those who know how to Append Scenes wind up with Scenes worth (worthy of) the effort to Save as a .mid file. Patterns are designed as an assembly tool (now this does not mean you have to use it like it was designed, but it does mean you need to appreciate the workflow it suggests)… which is you use the Pattern Scene as a construction tool to build the musical sections (Scene by Scene)… Scenes can be Appended or Split, moved to and from the linear Song structure. Then “chained” to make a linear Song.

With this as the workflow, there really is no reason to save each Pattern Scene to a separate .mid file. But since there are just 8 of them and since they are immediately and automatically stored in the internal Pattern folder. The time to export them to a computer would be to a DAW. And even then, the Chain and Convert to Song functions make complete sense as the easiest/best method to move the data to a computer.

MONTAGE Terminology
MIDI SONG = linear structure that include MIDI event data combined with a synth Performance.
PATTERN = loop record sequencer, made up of 8 Scenes (musical sections) that includes MIDI event data combined with a synth Performance.
.MID = a universal file format that includes only the MIDI event data

Work with it awhile, you’ll figure it out… it’s not that difficult.

are you deliberately avoiding the question?

How does an offloaded (saved to external storage) Pattern, maintain a link to the Performance.

As to it not being laborious to offload 128 * 8 Pattern Scenes... Can I send you my backup file, you do the offloading to a USB stick and send back all the unique patterns?

It's incredibly laborious, to me.

are you deliberately avoiding the question?

I answered your question.

How does an offloaded (saved to external storage) Pattern, maintain a link to the Performance.

It doesn’t — a stored Pattern is linked with a Performance — this all takes place inside the MONTAGE.
Again:
STORE = internal memory
SAVE = external memory

Work with it awhile, you’ll figure it out… it’s not that difficult.

are you deliberately avoiding the question?

I answered your question.

How does an offloaded (saved to external storage) Pattern, maintain a link to the Performance.

It doesn’t — a stored Pattern is linked with a Performance — this all takes place inside the MONTAGE.
Again:
STORE = internal memory
SAVE = external memory

Work with it awhile, you’ll figure it out… it’s not that difficult.

So once a pattern is offloaded to an external storage device, the only way to find what performance it was once linked to is to write it down?

How do you note which patterns work with which performances, so when a Pattern is reloaded from the USB it's no trouble to hook it back up?

You could rename the song/pattern to something that would make this associative cue for the link relationship. Perhaps even the exact same name. Following such a convention would make it clear which Performance was linked when saving to a USB stick.

Internally, the link is maintained - so you would also know by loading the internal pattern or song (that has been linked) and the Performance will be pulled in with it. Therefore, even if you did not save a filename that hints towards the link - you can still unravel this by loading the internal song or pattern that matches your save file's name. As long as you have not, renamed either of the files (save file or internal song/pattern).

How do you note which patterns work with which performances, so when a Pattern is reloaded from the USB it's no trouble to hook it back up?

You could rename the song/pattern to something that would make this associative cue for the link relationship. Perhaps even the exact same name. Following such a convention would make it clear which Performance was linked when saving to a USB stick.

Internally, the link is maintained - so you would also know by loading the internal pattern or song (that has been linked) and the Performance will be pulled in with it. Therefore, even if you did not save a filename that hints towards the link - you can still unravel this by loading the internal song or pattern that matches your save file's name. As long as you have not, renamed either of the files (save file or internal song/pattern).

I'm not sure why you and BadMister are focused on the internal Patterns.

They need to be Saved out because the Pattern Sequencer is full. Daughter is highly productive little experimenter with the Pattern Sequencer. I'm trying to free it up for her, by getting things out of it. All of it would be nice, so she can crack on without worrying about running out of space for a while.

She can't be the only one that's hitting this limitation of the Pattern Sequencer.

She does not like working with DAWs, not even with an MPC. She's become a bit of a fan of the Pattern Sequencer, despite my reservations about it.

Do you happen to know if there's anywhere I can extract the Patterns from a full backup? That might be the easiest way to solve this problem... do a full backup, to "export" every pattern, extract them, put them somewhere she can grab one when she wants, and reload it onto the MOD - only when she wants to work on that one again...

etc.

Do you happen to know if there's anywhere I can extract the Patterns from a full backup? That might be the easiest way to solve this problem... do a full backup, to "export" every pattern, extract them, put them somewhere she can grab one when she wants, and reload it onto the MOD - only when she wants to work on that one again...

Looks like an obvious feature for a future version of John Melas' tools...
Also, the guy doing these tools: http://www.xfactory-librarians.co.uk/products.html
just announced he's close to doing something similar for the Montage: https://www.yamahamusicians.com/forum/viewtopic.php?f=129&t=17973&p=101926#p101926

Cheers, @Dragos,

Brings to mind the idea that a diff check on a backup done on an earlier firmware (before Pattern Sequencer) and after might reveal where and how the patterns are stored.

Now to see if it's possible to rollback firmwares...

A good work ethic to teach your daughter is, if it is worth the time to create, it worth the time to save it. If you do each one when you create it you don’t wind up in a situation where you are waiting for some third party to hack a 128 x 8 Scene solution for you.

A good work ethic to teach your daughter is, if it is worth the time to create, it worth the time to save it. If you do each one when you create it you don’t wind up in a situation where you are waiting for some third party to hack a 128 x 8 Scene solution for you.

This kind of crap is beneath you.

You're better than this, when we're talking about a sketching tool and a child exploring creativity, iterating at a rapid rate, riffing on ideas through the looping facilities of the Pattern Sequencer, etc.

Next time, Yamaha should take the time to finish features to a polish becoming of a brand with their supposed pedigree, or open up their software for others to add more usability and general accomodation of empowering workflows.

I'm not sure why you and BadMister are focused on the internal Patterns.

When you save a song or pattern to a USB stick - it doesn't carry with it the information you're requesting. Part of the questions asked along the way was how to know, once you you've saved a pattern or song, how to know how it was linked?

I'm not defending the system implementation - but you've got to work with the system until something better comes along. That was my approach in the answer. When the existing approach Yamaha has chosen doesn't fit your needs - or there's an improvement that can help then I'm all for suggesting ways to improve the system while identifying why the current system is deficient or otherwise not optimal. I mean, I do this all the time. I have a difference with how something was implemented all the time and voice that. I'm good with that. I'm also not affiliated with Yamaha so I have no investment in defending the design. I think it's good to have feedback from users because we all use the equipment differently and it's interesting to hear all the different approaches and how aspects of the keyboard work against some goals.

... so, without the saved pattern self-expressing what it was linked to I gave two possibilities of how to manage this. That you could name the pattern after the linked Performance and that would manually hint at the linkage. Or you could save it as any old name and as long as the name still matches at some date in the future (you haven't renamed the internal pattern/song, you haven't overwritten memory completely with some other backup, or otherwise broken an association with what is now your external USB's save name vs the inside) - then you could look at your USB stick name and recall that song/performance in order to "dig up" the association.

Is this ideal? No. Is it great? Maybe not. I'm not painting it under those terms. I'm just saying those are the ways I'm aware of to deal with this question given the tools provided today. If that isn't going to work for you then I have no judgement about that. That's your call to make. I'm not saying to live with the system the way it is forever without complaints. Once you know what's available - you can make requests to enhance the system to better fit your needs. Best done on ideascale because the R&D group has visibility to the ideascale site which increases overall the visibility of your enhancement request to engineering side that would make coding changes should Yamaha elect to provide the changes.