Xpantastic!

> When you say cmd line do you mean a DOS based running under say XP or
> would I have to get a linux shell running in my PC?

The program would run in any Microsoft OS in the CMD shell (what you
called DOS-based), and also Linux & the Mac OS.

I've know of a program written this way to translate patches from a
first generation synth to a second gnereation synth, of which the
two synths have NOTHING in common other than the manufacturer. The
patche formats are 100% completely different..

> I like your Idea of just filtering and replacing the appropriate
> M1K code with M12 code. I am not clear on the Expander data format
Greg has alreayd uploaded the XPander patch format, as a PDF,and it's
beautifully formatted compaired to the original.


> but I have taken a look at my M1000 manual. The sysex patch file is
> pretty straight forward. Everything hinges on the data position in
> the file.

Position, range, ( 0-63, -127) and sign to be more precise.

> As PeWe ponts out it would certainly be easier to go from the M1K to
> the Xpander than the other way around.

I agree


> Looking at the M1K sysex file :The MOD sources/destinations all Have
> a number assigned to them, I suspect it's the same on the Xpander/M12.
Yes, download the news sysex spec that was uploaded by Greg.

> But wait, there are all those hardwired mods on the M1K.
And on the XP/M12 too

These may not be the same on both machines

> This creates a problem with the Xpanders 20 routing max.

One of the many questions that must be answered before a program could
be written to assist.

>
> BTW: If you find the posted M1K sysex file lacking I have the manual
> and my wife has a scanner that will create a PDF file from the scan.

I've found a PDF of the M1k manula. No need to scan it.
Thanks