On 1 May 2012, at 00:36, zestoi wrote:
> On 30 April 2012 06:02, Sean M. Pappalardo - D.J. Pegasus
> <spappala...@mixxx.org> wrote:
> As RJ said, that's an unintended-consequences bug that I need to examine more
> closely when I get back to my controller pile at home. (Still traveling at
> the moment.) I added that so the serial number would be stripped off of HID
> controllers but didn't realize others had spaces in their proper names, so I
> will devise a more intelligent way to remove the serial numbers and keep full
> controller names.
>
> for hid devices i've found that just matching on dev->product_string is
> enough. if someone has two controllers of the same type plugged in the 2nd
> instance just has to make sure it doesn't try to open a device that has
> already been opened. the serial number won't be part of that.
There is one quite important HID use case here: having 2-4 HID supporting decks
like Pioneer CDJ to control mixxx decks, most of the time these would be the
same device model.
In this use case, I think correct activation way would be to:
- activate devices by serial number automatically, if it has been activated
before
- write mappings javascript in a way you somehow tell from the deck which mixxx
deck it controls: Sean has mappings for stantons where you can see how this is
done.
Use case would be:
- connect 2 CDJs, mixxx sees the devices and activates both, without assigning
to deck
- user presses magic button on CDJs and maps both to decks
- one cable is disconnected, deck is deactivated from mixxx
- user reconnects cable, deck is detected by mixxx, but not assigned to any deck
- user presses magic button to map it again to correct deck
And yes, this is much better than automatically reassigning devices to same
deck it was previously assigned to, as long as the 'assign to deck' process is
logical and visible to the user.
This would require hot plug, which we don't yet have in HID but quite easy to
implement. Also, if the decks were used for sound output, things get
interesting, it should also work but it's separate topic.
Another question discussed on IRC was if devices known by vendor / product
should be activated automatically with correct mapping even when connected for
the first time. The mapping should map device to controls but not to specific
deck. If there are multiple matching mappings it can't be done of course: maybe
a dialog asking which one to load and remembering the choice?
The 'map this controller to this mixxx deck' method should be same for all
mixxx controllers, with known UI glue how it's done, and preferably, if LED
control of deck is available, blinking the 'map with this button' LED on
controller until deck is assigned.
If all devices use same method to map to a deck, it can be properly documented
and visual hints given in UI.
Just some ideas :)
*hile*
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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
