Multiple identical midi hardware mapping (UM-ONE) and applying Traktor S4mk2 mapping on iPhone.

Hi.

I found about Djay few days ago and been enjoying it since on my iPhone 13. Unfortunately either my Traktor Z1 or S4mk2 cannot be used with Djay as the midi mode cannot be activated without the drivers.

I managed to route the signal through my pc to Roland UM-ONE commected to my iPhone and everything is working great. Before I go through the trouble to map the device manually I thought about trying to add the existing mapping as I happen to have the same exact device.

This is where I found the mapping:
https://maps.djtechtools.com/mappings/8031

The file opens up automatically on my iPhone but no mapping seems to appear when I connect the S4 (the device is listed even though midi mode cannot be invoked). So I then tried to apply the mapping for the UM-ONE by changing the file name with no results.

I’m thinking there might be some differences in the syntax of the file as it’s originally made for pc version of the Djay Pro 2. Also I found another topic on this matter (Official support for Traktor S4 MK2) where it is suggested that you rename the file with the newest version of Djay. This seems to support my theory on the file format.

Mapping the S4 is not too big of a trouble but this would save me a lot of time as I’m not fully sure of all the possible combinations on S4.

Going through this I realized that Djay seems to handle only one mapping for every device type. I’m afraid this is coded through device name instead of device ID. This is why the files normally work when you download one and install it.

However what if we have multiple identical devices like two UM-ONEs? Same applies for other midi interfaces and to a device that has multiple ports. It seems there is no way to dofferentiate these instances?

I assume no matter what UM-ONE I connect it uses the same mappings. Of course this is not ideal at the least and most cases the two devices contradict and cannot be added to the same mapping file.

How would I overcome this problem? Other than buying different midi interfaces for every single device.

It seems there is a possibility to replicate the mapping and this creates another instance of a mapping for one device. When choosing a device this mapping can be change. I don’t it will remember what mapping to use though. This seems to allow using identical devices at the same time but as I don’t have two identical devices I cannot test it.

Is this right and how the Djay differentiates the devices? By device name?

I will now look into the mapping file and see if I can get it to work. All help still appriciated.

EDIT: I tried to delete one of the premade mapping instances and then renaming the downloaded instance with the same name. This made it disappear from the listing as the software probably cannot compile it.

Ok here we go. So it seems the syntax has been updated and the USB ID has been implemented since the Djay Pro 2. Good job.

USBID
305463783

This would mean that different identical devices are indeed listed separately when connected.

Unfortunately the syntax has changed also… This means if you don’t have a wrapper program to translate the syntax from older file format to the newer one I’m out of luck.

I could try to translate the file with the help of AI and written API but it really is more trouble than it’s worth.

There is also the fact that my Traktor is a second hand device and might have custom controls made up in controller editor. This would mean the script wouldn’t necessarily work. I think I should be able to reset it and indeed I should before creating the mappings of my own. This would make it possible to share the mappings.

I’ll wait for some replies before doing so. All information and documentation provided would help. I have other projects also and it would be neat and helpful to see how it’s working under the hood.

All this said the current version of the Djay is awesome (withour prior experience) and the mapping process is super simple and very intuitive. I have had a great fun creating a mappings of my own for Novation Launch.