Page 3 of 3

Re: MIDI mapping for android

PostPosted: 15 Aug 2019, 19:11
by Mihai Pinciu
Any news about any update on the mappings?

Re: MIDI mapping for android

PostPosted: 03 Sep 2019, 12:59
by rmartin
This is my result

IMG_20190816_221329.jpg


I don't understand why controller name is Studio 4a and not CMD Studio 4a. I try also to rename making file but nothing

Any idea?

Tnks Fabio

Re: MIDI mapping for android

PostPosted: 11 Sep 2019, 10:03
by Mihai Pinciu
Still waiting for a response Team@Mixvibes

Re: MIDI mapping for android

PostPosted: 16 Sep 2019, 15:53
by rmartin
Hi please any one of the developer team can reply
thanks
Fabio

Re: MIDI mapping for android

PostPosted: 27 Dec 2019, 13:33
by rmartin
Hi is there some one Mixvibe can reply?
Fabio

Re: MIDI mapping for android

PostPosted: 01 Jan 2020, 23:05
by DaybreakDog
I'm looking to get a Numark DJ2GO2 and use it with Cross DJ on my android device. It looks like the hack posted on page 1 MAY work but I'm kind of wary about sinking money into a controller only for it to be able to do everything except exactly what I bought it for.

Re: MIDI mapping for android

PostPosted: 24 Jan 2020, 01:00
by samymn
Hi guys!

I just managed to get my Hercules Universal DJ controller working with my Android tablet (OTG) and want to share my experience.
My first step was to follow the instructions from the tutorial and get the mapping file from the PC version of Cross DJ.
When I copied it to the mapping folder of the Android app it didn't work at first and I was getting the "Not compatible" message.
When I tried a second time, I found out that I had to change the "id" field inside the file to make it work.
How to get it correctly was the interesting part:
1. Just plug the controller to a PC and find the USB Vendor and Product IDs. There are many ways to find it out. I just used lsusb from a Linux machine. They are normally shown as a four digit hexadecimal code.
2. Concatenate the 2 IDs in hex code (VendorId and ProductId) and convert the 8 digit result to decimal. That's the number you put on the mapping file as <id ID=""\>.

I also changed the fields PCDevice and MACDevice to exactly match the controller name from the error message, but I don't know if that affects anything.
After these changes, the controller was identified and worked automatically any time I plugged it in.

Cheers!

Re: MIDI mapping for android

PostPosted: 06 Feb 2020, 16:13
by HOnIquaD
I also feel that this feature should be added by the team asap. Looking forward to some other working way for MIDI mapping on android. Is it possible?