Hi Andreas,
I'm the guy who does RMX mappings, I also let the RMX break... You'll have
to appreciate that as (up until now) the ONLY developer who builds Mixxx and
uses it with an RMX, there has not been a lot of demand for me to keep up
with the new format changes as they occur in HEAD -- there have been quite a
few changes to the format since 1.6.1. I have also been in no real hurry
to fix those mappings until the core of Mixxx settled down changes-wise and
got into a state were people started discussing betas and release
candidates.
I'm not going to comment on the shortcomings of Mixxx under the hood, all of
the developers are aware of them and we've discussed them at great
lengths. I think we've largely taken an extend and replace approach, we
try to extend the good and replace the bad; at the same time we want to
continue to release and improve software. Releasing software is how we
grow our community of users and developers. Growing the developer base is
how we get more hands and heads to help us replace the bad with something
better.
>From an outsiders perspective, I can appreciate that Mixxx's development is
not very easy to follow... But it's also been mentioned that where the
documentation falls short we make ourselves available via this ML and IRC
and try to help those who are stuck.
With respect to the debate over version numbers, even if 1.7 lost the Wizard
for learning which seems to be taking so much unwarranted fire, it would
STILL be a big milestone for Mixxx... From the users perspective the
ability to edit mappings inside Mixxx is a big feature and the ability to
create scripted behaviours for controls (even if you have to open up a file
in a text editor to do it) is HUGE. This doesn't even touch on the
rewriting and internal clean up work that's gone on since 1.6.1.
Scriptable controls allows Mixxx to not only control dynamic stateful
controllers like the SCS.3d, which would simply not usable in Mixxx 1.6.1,
it also allows us to finally start to support controllers that have
re-mappable behaviours.
To give you a sense of how this will help the RMX specifically, scripting
will make it possible to have different jog wheel modes using the scratch
button (as it was originally intended to be used), it will also be possible
to hold the down or up button and rapidly scroll through songs using the
jogs... Users will be able to create scripts to do stuff on buttons
3-6... All of these things are done via script and wouldn't be possible in
1.6.1; scripting makes Mixxx hackable to anyone with notepad and the will to
learn a little JavaScript.
If you have questions specifically related to the RMX you are welcome to bug
me and of course we always are happy to look at patches people send our way.
Cheers,
-G
__
--- == __/ t.O ==--
http://stacktrace.org/
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
