Hi Alex,
Welcome to YamahaSynth!

When i stop the mid file, the patch changes to another thing completely different. Is there any way to correct this?

This is because your data is instructing the instrument to make that change. There are several things that can cause this reaction.

1) a GM RESET command... this would cause the receiving device to reset to GM start conditions. “Concert Grand Piano“ on all Parts except Part 10 which would switch to “Stereo GM Kit“

2) Event Chase... this is a setting that causes the receiving device to reset to the conditions as indicated at the very start of the Track data. For example, if there is a Volume, Pan, or other message embedded in the Track data, the act of stopping play and returning to the top cause all the initial events to be sent. If you fast forward to a measure, ‘Event Chase’ will scan the Track and update the tone engine to the most recently sent Program Change, Control Change, or Parameter Change message.

I can see from your screenshot, each Track has a setup measure at 001... undoubtedly, when you return to measure 001, that data is being read and transmitted automatically to your MODX.

If you did not place this information there you should delete it. It is pretty much a guarantee that the MODX is responding to commands inserted in Measure 1 of your Cubase sequence.

Even though you have used the XML file to select your instruments, it is overridden by the commands embedded in the Track.

Recommended: if you don’t want the embedded data to change your receiving MODX, you should Delete measure 1. From what I can see in the screenshot, no music data starts until measure 2. Use the Select and the Scissor tool to make a cut separating measure 1 from the rest of the data... and Delete it.

EXTRA CREDIT:
You can have the MODX memorize any and all things that would in that Setup measure, so feel free to eliminate it. You don’t even need the XML file to select sounds, you can do that on the front panel of the MODX...using “Part Category Search” — then you can have the Cubase Project automatically restore all MODX settings.

Make sure you install MODX CONNECT. When launched inside of Cubase AI, it will automatically remember every selection and setting you make for this Project. It simply runs in the background (Auto Sync On)... when you close the Project, it will capture all your settings... and when next you open the Project, it will automatically restore every MODX selection and setting.

It is quite unnecessary to use the old method of searching for sounds via the XML list.

Bad Mister, thank you very much for your reply! =D

I've found a "solution" by switch from Cubase AI to Cakewalk. I don't know if the Cubase version that cames with MODX has the "MIDI Event List" function available, because i didn't find it. Hm, just to confirm: it is possible to edit this events directly from MODX interface, as well add notes and save later the modified MIDI file?

About the XML file, I prefer select the instrument directly from DAW software because it's more fast and i can test the instruments that he have to offer at real time while i'm listening a song. Doing that from the MODX interface requires that i stop the music, changes then play again.

To help the people that is new with the MODX as well and likes the Cakewalk - The INS file to map the instruments can be found on the site https://www.moessieurs.com/ or direct link - https://www.moessieurs.com/download/45/modx_os_2_ins.zip

Alex, you are free to use whatever DAW you are comfortable with.

About the XML file, I prefer select the instrument directly from DAW software because it's more fast and i can test the instruments that he have to offer at real time while i'm listening a song. Doing that from the MODX interface requires that i stop the music, changes then play again

Not at all true. If/when you want to learn how to select your sound without stopping the DAW, we’ll be here to help you (but in the meantime, just because you don’t know how to use a particular workflow don’t assume things about it... Particularly when they are not remotely factual. It’s only fair). You have to allow that there just might be a different way to work that has distinct advantages.

Glad you found a workflow that you are comfortable with.

Bad Mister, thank you very much for your fast reply.

I said that changing the instrument requires to me that i stop the music, because this is the message that appears to me. But i forgot to say that this happens when i load a MIDI file from USB port, directly to MODX without using a DAW. Sorry! I don't know if is there a way to do the changes directly from the MODX interface when loading a MIDI file from the USB port and when we are playing a song. If exists a way, i'll be glad to hear how to do it.

For example, i'm playing a MIDI file imported to MODX from a USB drive.

When i try to change the instrument, the MODX show this message and ask me to stop the sequencer.

Are you using Cakewalk or not?

But i forgot to say...

Well, I forgot to answer the question you did not ask ... haha!
Have you abandoned using Cakewalk already? The reason XML files are outdated is because they are only as good as the most recent list... and they stifle the concept of editing/tweaking each sound for this project - because you wind up accepting the programming, as is. Also when new Performance data is added to the MODX, your XML list is immediately obsolete and must be corrected.

