pcg Overview Table

This is the information I have on the x3 series .pcg file.
(also known as KORG5 format)

Note: all numbers givin are in decimal. (10 base) and are on record
position. (i.e. first byte of file is at record position 1)
The numbers are NOT in offset mode (i.e. first byte is offset 0) because
I use Qbasic for programming and I am making this list dammit. :)

If you want offset - subtract 1.
If you want Hex - whip out your dec-hex calculator. :)
Anything with a "?" means I havent a clue. (Tell me!)

Currently all I got is the names and the sizes of the patch data. I dont
have any details on what each of the 154 bytes in a program or the 126
bytes in the combination patch area.

I still havent a single clue what the heck record position 6 - 88 is for.
Anybody have an idea on that one?

There are areas in the global parameters that are missing or not understood.
Please feel free to check out X3Global.doc for more details on that.

The Drums Section needs a bit of fleashing out as well. Check out the
X3Drums.doc for more details on the drums specifics beyond patch locations.

What can you do?
Pick a section - or email me first and ask which section you should do so
we dont duplicate efforts. Then use the tried and true method of using a
hex editor to see what the changes you make on a patch or whatnot does
to the file. I have fabricated a general hex viewer to help me out and
I will place it in my special programs directory /pub/jonin/dos if you want
to use it. I am also going to make a program to help me disect the mess
a bit by focusing on the key areas. (i.e. my program would only show the
126 bytes for patch A00) This might be more usefull as my program could
know the values from the 'blank.pcg' and use that as a reference to highlight
differences.

If you find any hard information - please email it to me at jonin@netcom.com
Or you can throw it in the X3-FTP incoming directory at FTP.NETCOM.COM
(/pub/jonin/incoming for incoming files. /pub/jonin/x3 for X3-FTP)

With a little help - we should have this file nailed down fairly quickly.
Then we can get on to the patch-editor! :)