On 11/22/17 01:24, Sean M. Pappalardo - D.J. Pegasus wrote:
That /would/ be very handy in allowing users up the expertise chain (so
to speak) troubleshoot/develop mappings with the hardware owners. The
only thing I would suggest to make that process work well is to create a
bonehead-easy way for a very non-technical user to create a virtual
representation of their controller. (I'm thinking a GUI with a wizard
that walks them through the process, automating as much as possible.
Like have them take a photo of the device with their cell phone or Web
cam, then try to auto-identify controls in the image so the user needs
only edit their properties and move them around a bit instead of having
to create them all manually.) That also lessens the responsibility for
you and the OpenAV team to have to create virtual devices yourselves
from every controller ever made.
Photo recognition is way to complicated in my opinion.
More something like qt designer/glade designer etc but for ctrla would
fill the gap nicely. There are only a handful of input element types in
existence. Knobs, sliders, touchpads etc. You could have a designer with
all supported elements. You place them, give them names, sometimes extra
flags. And it outputs a format that ctrl understands.
On midi devices at least, the mapping could then be automated with a
wizard then. On HID devices things will get more tricky, but at least a
large part of work could be done through this by non technical people.
it
hopes to allow accessing HD screens on
all Ctlra supported devices, and get tight integration to the next level.
That sounds good on the surface, but wouldn't that then restrict the
ability of applications to style the information on the screens to a set
of pre-defined designs/layouts Ctrla supplies? I imagine a DJ
application like Mixxx will want to use the screens quite differently
than an audio editing application like Audacity or a DAW like Ardour.
I guess the API is just some sort of Framebuffer, where you can draw
whatever you want on it.
I kinda had some wishes like this as well, like auxiliary displays. Part
of the current skin subsystem, but on the other hand, in this case it's
more controller dependent. I think we will be more flexible with some
sort of second skin instance for each device.
kind regards
poelzi
------------------------------------------------------------------------------
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
