Sorry⦠will redirect my postā¦
![]()
I apologize for the misrepresentationā¦
Your assertion of your UI/UX suggestions as being ābetterā, are subjective and must withstand the scrutiny of the fundamental engineer(s) of the application, as to the core audio-engine ramifications if any and the value of such re-inventionā¦
One thing for you to consider in your dogma as a designerā¦
āPerfection is the enemy of the Goodā
This āperfectionā is the hubris of oneās subjective perceptions⦠which is intrinsically tied to a cognitive bias termed āNaĆÆve Realismā in the realm of social psychology.
Your suggestions may well be āBetterā however this potential must be borne-out through extensive testing across a broad base of users, in-order to find a consensus that aligns with your view of the flow of the UI elements that you believe to be āBetterā⦠There must be a compelling rationale for changes to the current UI/UX⦠So far, for me personally, the current UI/UX is fine. I donāt see a majority of users crying for a huge change in the UI/UX of AudirvÄna, only a minority of users that have complaints of various reasons and perspectives.
Again the precept of āa well thought out UI/UXā is a subjective one⦠It appears that the majority of neophyte users of the application are not having problems with the user experienceā¦
In regard to this rhetorically hyperbolic assertion and other unqualified and subjective opinions asserted by @pjmorley regarding the concept of ābit perfectā:
It is not relevant⦠In reality, the majority of users donāt have a problem with the AudirvÄna experience⦠Technically, the application aligns with the premise for the design of the audio-engine, etc, mandated by Damien Plisson. (As is described in my prior link to āAboutā) And it is apparent that in the opinion of a large demographic of AudirvÄna user audiophiles, both experienced and not so experienced, that there is no consensus of compelling rationalizations for changeā¦
Every UI requires a learning curve⦠What must be well thought out, is the rationale for changes to the UI after familiarity has set-in⦠Change is not always āBetterā.
I am an Apple Logic user⦠my perspective comes from decades of using different Apple UI/UX beginning with Apple IIe DOS and BeOS through to macOS and iOS⦠I have worked with a myriad of audio-centric applications and UIās⦠We just adapt⦠this is the reality⦠āBetterā is a relative construct.
NaĆÆve realism (psychology)
In social psychology, naĆÆve realism is the human tendency to believe that we see the world around us objectively, and that people who disagree with us must be uninformed, irrational, or biased. NaĆÆve realism provides a theoretical basis for several other cognitive biases, which are systematic errors when it comes to thinking and making decisions. These include the false consensus effect, actorāobserver bias, bias blind spot, and fundamental attribution error, among others. The term, as it is usā¦
![]()
And beauty? Donāt get me started. Margaret Wolfe Hungerfordās ābeauty is in the eye of the beholderā might be the most sensible thing ever said on the matter.
Phil
Sad to see one personās well meaning suggestion so quickly devolve into prententiousness, dismisssive and baseless claims, and borderline gaslighting. Several people here should be ashamed of themselves and appologise to the OP.
Itās all opinion and subject to connotative interpretation ![]()
These sorts of UI/UX suggestions should be presented to the AudirvÄna team, not displayed here⦠The OP got a feel for the opinions of others regarding the changes to the AudirvÄna UI/UX in question.
Your connotative interpretations are just opinion⦠and you got feedback regarding your perspectives.
We will see how much traction this gets⦠The OP was looking for affirmation blinded by hubris and got some valid criticism from a user that does not see the value⦠This does not mean that I am the arbiter of these thingsā¦. Consensus will be the arbiter of the value of these opinions in the context of the current AudirvÄna user experience.
![]()
And you posted there at the right place in the forum ![]()
Your mockups look great. I saw your email about them, and our team will review them. Our primary focus right now is the Remote app, but we know we need to improve the AudirvÄna software UX/UI, and they can help us get some ideas.
Note that as we also have streaming services on Studio, the mockups you sent would need some changes to be used with AudirvÄna Studio.
Hi Antoine, thanks ![]()
You are correct that my mockups are for Audirvana Origin, not for Studio. I initially started creating these mockups with Origin in mind because thatās the Audirvana version that I use, and also because the main focus of Origin is āplaying musicā. Thatās why I started with this version for my original mockupsā¦
The most recent versions of my mockups are a little bit more refined, so now itās easier to add the streaming services of AS⦠I try to create some mockups for AS later this week ![]()
Iām surprised the forum admins allow this sort of personal attack.
Your connotative interpretation of my statement is incorrect⦠And you parsed it to reframe the context to fit your narrativesā¦
This is the context of that statement:
Read through the entire thread⦠My interpretation was based on statements like this one below:
However, I can handle your ad hominem attack⦠![]()
We now have an authoritatively relevant opinion from the AudirvÄna folks.
![]()
![]()
The forum also provides a handy ignore utility so you or anyone else can choose not to see posts or comments from anyone you feel is being unfriendly or unproductive.
Nice work @Stijn_Van_Nuffelen
Personally, I donāt really have an issue with the UI of Studio.
However, it would be nice to add or remove certain functions.
In my case, the Podcasts, Radios and My Music menu items.
Oh, and the choice to use SQUARE album covers. Probably just me, but I hate the circular covers we have now.
Each to their own though, so keep up the good work fellaš
Honestly, I think this forum would get far more traction if Antoine were to include one of these with every subscription to Origin/Studio:
Thanks! in my mockup for Studio, you can edit the list of sources, so the app will show you only the services you use:
Very nice @Stijn_Van_Nuffelen ![]()
Also SQUARE icons!
YES
![]()
i hope for a UI redesign at some point cause the current one on mac is still a messā¦
I donāt see the value in putting a bunch of resources into trying to change something that is not broken⦠It seems that the folks not comfortable with the current UI/UX are spending time fretting over things that donāt fit their logic patterns and less time seriously listening to the music⦠Personally speaking, it seems trivialā¦
As long as the UI works as expected, does it really need a redress?
I play a very wide variety of music genre and format, from PCM (CD quality) and PCM (up to DXD 352.8kHz), all being modulated (upsampled) to DSD128 after plug-in HRTF DSP and DSD binaural files⦠I have no problem sorting these files and accessing them⦠I personally donāt even have album cover artwork on a portion of my library⦠What I am personally concerned with is the absolute presentation of the digital-audio signal being presented to my DAC, and the current UI/UX does not hinder my playback experienceā¦
The only thing that would make a difference to me, would be a redress of the UI that actually had less impact on CPU operations and graphics support influences on the core audio-engine performance.
![]()
Nice work @Stijn_Van_Nuffelen - leaner, cleaner, more legible = better to use and more pleasing to the eye
I can see where youāre coming from. Letās say that I agree that at least a deteriorated performance because of UX improvements should be a no go area, but I think thatās a shared opinion by the most users.
I think both parts would be preferable goals for AudirvÄna.
Easier for the user to navigate, less click actions needed as a goal for the UX designer and less CPU usage as a goal for the devs of functionality.
As far as I can tell by his answer @Antoine stated that the devs see the need for UI/UX improvements too, so I guess that that need may come from possible achievable improvements on the part of performance with this as well.
The constructs of āEasierā and āBetterā are contextually subjective⦠I donāt know about others, however, in my playback routine, I spend very, very, little time interacting with the UI having learned how it functions (which was easy to learn), and there are zero obstacles in finding the files I wish to play with the current UI⦠Cosmetics is a different perspective⦠Operational efficiency is also contextual and subjective.
We will see how much traction the flow of these mock-ups will get in the context of reduction of CPU operational support and the ramifications on the core audio-engine performance⦠It seems folks think that an image on the screen or remote control interactions do not require CPU cycles in concert with graphics sub-systems which require interrupts⦠How influential these routines are to the digital-audio signal/data flow/integrity of the signal on any given system platform is dependent on the platform capabilities⦠My M2 Max Mac Studio with 64GB RAM and multi-core graphics sub-system with 400GB/s memory throughput probably will handle the overhead⦠However, I am looking into the future of digital-audio reproduction with this platform⦠not the capabilities of reproducing gross graphical overhead.
![]()