With XML lists you are locked into recalling fixed sounds. The workflow that I’m suggesting is this __ for each DAW session, I edit the Parts (instruments) I am going to use. I do so because rather than accept the factory or previously stored programming, as is (like when using XML listing) I find that I wind up editing/tweaking each instrument to fit the project I am working on, now. Whether it is changing an Insertion Effect, or customizing a Drum Kit by changing the Crash cymbal, or tightening (tuning) the snare drum... or something as simple as changing how it is EQ’d (you are given 5 bands of EQ per Part ...and I use them!)

The XML list you wind up accepting the previously stored setting selections... (as if it was a sophisticated GM module). Hope the EQ works for the composition you are working on.

Try to envision working in your DAW, playing back a bass line; while it plays from Cakewalk... rather than selecting from a fixed listing of instruments, I can use the front panel’s “Part Category Search” to find and audition basses by type: Acoustic, Electric, Synth, etc. I can even edit / tweak the bass while auditioning it in the context of music played back from the DAW; I can change the Effect processors while auditioning it, I can EQ it, and even [STORE] my version of it to the Performance I am using... but I don’t even have to Store it in the MODX...

...Because I am using MODX CONNECT (running in the background along with the DAW), when I save my session, it will automatically save all of my custom tweaks... I don’t even need to Store it in the MODX at all... My custom versions of every MODX sound, every tweak, is stored with the DAW file... all in one place! All I need to do to get everything back is simply open the DAW File — MODX CONNECT will automatically restore all my edits. All my edits — every tweak, to every Part!

Pattern Sequencer added to the Performance Recorder with 2.00
Current situation (MODX ver 2.00) which introduced the Pattern Sequencer function of the Performance Recorder, you must select your instruments first, but that is an entirely different workflow... Create the Performance using the real-time aspect of actually playing with multiple Parts... instead of just a click, click, click of the metronome, you can use a feel-adjustable Drum groove

I have no idea how you envision using an external XML file to help you here in Pattern mode (???) what are you doing in those pictures? ... but if you’d like to discuss working with the on-board Pattern Sequencer, that’s a completely different discussion.

__In the Performance Recorder — the power there is in building your Multi Part Performance FIRST, using a combination Parts played in real-time, and multiple Arpeggios for inspiration. Later you can edit or replace what were originally Arp Phrases.

The current workflow would go something like this, setting a drum groove under control of an Arpeggio, perhaps a left hand bass Arp simply to establish the root and maybe a rhythm guitar Arp following left hand chord voicings... a lead or keyboard sound played directly across all keys. You create the Performance — it’s like choosing the members of the band... once I have an idea or two with this multi-Part Performance — assigning different Arps for different musical sections (verse, chorus, solo section, bridge, etc.) only then do I take the members of the band to the recording studio.

You do this by pressing the [Record] button. Now the Arps in each Scene can be documented to the Pattern Sequencer... each by each. The Pattern Sequencer allows what were Arp Phrases to be written out as MIDI Events... what the rest of the concept is from there is to move the MIDI events into your favorite DAW... (using MODX CONNECT). Once in your DAW you can expand on your basic idea.

Once moved over to the DAW, you can change your mind about which bass, audition several (as outlined in our original discussion), you can rewrite the bass line (often the bass Arp is just to outline the chord roots — you can then replace it with a proper bass line). You can go about creating drum fills where appropriate, and so on.

There is no one workflow, and it really is for the individual to find what works best for them. We only try to suggest what is on offer in the current firmware, and suggest that perhaps trying new workflows may help folks find their own favorite ways to work.

Extra Credit:
In my last post I forgot to tell you where to find the “Event Chase“
[UTILITY] > “Settings” > “Advanced” > EVENT CHASE

Event Chase (Song Event Chase)
Event Chase allows you to specify which non-note data types are properly recognized during fast-forward and rewind operations. Setting this to a specific event ensures the playback integrity of the event, even when fast forwarding or rewinding.
Settings: Off, PC (Program Change), PC+PB+Ctrl (Program Change+Pitch Bend+Control Change)

Check your DAW (Cakewalk) for details — often they have a similar function.