This is the part people trip on, so we'll go slow and you'll be fine. The
Titan Two sits between your controller and your console
and makes the console believe it's talking to a normal pad. Wire it up once,
and it just works every time after.
The basics, once
Three things are true on every console. Read them once here; the per-console steps below only cover what's different.
1. Four ports - which is which
Getting the ports right is 90% of a smooth first connect. The Titan Two has four:
OUTPUTGoes to the console. This is what makes the Titan appear as a controller (and it draws power from the console).
INPUT-AYour own controller - the one you actually play on. Highest priority.
INPUT-BThe authentication controller (more on that next). Also where headset / chatpad features come from.
PROGGoes to your PC for one-time setup in Gtuner IV. Never used during play.
No USB hub needed or supported - each controller gets its own port.
2. Why you need a second controller
Modern consoles refuse to be driven by a pad they don't recognize. The Titan can't fake that handshake on
its own, so you plug a genuine controller into INPUT-B purely to pass the console's
authentication check. You still play on the controller in INPUT-A - the one in B just sits there and
vouches for you.
The one difference worth remembering: PlayStation needs that controller plugged in the whole
time, while Xbox only needs it at power-on, after which you can unplug it.
3. One-time PC setup (the Output Protocol)
Once, before any of this: connect PROG → your PC, open ConsoleTuner's
Gtuner IV, and set the Output Protocol. Automatic
works for most people; if a console won't authenticate, set its specific protocol instead (listed per
console below). This is the only time the Titan touches a PC.
Now pick your console
The fussy one
Straight talk: PS5 is the hard one. Sony locks it down tightly, and ConsoleTuner
officially calls PS5 support "experimental." If something here fights you, it isn't
you - it's the platform. Here's the path that actually holds up.
What you need
The reliable route uses ConsoleTuner's P5 General adapter in INPUT-B
as the authenticator. The counterintuitive part most people get wrong:
a real DualSense or DualShock 4 will not authenticate PS5 games - Sony rejects
them through an adapter. The P5 General exists specifically to solve that.
Without it, the Titan falls back to "auth-reset" mode: it works, but briefly disconnects for about a
second roughly every 7.5 minutes verifying. Fine for a quick session, not great for a long one.
OUTPUT→ a USB port on the PS5
INPUT-A→ your controller
INPUT-B→ the P5 General adapter
Set it up
Output Protocol: USB PlayStation 5
On your PC once: open Gtuner IV, set Output Protocol to USB PlayStation 5, save, disconnect. (Read the firmware note below before updating anything.)
Plug OUTPUT into the PS5, then the P5 General into INPUT-B and wait for its port LED to go solid green.
Plug your controller into INPUT-A, then power on the PS5.
On the PS5: Settings → Accessories → Controllers → Communication Method → Use USB Cable.
The catch
Some games demand a genuine DualSense and reject any adapter outright - no setting fixes it. The escape hatch is PS Remote Play through a PC, which sidesteps the check.
Do not blindly "update to latest." Some Titan firmware versions break PS5 auth verifying. Check the current known-good firmware before you update.
If it goes wrong
OUTPUT LED is red, or you see an "A/U" error
Confirm the Output Protocol actually saved; suspect a bad firmware combo; power-cycle the whole chain (unplug every USB for ~10 seconds, then replug).
~1-second disconnect every few minutes
Expected if you're running without an auth adapter. Add a P5 General to make it continuous.
The game ignores your controller
Switch that title to PS4-compatibility mode, or use Remote Play. A few native games simply won't accept an adapter.
The easy one
PS4 is the stable, well-trodden path. One genuine controller for auth, and you're set.
What you need
A genuine DualShock 4, wired into INPUT-B and left there
for the whole session - that's your authenticator. Use a real data cable
(charge-only cables silently fail), and plug OUTPUT straight into the PS4, not through a hub.
OUTPUT→ a USB port on the PS4 (direct)
INPUT-A→ your controller
INPUT-B→ a genuine DualShock 4 (stays plugged in)
Set it up
Output Protocol: USB Automatic or USB PlayStation 4
On the PS4 once: Settings → Devices → Controllers → Communication Method → Use USB Cable.
Plug the DualShock 4 into INPUT-B and your controller into INPUT-A.
Plug OUTPUT straight into a PS4 USB port.
Wake the PS4 - it authenticates within a couple of seconds. Leave the DS4 in B for the whole session.
The catch
The DualShock 4 has to stay in INPUT-B. Leave it in and you'll get zero disconnects; pull it out and the link dies after roughly 8-10 minutes.
If it goes wrong
Disconnects every few minutes
The auth DualShock 4 isn't in INPUT-B, or fell out. Keep a genuine DS4 wired into B the whole time.
Nothing detected at all
The PS4 isn't set to wired comms: Settings → Devices → Controllers → Communication Method → Use USB Cable.
Random dropouts / resets
Usually a charge-only cable or a USB hub/extension. Use a known-good data cable straight into the console.
Covers Series X|S and Xbox One
Xbox is friendlier than PlayStation in one big way: the auth controller only has to be plugged
in when you power on. After the handshake clears, you can unplug it.
What you need
A genuine Xbox controller (Series 1914, Xbox One 1708, or an Elite) wired into
INPUT-B for the power-on handshake. Update the Titan's firmware
first - it's required for Series consoles. Use a real data cable.
OUTPUT→ a USB port on the Xbox
INPUT-A→ your controller
INPUT-B→ a genuine Xbox pad (only needed at power-on)
Set it up
Output Protocol: USB Xbox Series X|S or USB Xbox One
On your PC once: update the Titan firmware in Gtuner IV and set the matching Xbox Output Protocol.
Plug your controller into INPUT-A and a genuine Xbox pad into INPUT-B.
Plug OUTPUT into the Xbox, then power on using the console's power button (more reliable than the controller's).
Wait for the AU indicator to clear and the port LED to turn green - re-seat the genuine pad if AU sticks.
Once it's authenticated, you can unplug the INPUT-B pad - unless you want headset / chat audio, which routes through it.
The catch
The AU prompt comes back every cold boot. Just re-seat the genuine Xbox pad for a second to clear it, then unplug again.
No third-party pad is confirmed to authenticate an Xbox Series X|Sverifying. Use a genuine Microsoft pad to be safe. (Tip: an Xbox One pad on the USB Xbox One protocol can authenticate a Series console if the Series path acts up.)
If it goes wrong
"AU" after plugging in or power-cycling
Briefly plug in a genuine Xbox pad to clear it - then it's removable again.
Xbox doesn't recognize the Titan
Set the explicit protocol (USB Xbox Series X|S or USB Xbox One) and update the Titan firmware + Gtuner.
A wireless auth pad keeps dropping
Use a wired pad and a good data cable, charge it fully, and power on via the console button.
"Your Controller Needs an Update" loop (Series)
Update the genuine controller's firmware while it's connected through the Titan, then retry.