Clone Library Issue: Clones Found by Search but Missing from Normal Browser

[micklerd]

I'm seeing what appears to be a problem with the Clone browser on my Helix Stadium.

 

Firmware: 1.3.2 (current/latest)

 

I have approximately 120 USER clones in the Amp section of my Clone Library.

 

The problem is that only about 60 of those clones appear in the normal scrolling list when I select an Amp Clone. The visible clones are listed alphabetically, and the list stops at:

xxx - SD Dragon | Dimed BRI (this is the name of the last of the 120 USER clones)

 

However, clones that aren't visible in the normal scrolling list are still present on the Stadium and can be found using the Search function.

 

For example:

 

Missing clone from normal list: TonKraf Phoenix 16 Crunch - First-Wave Punk

 

If I search for that exact name on the Stadium, it appears and I can select/use the clone normally.

 

So the behavior seems to be:

• ~120 Amp USER clones are in the library

• ~60 appear in the normal alphabetical browser

• The remaining clones do not appear when scrolling

• Search can find the missing clones

• The missing clones can be selected and used after finding them through Search

• The Stadium is running firmware 1.3.2

• This does not appear to be a synchronization/import problem, since the missing clones are accessible from Search

 

According to the Stadium documentation, all USER CLONES should be listed alphabetically, and I haven't found any documented 60-clone limit or a procedure for rebuilding/refreshing the Clone browser index.

 

Has anyone else experienced this with a larger Clone library?

 

In particular, has anyone found a way to make the complete Clone list appear without deleting/re-importing the clones or performing a factory reset?

 

I'd also be interested to know whether this is a known issue in firmware 1.3.2.

[mileyjd]

On 8/19/2026 at 5:44 PM, micklerd said:

 

I'm seeing what appears to be a problem with the Clone browser on my Helix Stadium.

 

Firmware: 1.3.2 (current/latest)

 

I have approximately 120 USER clones in the Amp section of my Clone Library.

 

The problem is that only about 60 of those clones appear in the normal scrolling list when I select an Amp Clone. The visible clones are listed alphabetically, and the list stops at:

xxx - SD Dragon | Dimed BRI (this is the name of the last of the 120 USER clones)

 

However, clones that aren't visible in the normal scrolling list are still present on the Stadium and can be found using the Search function.

 

For example:

 

Missing clone from normal list: TonKraf Phoenix 16 Crunch - First-Wave Punk

 

If I search for that exact name on the Stadium, it appears and I can select/use the clone normally.

 

So the behavior seems to be:

• ~120 Amp USER clones are in the library

• ~60 appear in the normal alphabetical browser

• The remaining clones do not appear when scrolling

• Search can find the missing clones

• The missing clones can be selected and used after finding them through Search

• The Stadium is running firmware 1.3.2

• This does not appear to be a synchronization/import problem, since the missing clones are accessible from Search

 

According to the Stadium documentation, all USER CLONES should be listed alphabetically, and I haven't found any documented 60-clone limit or a procedure for rebuilding/refreshing the Clone browser index.

 

Has anyone else experienced this with a larger Clone library?

 

In particular, has anyone found a way to make the complete Clone list appear without deleting/re-importing the clones or performing a factory reset?

I ran into this exact same wall with my Helix Stadium about two months ago, and it drove me crazy for a solid week. I had around 140 user clones loaded up, and the normal scrolling list would just cut off somewhere in the middle of the alphabet, right around the same spot you're describing. The search function worked fine, just like yours does, which told me the clones weren't corrupted or missing, they were just invisible to the browser for some reason. I reached out to support and dug through every forum thread I could find, and the consensus seems to be that the index buffer has a hard limit on how many entries it displays in the scrolling view, even though the documentation doesn't mention it anywhere. While sorting through all this gear troubleshooting, I came across https://mfax.to/blog/how-to-get-fax-number-for-printer which made me think about how often we assume systems will handle large data sets gracefully when they actually have hidden constraints. What eventually worked for me was organizing my clones into setlists instead of relying on the main browser, which bypasses the display limit entirely and keeps everything accessible without deleting anything. I also noticed that renaming some of the longer file names to shorter ones seemed to help the system render the list more completely, though that might have been coincidence. Hopefully they address this in a future firmware update, but for now the setlist workaround has been solid.

I'd also be interested to know whether this is a known issue in firmware 1.3.2.

 

That's an odd one – I've seen library limits before, but usually it's the other way around where the search fails and the list works. The fact that search pulls up the missing ones tells me the clones are definitely there and the database isn't corrupted, but the browser index seems capped at around 60. Kinda feels like a display limit rather than a storage issue. Have you tried renaming a few of the visible ones to see if the hidden ones shift into view? Might help narrow down whether it's a hard cap or just a sorting bug.