2 Midi Fighters won't work at the same time! :(

[Citizen_Insane]

Ok so here's the situation, I have a VCI 100, regular Midi Fighter and a Custom Midi Fighter. Using a Macbook Pro with Snow Leopard, Traktor Pro (haven't upgraded to 2 yet).
Regular MF is on Channel 3, Custom on Channel 4, so I know it's not a mapping conflict.
Now, regardless of my VCI 100 being plugged in or not, I can plug in either one of the MFs individually and it will work, no problems.
The problem comes when I plug both in. Whichever is plugged in second will not send to Traktor, although it will receive (the beat pulsing LED on the Custom still pulses with both plugged in). This happens regardless of which USB port I use, whether I use a USB hub or not.

I have a slight suspicion that Traktor might be picking up both MFs as being the same device as maybe they are recognized under the same name? But I have no idea how to change that. That's really my only guess about the problem... other than that I know both MFs are in full working order, just they don't want to play with each other

[HerbStrike]

you checked the in and out port list see if it see's two mf's

[Citizen_Insane]

you checked the in and out port list see if it see's two mf's

Yay! In out list sorted it. They were both under the same Midi Fighter listing... thanks

EDIT: Oh wait... trouble is still a brewin'

[HerbStrike]

thats usually the issue with conflicting device's glad i could be of service enjoy

[Citizen_Insane]

Hate to say this but I had it working for about 30 seconds... now Traktor refuses to pick up my original Midi Fighter as being plugged in AT ALL.
in port and out ports appear at "n/a:Midifighter"
My computer isn't even picking it up at a MIDI device anymore

[HerbStrike]

boooo check the connections you got it going through a hub? powered? try reinstalling your mapping, and changing the ports again?

[Citizen_Insane]

boooo check the connections you got it going through a hub? powered? try reinstalling your mapping, and changing the ports again?

Tried all of those... no dice. Gonna try re-flashing the firmware.

EDIT: Flashed to the latest firmware... original MF is working again... now to test with the other.

EDIT 2: And now the custom MF is doing what the original MF was doing... time to re-flash it too.... and it works again... I feel like I'm going in circles...

Pretty sure at this point it has to do with traktor recognizing them as the same device and not the in/out routing, I appear to have gotten things back to their original state of not working.

[djproben]

My solution to this problem is just a workaround and I haven't tried it in TSP2 yet because, well, I'm still having problems getting TSP2 working properly But what I do is kind of tedious -- when I open Traktor I open the controller manager and re-select each midifighter port on its own mapping each time. Then I try to remember to set them to n/a every time I shut traktor down. This step isn't necessary but it makes things easier if you remember it. Basically traktor is going to forget which midifighter is which during each restart due to the name being the same. Changing the name in Audio MIDI settings doesn't do jack about this.

However I also have been planning on another solution but I haven't had time to try it yet -- it's to recompile the firmware for one of the midifighters to change its name. I will work on this when I get the chance but it may not be for a week or two ... the discussion about it is here if anyone wants to try it out before I get to it -- http://www.djtechtools.com/forum/showthread.php?t=28214 -- and DJKeyWee refers to an MF sticky thread that will be helpful as well. I went through the source code and I'm pretty sure what I posted there is the right thing to change in order to get the midifighter to announce itself by a different name.

[Citizen_Insane]

@djproben: thanks for the quick reply to my PM. I'll test your work around, I don't have TP2 so for all we know the issue might be solved with the upgrade lol.

Unfortunately I lack the coding experience necessary for things such as messing about with the source code of the MF. Maybe we should just ask someone such as Midi Fidler, he's might know how Ean's got that stuff working.

EDIT: The workaround is working for me, very nice thinking there. Now I can actually use all of my controllers

[djproben]

@djproben: thanks for the quick reply to my PM. I'll test your work around, I don't have TP2 so for all we know the issue might be solved with the upgrade lol.

Unfortunately I lack the coding experience necessary for things such as messing about with the source code of the MF. Maybe we should just ask someone such as Midi Fidler, he's might know how Ean's got that stuff working.

EDIT: The workaround is working for me, very nice thinking there. Now I can actually use all of my controllers

Glad to hear it actually works! I'm pretty sure I can handle the source code recompile when I get the chance to mess with it so I'll try to make it a priority; I actually have 3 midifighters but have never used more than 2 at a time because of this problem and I don't even use 2 most of the time because I can't be arsed to mess with it. It's an annoying workaround because if you have a lot of controllers traktor is really slow opening the preferences; all said and done it adds about 5 minutes and a bunch of annoying clicky-clicks to Traktor setup. Doesnt seem like a lot but it gets old after a while, especially when you've got the sound guy waiting on you to play something so he can do his sound check and then go smoke a joint.

If I'm successful in recompiling I'll post the file!