Test the headset on the intended controller
Start with the headset plugged into the same controller you intend to use for audio, connected directly to the console. Check playback and microphone input separately in the console settings. Once both work, move that controller and headset into the Titan Two setup and keep the other audio settings unchanged for a fair comparison.
If the audio already fails in the direct setup, inspect the headset plug, microphone mute and console device assignment before adding the adapter. Otherwise you may be diagnosing a problem that has nothing to do with passthrough.
Check the documented passthrough combination
ConsoleTuner describes audio and other controller-specific features as available on compatible passthrough connections. The detailed PlayStation 4 guide lists headset and speaker support with a DualShock 4 V2. Xbox controller audio also depends on the controller and connection route. Keep the specific audio-capable controller attached while testing and check the guide for that host and protocol.
Bluetooth input, a USB wireless receiver and a wired controller can all deliver button input while exposing different audio features. Verify the particular headset route instead of assuming that all three behave the same way.
Separate audio failures from input failures
With a clean profile, check controller navigation and then repeat the playback and microphone tests. If only one audio direction fails, note which one and whether another controller was connected. ConsoleTuner’s firmware history includes fixes for specific headset and multi-controller combinations, so the adapter firmware and connection order are relevant diagnostic details.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.