Design: UI/UX revamp #448
Replies: 12 comments 23 replies
-
|
I think it'll be a good idea if users have at the very least the option to move the meters to the right side of the screen, like akleja proposed. Dunno. |
Beta Was this translation helpful? Give feedback.
-
|
Is it about how things look, or how things work? If the latter, I'd suggest starting with a little more in-depth user research, to understand user profiles and needs, maybe to have some questionnaire, write some user stories, then, when it comes to discussions like this, present wireframes instead of screenshots in different styles. If it's just about the style, then both look good :) |
Beta Was this translation helpful? Give feedback.
-
|
The waveforms in the 2nd concept are way too imprecise for most uses. Of course, making things look good is important, but this shouldn't come at the cost of functionality. |
Beta Was this translation helpful? Give feedback.
-
|
The waveform isn't going too look like this in the final result, it's just the artifact of the program that Marco used to draw this. |
Beta Was this translation helpful? Give feedback.
-
|
I hope so. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah both waveforms are just an proximation in both concepts. I'd want to keep the drawing mostly as is, just with some light anti aliasing. |
Beta Was this translation helpful? Give feedback.
-
|
About the loudness meters: If I see orange in the color gradient, I'm not sure if the audio is a good loudness or too loud. With flat-color zones this is much better: If I see yellow, my audio is a good loudness. If I see red, I must make it quieter. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I agree. I want the split to be at -18 dBFS, but it should be possible to adjust. |
Beta Was this translation helpful? Give feedback.
-
|
Gotta say, having the time in the top area makes more sense to me than putting it at the bottom. |
Beta Was this translation helpful? Give feedback.
-
|
Ok so I've worked some more on my mockup.
There are still some things to figure out. The RMS meter for one. Also not sure about the waveform colors, but thought perhaps a bit more contrast might be a good thing. Haven't figured out track input assignment yet either
|
Beta Was this translation helpful? Give feedback.
-
|
This is definitely the best one I have seen |
Beta Was this translation helpful? Give feedback.
-
Does this also includes things like being able to see and switch audio sources? (which currently is quite a content-size mess) |
Beta Was this translation helpful? Give feedback.
-
|
Updated and simplified a bit the structure of the meters, the top panel, improved the waveform visuals.
|
Beta Was this translation helpful? Give feedback.
-
|
I can't say which one is better. |
Beta Was this translation helpful? Give feedback.
-
|
This looks really clean and I would love to use something like this. |
Beta Was this translation helpful? Give feedback.
-
|
Could that waveform colour be made customizable? |
Beta Was this translation helpful? Give feedback.
-
|
Yes: Of course, it should be possible to change these colors, so that colorblind users can also use Tenacity without compromises. Speaking of colorblindness: If done well, the 3 colors would naturally have different values, like this:
In that case, the option to change the colors will have a lower priority as it's already much easier to differentiate between the default colors for colorblind people as well as other people. Reguardless, this theming possibility should still be made eventually. |
Beta Was this translation helpful? Give feedback.
-
|
I'd really rather that something like the OP be the default - I've always found that red-yellow-green progression really distracting in the Winamp days and it never really seemed to add anything that the two shades of blue/purple here aren't doing better. Even if the values were different enough so that they'd be visible, it sends an initial message that accsesibility is an opt-in afterthought in this case. Really, the flatter blue (or whatever) and grey is so much better looking and already accessible as a default that I don't see any reason why Tenacity should depart from that. |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate what you're saying about looks but meters exist for a very good reason, and the colours have meaning. I personally strongly disagree that the default should be flat single colour, that's to me the very definition of form over function. I shouldn't have to change settings to make the fundemental purpose of meters useful. To say that a flat colour is "accessible by default" is like saying you don't need to describe your images, because they won't be seen, so it's more accessible to blind people. Removing the important functionality of the decibel zones because colourblind people can't discern them in the default colours is a bad argument. Either make them three easy to discern for colourblind people colours and say to hell with the theme colours, or make it an easy-to-find option for colourblind people to select three colours that they can discern (point in case: there are multiple forms of colourblindness, a "default" is never going to be good for each). The fact that you think that two shades of the same colour for a 3-zone meter is "better" than red-yellow-green and referencing winamp implies you're thinking of this from a media player point of view, not a recording studio point of view. I would posit that for tenacity, the latter is more the target audience. (edited because my fingers typed audacity when my brain meant tenacity) |
Beta Was this translation helpful? Give feedback.
-
|
I get what you're getting at about form over function, it's just that the RYG stuff actually kinda hurts my eyes to look at so it is functional in that sense. Anyway, flat versus RYG is a false dichotomy when the default could be blue on the outside, yellow in the middle and some kind of dark red on the inside and it would look a lot clearer. |
Beta Was this translation helpful? Give feedback.
-
I just realized I was unconsciously thinking about the Audacity logo colours here... |
Beta Was this translation helpful? Give feedback.
-
|
Great stuff. Some points
|
Beta Was this translation helpful? Give feedback.
-
|
I just want to add some of my perspectives on this whole discussion While it might be reasonable to decide on a overall goal for the UI, I am of the opinion that these are just drafts, and whichever path we chose, much will still change along the way. They might help making all small changes lead in one direction, but they should not be considered final in any way. At least that's my preference. We need to figure out a lot of things, and I think detailed wireframes of specific components is a worthwhile focus moving forward. Trying to solve everything at once won't really work out I think. Also there are a lot of things besides the main window that needs to be reworked. There already are a few discussions going on regarding some components, and it might be better to not have parallel discussions. I suggest using the already existing issues, or opening new ones for things not yet discussed. Some UI related issues (might've missed some): There's also some prior discussions: |
Beta Was this translation helpful? Give feedback.
-
|
I would say that we wait until maybe Version 2.0 of Tenacity to do this. We're already making an alternative to Audacity, and we should keep the UI like it was in Audacity before making a change to it. We don't want to throw those off coming from Audacity, of course. |
Beta Was this translation helpful? Give feedback.
-
|
@nawordar Community feedback. |
Beta Was this translation helpful? Give feedback.
-
|
@nawordar this will improve the program in general, because: the first priority should be to get the program
Only once we are sure that this is done right, should we redesign the u-i (even if we already know the changes we will make), since doing Three major tasks (as suppose as just two) at once |
Beta Was this translation helpful? Give feedback.
-
|
Never mind, this makes sense. We should make a first stable release with old UI before changing it |
Beta Was this translation helpful? Give feedback.
-
|
Agreed but I think we have the great opportunity to improve the UI and after stable releases, there is no reason to not get to work. |
Beta Was this translation helpful? Give feedback.
-
|
I thinks some changes should be included in the first release, namely making sure the the themes apply correctly. Right now the drop downs doesn't conform to the program theme, and on some platforms doesn't match the system dark theme preference. Also the scaling of the drop downs are buggy and they get clipped on many systems. To resolve this i think a few changes are warranted (and some ongoing)
Additional major design changes I think I agree should wait until after first release. |
Beta Was this translation helpful? Give feedback.
-
|
Just an idea, you could take a page out of waveform daw book |
Beta Was this translation helpful? Give feedback.
-
After having some discussions with the team about the UI/UX direction of the project, it turned out that we need more feedback from the users (from you).
In the last few days @akleja and me worked on some different mockups of what we think Tenacity should look like in the future, however they are widely different and can't decide upon which one the development should go.
Although not finished yet and totally in wip, we think it's a good thing to get feedback now as our designs are 2 different directions (but similar in some pieces).
Here is the design by @akleja :
And here is mine:
Again though, keep in mind they are not anything near final, but it would be interesting to see what direction we should take in the future, let us know.
Beta Was this translation helpful? Give feedback.
All reactions