Lately I’ve noticed that when I’m scrolling through the patch menu, that action of turning the wheel and scrolling through each named preset creates a click, like an electrical click. Has anyone experienced this?
Yes. The more presets you have, the worse it gets.
And it’s more to this issue: If your preset list is at 1.000 or more, the arpeggiator will also slow down or stutter while searching for a preset or just entering the preset browser.
I think the CPU is not capable of querying a larger SQLite database (which is used in the ONE). When I add both GEO addons and all additional factory stuff, the database is at around 130 MBytes. This a lot of data for a synth, and most of the data is redundant. All parameters are stored with their description as strings, which is very strange.
To be more precise, one preset eats up between 110kByte and 800kByte, depending on its sequencer data. If we ignore the sequencer data, Moog needs 112.640 bytes to describe about 3000 different parameters. That is a great waste of space. Why? Let’s assume that all digits are save as doubles with 64bit precision, and that we have 2000 doubles and 800 booleans and 200 smaller strings (16 characters) with UTF-8. That would mean 20002 + 800/16 + 20016 = 4000 + 50 + 3200 = 7250 Bytes = 7KBytes per preset. Thus, 94% of the space are wasted.
However, if you’re in the studio, that shouldn’t bother you much. For a live scenario, create a new user space with only a few dozens presets, and you’re fine to go.
Thanks for chiming in. No, Preset Autoload is off.
The issue gets worse and worse the more presets you have in your loaded User Space. Keeping it below ~500 presets, the crackling is not a real issue and only happens when scrolling fast.
With > 2.000 presets it’s a real crackling fest.