I know this is discussed very often but I can’t find the ‘helping’ answer in the wiki or forum.
I connected a USB gamepad (prepared for faderstart), but in the config of mAirList I can only see that the gamepad is connected but not any possibility to configure it. The 2 lines (for the button-in and out selection) are light-gray and not selectable.
Do I need a script to activate the gamepad? Nothing else is connected to a USB port. The gamepad works fine in Windows (button 7)… We’re using the latest mAirList version. (2.1.26)
I use a gampad myself (mine is a Logic3 ten-button one), so I suggest you try the following troubleshooting, in the order below:
Open Settings, Control Panel, Game Controllers. Is your device listed there? If your device is not listed in this dialog, mAirList cannot ‘see’ it either. If not, I strongly suggest you use the Add New Hardware Wizard to install it, not the seductive-looking Add… button in the dialog; the latter has not always worked IME.
Once your device appears in the Game Controllers list, select (highlight) it in the list, then click Properties and use the test dialog to make sure that the pad’s button presses are being ‘seen’ by Windows as well.
Close Game Controllers and open mAirList Configuration. Expand Remote Control, then you should be able to assign actions/commands to the (non-greyed-out) buttons which you can now select in the top dropdown.
Remember that if/when you move the gamepad ‘interface’ to another PC (and sometimes if you move it to a different USB socket on the same PC!) you will have to do the button configuration again because it is now a ‘different’ device, referred to internally by Windows using a different GUID.
I hope this helps. Please post again (with details) if you have problems in the Game Controllers part of this.
1) Open Settings, Control Panel, Game Controllers. Is your device listed there? If your device is not listed in this dialog, mAirList cannot 'see' it either. If not, I [b]strongly[/b] suggest you use the Add New Hardware Wizard to install it, [b]not[/b] the seductive-looking Add… button in the dialog; the latter has not always worked IME.
The device is listed, but I installed in manual again as U suggested. Still the same problem.
2) Once your device appears in the Game Controllers list, select (highlight) it in the list, then click Properties and use the test dialog to make sure that the pad's button presses are being 'seen' by Windows as well.
The LED 7 goes 'ON' when I make a interconnect on button 7. Sow Windows does see the gamepad.
3) Close Game Controllers and open mAirList Configuration. Expand Remote Control, then you should be able to assign actions/commands to the (non-greyed-out) buttons which you can now select in the top dropdown.
[img]http://centani.nl/images/gamepad.png[/img]
Nothing changed, nothing to select here
4) Remember that if/when you move the gamepad 'interface' to another PC (and sometimes if you move it to a different USB socket on the [i]same[/i] PC!) you [b]will[/b] have to do the button configuration again because it is now a 'different' device, referred to internally by Windows using a different GUID.
I understand but on this PC (and in the studio) I used only one, and the same, USB port for the gamepad.
Maybe the gamepad isn’t working correct. I don’t have an other one to try. There is alwas PLAN B. I can always use the ‘old’ gameport :lol:
Not related to this problem yet, since Vincent hasn’t got his gamepad working, but for anyone else going the USB gamepad route, note that the polarity of connections between the desk and the gamepad DOES matter!
We used the gamepad test dialog (in Properties as explained above) and discovered that the connection only worked one way round. (Which makes sense: as my colleague said at the time ‘… it is a circuit, after all!’)
So if when you do get things going, it still doesn’t seem to work: try swapping the polarity of the connections from the desk to the gamepad.
Cad,
Yes - the polarity is important if you’re using a desk that has opto-coupled remotes. Also, it should also matter if the buttons are a direct connection (like a Behringer DX1000) - because the ground of the connector is conducting via the chassis, so the + signal will be grounded anyway
Today I found on a fancy fair an other USB gamepad (Thrustmaster, as used in the manual but with 12 knobs) but I got still the same problem. In Windows it is working fine.
I also found an older gamepad for the ‘good old’ gameport but I need to test this in the studio (don’t have any gameport on my home computers…).
Today we have an public holiday in Holland so I can’t go into the studio now.
Tonight I tried the 2 gamepad’s on the studio computer. Still with the same problem as described. In WindowsXP PRO SP2 the gamepad’s are working correct… but not with mAirList.
Am I the only one with this problem? I don’t think it has something to do with the polarity of connections because CAD and Charlie Davy, an original gamepad does have the same… and our D&R AirMate has reed contacts.
It must be a software issue. Windows does recognize the Gamepad (you see it in Control Panel, and it appears attached), but mAirList does not; or at least it is not able to determine the number of buttons.
I will prepare a small program which dumps information about all attached joysticks.
