Midi mapping bug.
Midi mapping bug. Posted on: 16.06.2012 by Vernon Positano I've started a mapping on a midi controller using traktor pro v1.xx and just ported it over to v2.5 to find that all the 'effect select' mappings are now bringing up the wrong effects in v2.5. The only one thats working as expected is 'delay', which I'm guessing is because its at the top of the list of effects in both versions.Is this a known issue.. any info on how to resolve this, without remapping the effects again ? | |
| Vernon Positano 17.06.2012 |
Originally Posted by space monkey
Yeah, after I posted, I realised what it was and imported my old effects settings which fixed it. I could then add the new effects and it was fine. Seems like the mapping is based on an index number for the effects, rather than its name, and that might be different depending on what effects you have active. That seems like pretty shoddy coding tbh. |
| Vernon Positano 16.06.2012 | I've started a mapping on a midi controller using traktor pro v1.xx and just ported it over to v2.5 to find that all the 'effect select' mappings are now bringing up the wrong effects in v2.5. The only one thats working as expected is 'delay', which I'm guessing is because its at the top of the list of effects in both versions. Is this a known issue.. any info on how to resolve this, without remapping the effects again ? |
| Vernon Positano 17.06.2012 |
Originally Posted by space monkey
Yeah, after I posted, I realised what it was and imported my old effects settings which fixed it. I could then add the new effects and it was fine. Seems like the mapping is based on an index number for the effects, rather than its name, and that might be different depending on what effects you have active. That seems like pretty shoddy coding tbh. |
| Branden Wentler 17.06.2012 | Yeah, the addition of new fx in 2.x throws off the maps. You can either edit your mapping or disable the new fx. |
<< Back to Reviews of DJ equipment Reply