Yes, as JFord mentioned, the problem you are seeing is caused by Sysex and Program Changes (CC's) in the midi file themselves and not from your DAW. Your DAW is just processing the code that's there and is sending this to your M1 which is executing the instructions. This is a common problem with downloaded midi files.

The way I resolve this is to delete any Sysex and CC's that are associated with patch changes. Look for CC's that are associated with program changes, such as 0, 32 and Program Change (PC). These are usually group together in the midi event editor and might be listed as follows:

CC0=63
CC32=2
PC=4

Removing these will allow you to assign specific patches to each track. When you save the file, either using RB or Sonar, the DAW will remember the patches that you select.

Patch selection is easiest if you use a "patch list" specific to your M1. That way you can assign the needed patch directly from inside your DAW.

There is a Korg M1 patch list located here on the PG website: http://www.pgmusic.com/support_miscellaneous.htm

Jeff

Win11, Intel i7 7700K 4.2Ghz, 32Gb RAM, 2x1Tb HD, 500Gb NVMe, BIAB/RB 2025, MOTU 828MK3 audio, MOTU Midi Express, Yamaha Montage 7, DX7II, TX802, Motif XS Rack, Roland Fantom XR Rack, Oberheim Matrix 1000, VoiceLive3 Extreme, Kontakt 6, SampleTank 4.3