Quick answers to common MatchPatch questions.
MatchPatch mainly changes output block levels so presets and snapshots land closer to the target loudness.
If you manually edit names or gain values in the table, those edits can also be saved.
See Reading Results.
MatchPatch is meant to balance level, not redesign your tone.
It changes output level rather than amp, cab, drive, or effect settings. Still, always listen after importing the adjusted file, because level changes can affect how a sound feels in the mix.
The safest undo is your backup.
Keep the original .hls, .hlx, .pgs, or .pgp file, and use Save As when
possible. If you do not like the adjusted file, import the original backup
again.
Yes. Use loopback or simulated mode to learn the app without hardware.
Those modes are useful for practice, but they do not measure your real processor tones.
Loopback mode measures the reference DI directly. It is a safe way to test the MatchPatch workflow without connecting a processor.
Do not use loopback results as final live preset levels.
See Backends.
Simulated mode pretends to be a processor. It is useful for testing the workflow without hardware while seeing more varied fake results than loopback.
It is not a real processor measurement.
Use hardware mode when you want real results for rehearsal or stage use.
Hardware mode measures the actual Helix or Pod Go sound.
See Hardware Measurement.
MatchPatch needs the same performance through every preset so the comparison is fair.
The DI should match your playing style. A metal rhythm DI and a clean ambient DI can lead to different balancing decisions.
See Reference DI.
Use a clean DI that represents the music you are balancing.
For rock, include palm mutes, chords, and lead notes. For clean or ambient music, include ringing chords and softer playing.
Use the default first.
Change target LUFS only when you have a musical reason or a repeatable band setup that needs a different level.
See LUFS And Loudness.
Solos often need to sit above rhythm parts. MatchPatch can add a solo boost to snapshots it recognizes as solos.
See Snapshots, Solos, And Ignored Snapshots.
It looks at the snapshot name. By default, names containing solo are treated as
solo snapshots and marked with a star.
Clear snapshot names help.
Grey snapshots are ignored. MatchPatch skips them and does not adjust them.
This is useful for unused snapshots or placeholders.
A red cell means MatchPatch could not safely calculate a normal adjustment.
Common causes are silence, wrong routing, missing loudness data, or an output level that would go outside the processor range.
See Troubleshooting.
A measurement file is a temporary processor file made so MatchPatch can measure the processor correctly.
It is not the final file for playing.
See Measurement And Adjusted Files.
No.
Warning: Measurement files are for measurement only. Use the adjusted file for playing.
A single .hlx or .pgp preset does not know where it lives on the processor.
MatchPatch needs a temporary slot, such as 12A, so it can switch to the right
location during measurement.
See Normalize A Single Preset.
Yes. Use File > Open and select only .hlx files for Helix or only .pgp files
for Pod Go. MatchPatch shows those presets together as a temporary setlist in
the preset table.
Save overwrites the original preset files. The first overwrite prompt lets you approve overwriting the rest of the batch. Save As writes one matching setlist instead.
Do not mix preset files and setlists in one Open selection, and do not mix Helix and Pod Go files.
Both can help.
Normalize before rehearsal to start from balanced levels. After rehearsal, rerun or manually adjust any presets that still feel wrong in the band mix.
Yes, for setlists.
Use Select changed and choose a previous version of the same .hls or .pgs
setlist.
Yes. Enable Edit manually, then double-click editable cells.
Use small gain changes and save a backup.
Yes. The table has CSV open and save buttons.
This is useful if you want to review or edit preset names, snapshot names, and gain adjustments outside MatchPatch.
Use Default timing first. If results still vary, run Determine optimal parameters.
Long delay or reverb trails often need slower timing.
See Optimize Timing.
Send:
- what you were trying to do;
- whether you used hardware, loopback, or simulated mode;
- the warning text;
- a screenshot of the result table;
- a screenshot of the Log tab;
- whether recorded-output playback sounded correct.
Do not send private files unless you are comfortable sharing them.