Behringer CMD PL1 tsi

[Da3dalus]

As long as MIDI for each unit is routed to corresponding .tsi you should be good. They can conflict each other only in case when both mappings are set to 'all ports' and under condition that both units are sending MIDI in the same channel with duplicate note and CC.

Did you try to plug it to some other cable/computer?

Yea I tried another cable, no difference.

I would try it on another computer but I need to to work on my own one.

when I plug it rusn through its little LED light show that tells you its connected, but then it just stays orange and no response from the pads, jog or encoders.

So annoying and I have a party thursday

[Stewe]

I have suggested trying another computer just to locate if issue comes with your system or the actual unit. Do you run windows?

[nem0nic]

As long as MIDI for each unit is routed to corresponding .tsi you should be good. They can conflict each other only in case when both mappings are set to 'all ports' and under condition that both units are sending MIDI in the same channel with duplicate note and CC.

This is not 100% true. Traktor has problems with having several TSIs loaded, even if they're not being used (no hardware device associated). It can not only cause problems with messaging, but it can also cause the Controller Manager to hang (especially on initial opening and device selection). It's always a good idea to only load the TSIs you have active hardware for.

OP, update to 2.6.2 or higher. Why are you still running a version that's now over a year old?

[Stewe]

This is not 100% true. Traktor has problems with having several TSIs loaded, even if they're not being used (no hardware device associated). It can not only cause problems with messaging, but it can also cause the Controller Manager to hang (especially on initial opening and device selection). It's always a good idea to only load the TSIs you have active hardware for.

OP, update to 2.6.2 or higher. Why are you still running a version that's now over a year old?

I have four controllers each loaded with an ultimate mapping (20+ devices) running with out any conflicts and never experienced any issues of that type. The loading part is loooong but that's only issue with numerous devices.

[nem0nic]

I have four controllers each loaded with an ultimate mapping (20+ devices) running with out any conflicts and never experienced any issues of that type. The loading part is loooong but that's only issue with numerous devices.

We've seen instances where it is indeed an issue. This has been corroborated by the service departments at multiple companies, as well as personally (when examining a similar issue on a colleague's computer).

Also from a troubleshooting perspective, this process simplifies the possible elements in play. The first step in any troubleshooting process is to reduce the environment to it's simplest form. It takes seconds, costs nothing, and can be reversed easily if desired.

With all due respect, this should be one of the first steps a user takes if there is a problem with an attached MIDI device.

[Da3dalus]

This is not 100% true. Traktor has problems with having several TSIs loaded, even if they're not being used (no hardware device associated). It can not only cause problems with messaging, but it can also cause the Controller Manager to hang (especially on initial opening and device selection). It's always a good idea to only load the TSIs you have active hardware for.

OP, update to 2.6.2 or higher. Why are you still running a version that's now over a year old?

Stewe Ill try it on another computer and get back to you.

Yea I updated to 2.6.2, still no joy. So annoyed...

Just never bothered to update.

Thanks for helping out guys.

[Stewe]

Da3dalus,

Do you have any sort of MIDI editor software, virtual midi cables and such running in background before opening Traktor?

[nem0nic]

You might also want to verify proper operation in another application. You could try Deckadance, or you could download MIDIOX for free and look at the raw data.

You may also want to contact Behringer support and have them walk you through some fixes if you're not comfortable on your own.