Hello, the interface is lovely and all… BUT:
the tiny line to adjust ‘Max. memory allocated for tracks preload’ is sooo short it makes it a very difficult adjustment. I basically have a very hard time not jumping from 256 to 2000-3000. I can’t imagine I am the only one.
**Please make the number field editable, makes things much easier.
DAWs and audio plugins (and graphic design apps) for example generally approach things that way (on top of cute interfaces with lovely buttons and all) so as to allow for fast precision.
IMO all numbered options/prefs in any app should also propose an editable field.
You have a point here but otoh it shouldn’t be much hassle to change this to a numbered option. The effort should be tiny in comparison to creating the parametric equalizer…
@matt@Djm1960 … What makes the perfect ‘number’ or ‘figure’ in the context of playback pre-load memory? It looks to me that the system rounds this off anyway…
I notice on my Audirvana (Origin and Studio) on Windows, that the UI’s behaviour is very unpredictable/inconsistent with all the ‘sliders’ in the settings and not only for memory allocation, but also for resample values, volume percentage values etc. Some of those require a precise number and a ‘estimated’ slider position won’t cut it.
In some cases I can get to those elements with the Tab/Enter keys and then more or less precisely change the values with arrow keys. Some work and some don’t.
Microsoft and Apple have published ‘best practices’ to follow when designing a UI. One of them is also that a desktop UI also should be completely usable with only a keyboard. Almost all desktop programs I use follow those rules, including the possibility of manual entering a number when a slider/knob receives focus.
One of the (many) examples in Audirvana is for instance this slider:
I can ‘Tab’ to it and then I see a (barely visible) outline, but I can not precisely give a value there (let’s say 92%). I can not manually enter a number and I can not precisely move the slider with the arrow keys. When sliding with the mouse the value is basically a gamble.
This behaviour is not consistent because it varies between different sliders/controls.
In 99% of desktop apps in Windows these kinds of settings are no problem at all and behave like expected with keyboard and mouse.
For me this is one of the many small annoyances in Audirvana’s GUI which exists for years already and never seems to get solved. It is not a dealbreaker for me, because of Audirvana’s SQ. I have also accepted that the Audirvana team is probably very good in programming a good sound engine, but less so in GUI and practical use design.
But in short: don’t try to convince people they should not perceive things as a problem, because you don’t perceive them as a problem. That is a very egocentric approach. It is like discussing the taste of ice cream. You can argue that chocolate ice cream tastes superior until the cows come home, but in the end others will still prefer vanilla.
You make the juxtaposition to another context… I pointed out that in this case with the pre-load memory, that I don’t see what the hassle is… What somebody makes of this is entirely subjective…
Nope I simply extrapolated this issue to a broader perspective because the issue in this thread is a small part of a broader problem.
If you can’t see that connection that is your prerogative
I don’t think there is a perfect number. I set mine as close to 6144 MB as I can get. Monitoring AS memory use it is a miracle of minimalism when compared to other playback software and I have seldom seen AS using more than 2.5 GB of ram but then that is only when sampling to 768 PCM, I don’t use DSP or do anything more complex. Bit perfect playback results in AS only ever using less than 1 GB with my PCM files.
No intentions of a narrative about you, merely my brains desire for neatness, irrespective of the factual conditions. My comment was meant as a self deprecating joke, my OCD is my issue………
Only time I think this is an issue is for those with minimal amounts of RAM. I use Mac OS and it is quite the RAM hog, but then it is designed to be, it loads a lot into RAM to speed the OS based on the premise that “unused expensive RAM is wasted RAM” if my system only had 8GB I would say setting this much above 2GB is not a good idea as you don’t want to impact performance of the OS. I typically buy Macs with 64 GB or 128 GB so not an issue. (Other than it makes it more difficult to soothe my OCD by setting a precise amount of allocation using Audirvana’s slider!)
So called “magic numbers” in a programming context often refer to specific values, and these values are frequently powers of 2… It should be easy to set a buffer at 2048 meg, otherwise know as 2 gig, but its not with the GUI of Audirvana…
I set it and it is done… doesn’t need to be perfect…
I see the connection, however you usurped the premise of my viewpoints on this particular function, in-order to fit your narrative about me.