Midi mapping bug.
Results 1 to 3 of 3
  1. #1

    Default Midi mapping bug.

    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 ?
    www.djmoonie.co.uk
    The Left for dead show
    (GMT+0) Tuesdays Midnight til 1.30am, on www.phonic.fm,
    or 106.8fm in the south west of england.
    For private bookings, please use www.djmoonie.com

  2. #2
    Tech Guru space monkey's Avatar
    Join Date
    Mar 2009
    Location
    back home
    Posts
    1,174

    Default

    Yeah, the addition of new fx in 2.x throws off the maps. You can either edit your mapping or disable the new fx.

  3. #3

    Default

    Quote Originally Posted by space monkey View Post
    Yeah, the addition of new fx in 2.x throws off the maps. You can either edit your mapping or disable the new fx.

    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.
    www.djmoonie.co.uk
    The Left for dead show
    (GMT+0) Tuesdays Midnight til 1.30am, on www.phonic.fm,
    or 106.8fm in the south west of england.
    For private bookings, please use www.djmoonie.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •