Hello there. On 01/21/2014 11:18 AM, Neale Pickett wrote: > When I was first writing this driver, you guys (probably Pegasus) > encouraged me to make it its own type of driver and not piggyback on the > MIDI driver. But now that a second device (2 out of 2) is known to send > MIDI, it would actually be a significant reduction in lines of code if I > went back to providing a driver that made these two use the MIDI code.
I'm not quite clear on how everything is interacting here. When you say "driver," I'm thinking Linux kernel (or user-space) driver. Can you knock up a quick block diagram? How does this relate to the usb-bulk framework work you did over a year ago that's in v1.11? > The Steel actually has a second mode that sends HID messages. I haven't > played with this one much since it was so easy to do the MIDI. You might want to look at using that. Sometimes more features and/or higher resolution is available using HID compared to MIDI on some controllers. Plus it should work without having to make any code changes. > So, what say you? Can I retool the "bulk" code to be a shim in front of > the MIDI code? Is it maybe too close to 1.12 for this kind of change? I can answer this better once I understand the above, though RJ has the final word. Sincerely, Sean M. Pappalardo "D.J. Pegasus" Mixxx Developer - Controller Specialist ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ 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
