Identify which parts of the profile matter
A translator can contain controller remapping, keyboard or mouse mappings, and mouse-to-stick conversion settings. Pick the part that matches the behavior you want to change. A key that triggers the wrong action is a mapping issue. A mouse that turns differently at slow and fast movement is usually a conversion issue. Those are different settings even if they share the same file.
Keep a copy of an imported GIT before editing. Some entries may assume a particular game layout, a sensitivity setting or a specific controller. Write down those assumptions so you can compare the edited file with the conditions the original author used.
Install it with the intended slot and inputs
Program the translator on a spare slot and select that slot. Gtuner IV can load an Input Translator with a script or Gamepack and can restrict controller remapping to specific inputs. If your configuration uses more than one controller, test each independently before connecting everything together.
If the mapping looks correct in the editor but changes a different device, inspect which ports are included by the profile. If both translator and script are installed, temporarily test the translator alone to learn which part changes the final output.
Change the conversion one control at a time
Use the same local camera movement to compare a baseline with one new conversion setting. Repeat slow and fast movements and note where the result diverges. Changing several values together can make a profile feel different without explaining whether the deadzone, sensitivity or curve caused it.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.