Inhardware terms, the DJ2GO 2 is actually quite nice and good for the price with a built in twin stereo channel sound card (stereo main and stereo headphones) but very limited with Serato DJ Intro. It would be great with Mixxx so I hope someone can point me in the right direction.
Hi, did you get this to work in the end? I am in ths same situation as you where I would prefer to use Mixxx with my, soon to arrive, dj2go2. However, I do not have a clue about mapping and XML files etc. I was hoping mixxx will let me control the jog wheels like real turntable platters where I can rewind as if rewinding real vinyl?
Great, thanks for sharing! It would be nice if we could get a complete mapping for the DJ2GO2 included in Mixxx 2.1. Please read the Contributing Mappings wiki page for details on how to submit your mapping for inclusion in Mixxx. Note that we have been very busy getting 2.1 beta and the build server ready so there is currently quite a backlog of controller mappings to review. It may be a while (as in a few weeks or maybe a month or so) before I have time to thoroughly review a mapping for the DJ2GO2, but I am confident we can get it done by the 2.1 final release at the end of March 2018.
So I picked up one of these and have used this mapping in Mixxx as a jumping-off point (I use mine for music and sound effects when I am public-address announcing, so I have some slightly different ways of using the controls than a DJ would.)
For the most part all of the actual functionality I want is either already written in the .js file or can easily be remapped in the MIDI learner. So what I would like to do is dig in and figure out how to make the lights on the sample pads work. (An advanced feature I would like would be to remap the Sync button (again, for my purposes, something I would never use) as a Shift button, but my gut is that that is WAY advanced math.) Problem is that I have no idea what the addressing is for them is.
Simply replacing engine.connectControl with engine.makeConnection does not work in that case because the script uses the hacky old behavior of engine.connectControl evaluating a string as a snippet of JavaScript code instead of taking an actual JS function as an argument. engine.makeConnection should work just by removing the quotes around the function names.
3a8082e126