akp programs & importing

[hello mate]

Hello there

I'm sure I'm doing something wrong but when I import a akp file the mapping in the keyboard mapper seems to be a bit odd, when viewed in awave or even loaded in another sampler like directwave it seems to load fine and as expected though

for example a program of mine

progname -
HELLO_BASS

Layer 1 -
a001 -L.wav - c2 to b2
a002 -L.wav - c3 to b3
a003 -L.wav - c4 to b4
a004 -L.wav - c5 to c7

layer 2 -
a001 -R.wav - c2 to b2
a002 -R.wav - c3 to b3
a003 -R.wav - c4 to b4
a004 -R.wav - c5 to c7


(shows as it should in awave + loads in directwave as expected)

these are mapped across the keyboard zones mentioned in the program

but when loaded into TX16 I seem to get 4 groups with some different mapping to expected

the 1st 2 groups are fine

group 1 - layer 1
a001 L.wav - c2 to b2

group 2 - layer 2
a001 R.wav - c2 to b2

that's how I would expect them all to be treated 1 split to a group not 3 like the later groups

the rest load in a way I wouldn't expect

group 3 - layer 1
a002 L.wav - c3 to b3
a003 L.wav - c4 to b4
a004 L.wav - c5 to c7

group 4 - layer 2
a002 R.wav - c3 to b3
a003 R.wav - c4 to b4
a004 R.wav - c5 to c7

so there are like 3 splits to a group for some reason, I'm sure I'm doing something wrong here

seems to do it on every akp program I load into TX, am I doing something wrong here or misunderstanding something, I thought I'd take the time to write in case it was a problem.

[hello mate]

Okay having a little mess about I've figured you can manually go in and make groups from splits but it's fiddly and I wonder why I would need to?

anyone can shed any light on why this happens?