On 05/28/2017 11:36 AM, Daniel Schürmann wrote:
@Stephan: thank you for stepping in here.
Is a card wall only skin really sufficient for a radio station, or is it
only one device, along with a dual CD player and such?
Looking at dedicated broadcasting apps, the often feature a card wall
with a common volume slider + two dedicated decks we with individual
volume sliders.
Should we consider this his ad well?
Yes, the current sampler grids are just a quick hack to approximate a
more versatile sampler deck feature. With the Hercules P32 mapping I
have made these work more like decks by making the controller script
assign the samplers to the corresponding sides of the crossfader. It
would be great to group samplers into a virtual "deck" with all the
normal deck controls like volume faders and EQs. This would also make it
more practical to manage putting effects on samplers. We should look
into Traktor's sampler deck and remix deck features for inspiration. I
think we can come up with a single unified sampler/remix deck feature
that could work equally well for live remixing and radio DJs.
@be: why not add a dedicated "Deere Card Wall"? This can be re-use all
files from the Deere folder, just coming with its own skin.xml. For such
a radio use case, all additional configuration features are just
clutter. Instead we can focus on different config options, we discover
usefull for radio DJ as required when using it.
My hesitation is mostly because of the maintenance burden. I think we
should try to do as much as we can with unified skins. If we end up
deciding that different use cases have incompatible needs, then we could
clone the skins and rearrange the skin.xml files right before the
release. Otherwise we'll have to continually synchronize the skins each
time a change is made.
The extra window card wall extending current Deere is also a good idea
an should not be hard to implement following RJs idea in the liked bug.
Of cause it is not that flexible as we now it from certain development
tools, but it exactly solves the use case to drive a disk screen setup.
I prefer that way, as a short term solution, instead of waiting ages for
a widged docking skin.
Okay, but let's leave this for after 2.1.
Am 28.05.2017 6:00 nachm. schrieb "Be" <b...@gmx.com <mailto:b...@gmx.com>>:
I do not see anything different from a "cart wall player" and a grid
of samplers other than the name. Cart wall software displays more
information at a glance on the samplers like user defined color
coding. Those features do not yet exist in Mixxx. It would be nice
to add them and not just for radio users. I don't think this will
require separate skins for radio DJs.
On 05/27/2017 06:20 PM, Stéphane Lepin wrote:
Hi everyone,
I think a dedicated "carts-only" skin, with only samplers and
library
access, could be an interesting addition for radio people, as this
category of users would not be immediately interested by the
DJing decks
while looking for a cartwall software. I quickly tweaked
LateNight to
add more sampler decks, so I will try to make a draft
cartwall-only skin.
This is already possible with Deere by dragging the decks/library
splitter all the way to the top. We could add an option to the skin
settings menu to make it more obvious and add the same option to Tango.
Looking at Deere this way, I think the vertical order of the parts
of the skin might be a little odd for radio DJs: samplers, mic/aux
inputs, then library. Would it be better to put the mic/aux inputs
above the samplers? Maybe effects should go below both mics/aux and
samplers?
Idea: add a dedicated window for the cartwall/sampler decks.
This would
especially be useful for home radio studios, where radio DJs with
dual-monitor setups could use Mixxx's DJ decks (with or without
AutoDJ)
on one screen and put a large cartwall window on another screen.
It would be nice if we could have parts of the skin in a separate
window, but the skin system has no way to do this. It would be
pretty tricky to make this work well with the existing system. Refer
to the discussion on https://bugs.launchpad.net/mixxx/+bug/1152575
<https://bugs.launchpad.net/mixxx/+bug/1152575>
Kind regards,
Stéphane Lepin
2017-05-27 22:35 GMT+02:00 Daniel Schürmann <dasch...@mixxx.org
<mailto:dasch...@mixxx.org>
<mailto:dasch...@mixxx.org <mailto:dasch...@mixxx.org>>>:
Hi,
I have found a good reference for a card wall player I had
in mind:
https://www.youtube.com/watch?v=1JBaUZo51mg
<https://www.youtube.com/watch?v=1JBaUZo51mg>
<https://www.youtube.com/watch?v=1JBaUZo51mg
<https://www.youtube.com/watch?v=1JBaUZo51mg>>
I think it would be far more straight forward to start from the
scratch instead of putting this into Deere and Tango. On the
other
hand It will also work as a view setting for one of them:
"Radio mode"
Finally it is only the way to get to it. Switch skin vs.
Switch view
option. Remember that we had a lot more skins in Mixxx 1.1,
one for
every resolution.
> I don't think "instantly usable by default" is necessary,
as long as it is easy and obvious how to configure the skin
settings for a radio DJ use case.
Yes, that is the point. A new user should be instantly be
aware that
Mixxx has a radio mode, that's all.
> I suggest trying Tango and the updated Deere skins on your
netbook before deciding to put in the work to update Shade. If
there are some modifications we can make to those skins to work
better for netbooks, that would be a lot less work than updating
Shade.
Yes of cause, I will do this, this is already planed.
>> How about to save the yellowish into Deere?
>> This way we can argue, that we have merged Deere and
LateNight?
> Definitely not. The reason I started working on Deere was
because I like its color scheme.
Why not, you could keep the blue color schema and add a
yellow one.
The colour is just a matter of taste and it was considered as
beautiful when it was introduced. Sometimes a color can also
be an
eye-catching and characteristic design, even it is out of
fashion.
>> Also, there's another debate that is ignored but should
not, and has to do with loading times. It is known that Deere
takes nearly double the time than Latenight to load. On a fast
machine this is just a minor thing (if you're not relaunching
the application many times to test something), but on older
machines speed can be a decision to choose one over another.
>> I don't know if it is fully consequence of using SVG vs
PNG, or other reasons apply.
> That is an issue. I'm not sure why there is such a big
difference in load times. If rendering SVGs is the issue, we
could cache the rendered SVGs in the user settings folder the
first time a skin is loaded for faster startup times after that.
That way the vectors can be scaled appropriately for the screen
resolution and have faster startups.
The SVG rendering is one mayor time eater. The other are the
plenty
skin options, because all of them are instantiated in the
device memory.
Pre rendering the SVGs will help, but it will bypass the graphic
card rendering and scaling in Mac OS. Keeping a low end skin
is IMHO
more straight forward here and solves both issues.
Am 27.05.2017 um 18:29 schrieb Be:
On 05/27/2017 11:00 AM, Josep Maria Antolin wrote:
> Also, there's another debate that is ignored but
should not,
and has to
> do with loading times. It is known that Deere takes
nearly
double the
> time than Latenight to load. On a fast machine this
is just a
minor
> thing (if you're not relaunching the application many
times
to test
> something), but on older machines speed can be a
decision to
choose one
> over another.
> I don't know if it is fully consequence of using SVG
vs PNG,
or other
> reasons apply.
That is an issue. I'm not sure why there is such a big
difference in load times. If rendering SVGs is the issue, we
could cache the rendered SVGs in the user settings
folder the
first time a skin is loaded for faster startup times
after that.
That way the vectors can be scaled appropriately for the
screen
resolution and have faster startups.
On 05/27/2017 11:00 AM, Josep Maria Antolin wrote:
I am not too good at graphics, and haven't looked
much about
making
skins, so I'm not be best candidate to maintain the
skin,
althought
seeing that the other option is removing the skin, I
guess I
will have
to take some time and work the todo list that you
mentioned
above.
I guess we could remove some of the yellow parts
too, or at
least make
them color schemes.
I'm not too good at graphics either, but most of what
you need
is already there. It's mostly a matter of rearranging the UI
with the skin XML. There are a few new icons that will
need to
be made. Even if you aren't great at graphics you can make a
first draft for those icons while working on the skin
XML. Then
someone who has more graphic design skill can tweak the
icons.
Speaking of which, if anyone wants to improve the new
beatloop
and reloop icons in Deere 2.1, please contribute.
------------------------------------------------------------------------------
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
<mailto:Mixxx-devel@lists.sourceforge.net>
<mailto:Mixxx-devel@lists.sourceforge.net
<mailto:Mixxx-devel@lists.sourceforge.net>>
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
<https://lists.sourceforge.net/lists/listinfo/mixxx-devel>
<https://lists.sourceforge.net/lists/listinfo/mixxx-devel
<https://lists.sourceforge.net/lists/listinfo/mixxx-devel>>
------------------------------------------------------------------------------
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
<mailto:Mixxx-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
<https://lists.sourceforge.net/lists/listinfo/mixxx-devel>
------------------------------------------------------------------------------
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
<mailto:Mixxx-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
<https://lists.sourceforge.net/lists/listinfo/mixxx-devel>
------------------------------------------------------------------------------
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
