On 05/26/2017 06:22 PM, Daniel Schürmann wrote:
Why do we need a special radio skin? What would be useful on a radio
specific skin that isn't already available in Tango or Deere?
The layout and features for a radio skin are quite different. We can
indeed support all required features in Tango or Deere, but a typical
radio DJ will never feel hat home. If we try to support both use-cases
(DJ + radio) in a single so skin we probably do a bad job for both.
When I think on a radio skin, I think on a card wall player, fader
start, a big wall clock, a big "on air" lamp. First class multi mic and
Aux integration.
Deere and Tango both support all 4 mic & aux inputs supported by Mixxx.
Fader start is not a skin issue. I think a big wall clock would probably
be better served by an actual wall clock rather than a computer screen.
Deere and Tango both have on-air indicators, but they could be more
prominent if that's desired.
If we want to design for radio DJs, we should do usability tests with
radio DJs. Watching real people interact with the design is much more
useful than asking people on the Internet for feedback. Usability tests
are quite easy to do: https://www.youtube.com/watch?v=VTW1yYUqBm8
I think the new sampler designs will be welcomed by radio DJs.
Yes. That is a good start, but it is still not a real card wall player.
What is a card wall player?
If there are improvements that would help radio users, I'd rather
modify Tango and Deere than fork them or make a new skin.
A good skin maintainer for a radio skin, is most likely not a good
maintainer for a DJ skin. But a good skin with a consistent design is
maintained the best by a single developer/design artist.
I disagree. A good skin is best designed by a team collaborating and
reviewing each others' work.
As for Mixxx being known for the aesthetics in LateNight, Mixxx has
been criticized for this:
"While the current skins have been tweaked and improved there still
needs to be work done to make the default ‘LateNight’ skin a bit
more contrasting. It suffers from a similar issue to what I
experienced on the Xone:43C: too much red/orange on black."
https://djworx.com/quick-look-mixxx-2-0/
<https://djworx.com/quick-look-mixxx-2-0/>
Personally, I agree with that sentiment. I don't like the colors in
LateNight. Perhaps a good designer could adjust the colors a bit to
improve the situation without having to do a major redesign, but
picking good colors is tricky. On the other hand, many people I have
shown Deere have quickly been impressed with the look of it. I think
Tango is looking really good too, but it could still be improved
with some adjustments to the waveform background colors.
If there is a common sense that the yellowish LateNight does not look
good, we can drop it. @ywwg: what do you think, what are the reasons for
or keeping it?
It seems that Jorge does not have time to fix the outstanding issues
in DarkMetal, but if someone else volunteers to implement the
changes outlined above changes and those mentioned in the pull
request ( https://github.com/mixxxdj/mixxx/pull/1179
<https://github.com/mixxxdj/mixxx/pull/1179> ), we could include it
in 2.1. That would take quite a lot of work.
It looks like, we look at Mixxx skins from. different view. For me skins
can be used to allow different use cases (Skin A optimized for use case
A) and different visual and taste preferences. It is not required to
support all in all single skins.
So as long we have a good default settings skin that looks good and
works, for the most common on use cases, there is no need for or
additional Skin doing the same. From this so poin of view we there is
no need to copy all Deere features into Shade an DarkMetal.
All skins should support all features, otherwise some users will have to
choose between features and their preferred aesthetics. Users should not
be tied to a skin because their controller mapping doesn't work well
with other skins. I think Deere and Tango both demonstrate that if a GUI
is well designed it can satisfy many use cases without the maintenance
burden of a skin for each use case. We need peer review, input from
people using Mixxx in different ways, and empirical observations from
usability tests to create good designs. Like good code, good designs
generally don't come from just one person pursuing their idea.
Please remember to use Reply All to send replies to the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
