Record a Titan Two GMK macro in Gtuner IV

Set up a repeatable recording

Connect Titan Two over PROG and open Device Monitor. Confirm the intended controller output before recording. If an existing slot changes those controls, either unload it for a clean recording or deliberately keep it active and note that the recorded sequence includes its effects. This helps explain why playback later differs from a description of the physical buttons you pressed.

Start from a stable screen, such as an offline menu, and decide exactly when the recording should begin and end. Avoid extra movement and release the last button before stopping. A shorter timeline is easier to inspect and helps reveal where a pause or unexpected input was captured.

Save the recording and inspect what it contains

Use the recorder controls to capture the sequence and save the result as a GMK file. Keep an untouched copy before editing. The manufacturer’s changelog documents filters for saving selected input groups and later support for recording paddle state. If a control is missing from the result, check whether it was visible in Device Monitor and included in the recording.

Open the saved file in Macro Editor and check the first and last events. Make sure the timeline shows a return to neutral where you expect it. A sequence that never releases its last control is a different recording from one that ends with an intentional pause.

Test playback from the same state

Use the playback method appropriate to your setup and consult the hardware guide for macro storage. Start from the same screen and controller state as the recording. A fixed timeline cannot by itself account for a menu starting one page later or for a prompt that appears at a different moment.