First, aside from our discussion on building a .pat file, based on what you said I think you might be confused on how these VSTi's get called up by BIAB (and ANY DAW). Assuming you have a pat file for a certain synth (VSTi), or you do convert the Sonar .ins file to a .pat file, you must STILL tell BIAB, or ANY DAW not just BIAB, to load the Korg M1 or whatever synth/VSTi you want.

BIAB will not CALL UP the Korg M1 VSTi by simply using the Korg M1 .pat file.

Next, what I was explaining above was how to CREATE a FULL .pat file that has ALL of the Korg M1 patches, not just first factory 100, but all 2600+ programs (aka patches).

I was just suggesting a STARTING point: by using the one converted from Sonar (the .ins) by BIAB into a .PAT and ADDING to it.

I was NOT suggesting you keep editing the same file over and over or even creating a separate .pat file for each 100 patches (one per card as it were) that would be tedious to use - you'd have to remember which Korg M1 "Card" had which patch and call up that .pat file.

Good luck
Larry

Win10Pro,i9,64GB,2TBSSD+20TBHDDs,1080TI,BIAB'24,Scarlett18i8,Montage7,Fusion 8HD,QS8,Integra7,XV5080,QSR,SC-8850,SPLAT,FL21&others,Komp.14,IK suite&others, just a guitar player-AXE FX III &FM9T, FishmanTP, MIDIGuitar2, GK2/3'sw/GI20