This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
roadmap:settings_analysis [2017/01/21 15:16] – [From the user perspective] muldjord | roadmap:settings_analysis [2017/01/22 15:23] – [Suggestion] muldjord | ||
---|---|---|---|
Line 1: | Line 1: | ||
=====Settings Analysis====== | =====Settings Analysis====== | ||
+ | ====Suggestion===== | ||
+ | Two step drumkit load: | ||
+ | * Users selects a drumkit file (as we do today) and clicks " | ||
+ | * Now the drumkit xml is loaded and the MemoryChecker analysis it so we know the estimated size of it. | ||
+ | * User then (optionally) turns the knob for memory preload, which live updates the estimated usage numbers in a label. | ||
+ | * User clicks " | ||
+ | |||
+ | While loading and while playing we could then have a label showing " | ||
+ | |||
+ | Muldjord: I quite like how it is right now. It's simple. Click to load the kit and it will load to the specified limit. Adjust the limit and purge if you need it. Less clicks and easy to understand. I don't think this needs redesigning. | ||
====From the user perspective===== | ====From the user perspective===== | ||
- | We should probably just give a "RAM usage" knob to the users, as this will probably be the only thing they can relate to in general. | + | // |
Additionally we could (at least in the beginning to see if it makes sense) give some info how many samples per sound file are cached (which should also help us debug issues when they can simply tell us the value that is shown in the GUI). | Additionally we could (at least in the beginning to see if it makes sense) give some info how many samples per sound file are cached (which should also help us debug issues when they can simply tell us the value that is shown in the GUI). | ||
This shown value is of course dependent on the drumkit. | This shown value is of course dependent on the drumkit. | ||
Line 7: | Line 17: | ||
And of course we should store this value in the drumgizmo config file. | And of course we should store this value in the drumgizmo config file. | ||
- | Muldjord: A "RAM usage" knob seems like the right way to go. I would also, in combination, | + | //Muldjord:// A "RAM usage" knob seems like the right way to go. I would also, in combination, |
+ | //Deva:// The "Purge and Reload" | ||
====The technical/ | ====The technical/ | ||
From '' | From '' |