It seems to me that MODX assigns numbers to files in memory and the names do not have much meaning?

Maybe there is a problem in the file you are loading?

Maybe, but I listen all files they seem to be correct.
All files has equal size and short time 0,400 in Sound Forge.
I will search problem...

---
Oh, idea! I will try to make X8U starting with only layer# 02-samples! Maybe thay corrupt...

I've make second layer of my samples into X8U and install it sucsessful. Samples has not errors.
I load directly via "add keybank" into "New Waveform" on hw MODX sampler.
The names
@010101.wav
@010201.wav
@020101.wav
@020201.wav
010101.wav
010201.wav
020101.wav
020201.wav
No problem!

Only one comes to mind this is bug into MODX load manager
batch install fails with unknown errors

But problem mayby depend of names style

I'm in panic 🙂
I don't understand anything anymore.

I'm already afraid that modx memory problems.
Some installed Library Import report No Data 😮

I do Initialize All Data. Seems to be OK. Import now works.

But this crazy samples again stupid.
I rename anyway
zzz0101.wav
0101zzz.wav
Guitar C1.wav
all 200 samples.
In addition I convert this in Audition with 16 bit. Nothing to good.
Crazy staff.

Maybe user memory corrupt? 🙁
But some libraries I install now agayn.

renamed and converted 24 to 16bit 44 to 44kHz Stereo to Stereo...
Samples with watermark? 😮

I use John Melas Waveform Editor

In MODX Edit Waveform I see the strange that
the keybanks turn upside down.
120, 119, 118... 2, 1

Keybank full. <<<

I try to build custom perfomance in MODX.
What is mean? 128 is limit?
I have my old performance with more semples into waveform. How it possible?

My old working bank with 256 items

Yes, I understand! 256 MONO 😮
128 Stereo is it limited? That's what was the matter.

I've mentioned this before with much push-back from Yamaha. I think it is critical for the keyboard to have summary screens that tell you how close you are getting to various water lines. "Keybank Full" has two possible ways to show this error. Either one Waveform has too many Keybanks (a lower limit) or the instrument supports a maximum total number of keybanks (for all waveforms combined).

Somewhere buried in the message base, which is now incredibly difficult to search, is a post from Bad Mister where he gives the statistics for maximum keybanks. I don't find this information in the docs -- but I've had problems locating information in docs before.

At any rate - even if you had the maximum number of keybanks supported (say it's 2048 - like Motif XF) then you wouldn't know how many keybanks you are using. At least not on the instrument itself.

Since you have JM Tools - maybe it provides the necessary statistics so you can know how close you are to this waterline. This analysis can only be done either using an X8A file (backup) or somehow polled from the instrument using some form of a scan.

BTW: the sort order is up to you.

From the docs:

2) Keybank Parameters Edit
This window allows you edit basic parameters of the selected Keybank of the Selected Waveform. These parameters are: Level, Pan, Root Key, Key Range, Velocity Range, Coarse, FineTuning and Loop Mode. Keybanks can be sorted by any column by clicking on the column header. They can be reordered using drag and drop or Ctrl+Shift+Up/Down Arrows.

You can click on the column header to reverse the sort order.

... and it looks like JM Tools do not show you the total keybanks used. So you'll need to get a calculator out.

My assumption is that when you run into problems the total number of keybanks exceeds 8192 or whatever the MODX limit is. So what I would do is get the "keybank full" message then add up all used keybanks and see what that number is after adding 128 (if the failing waveform you try to add has 128 keybanks). Whatever this number after adding would be above the limit and whatever it was before adding would be below the limit. You can then infer what the limit actually is based off of multiplying 8192 by 1,or 2 and then multiplying that result by 2 ... and so on.

I don't think the 256 limit is being exceeded because after initializing (remove all the other keybanks) the problematic waveform loads without issue. Assuming this is an accurate description of what's going on - the problem would be with exceeding the total keybank limit for all waveforms and not the 256 limit.

The link provided isn't what I was referring to because it only lists the max # of keybanks per Waveform. Not the max # of keybanks for all Waveforms.

The keybank limit is "kind of" defined here:

https://www.yamahasynth.com/forum/load-xf-x3a-files-into-montage#reply-13383

Although the documentation mentions max # of keybanks (samples) for the Motif XF. And, BTW - this was per flash board where the Motif XF has two flash boards. I'm inferring the limit is 8192 although this may be incorrect.

Therefore, I advise using the error to find out what the limit is before and after loading the last Waveform that produces a "Keybank Full" error.

It'd be great if I could point to some documentation page that shows the limit but I haven't been able to find this. That doesn't mean it's not documented. Just that (IF it does exist in documentation) it's not well indexed for searching. And I do search for 8192 and power of 2 (2^13 = 8192, 2^14 = 16384, etc).

If you knew the limit and there was (a not yet existing) menu that told you the number used -- you could self-serve knowing why you received a "Keybank Full" message.

The main point here is that there is a limit - in terms of count. How much "size" they take is irrelevant. I take it the internal index of all keybanks is a variable of some # of bits which constrains the count.

Other threads BM mentioned that the Montage/MODX limit hasn't been "officially" (internally) published so he assumed Montage/MODX would be constrained to 8192 based off of Motif XF's per-flash-board limits. There may be another message with more elaboration but I cannot find it.

If not done already, the JM Tools should really add up all of the keybanks used so you know where you sat in terms of that statistic. I see the data is available but you have to add up the keybank count per waveform. Loading an X8A into JM Tools will give you all Waveforms for User and Library. I only have the demo version of JM Tools so there's a limit to what I can support.

Yes, Bad Mister said it.
But I myself understood this, that the number of virtual keys is tied to key banks.
I just didn't think about it initially.
When I installed the bad X8U, I didn't get any message other than "Now loading... Please don't turn off the power."
Big thnks to all 🙂

Some resources are expressed in size. 1.75GB (or 1.8GB or 1.0GB depending on your rounding and model). This is a size-based parameter. Some are count based. The size of each is irrelevant because we're giving a count and the size doesn't matter. It could internally take any size (it is what it is) - but the count is what the limit is not the number of bits storage of the associated record takes.

Whatever the storage required for each record certainly translates to a "size" in memory. However, there is such a thing as memory compacting so the storage required may not be exactly count*some_fixed_number. Therefore I say the size is irrelevant to know because it really doesn't matter. Being concerned with size for a count-based limit is placing, unnecessarily, an additional layer of complexity. And internally any memory compacting/compression/etc. need not be considered either. The count is what matters. There is a limit and you cannot exceed that count.