LipSync GAP Model Loader (Legacy Alias)

Good news: this node is not actually a second loader. GapPerfectSyncModelLoader ("LipSync GAP Model Loader (Legacy Alias)") is just GapLipSyncModelLoader wearing an older name. In the pack's NODE_CLASS_MAPPINGS, both names point at the exact same class - the alias exists so workflows saved under the earlier "PerfectSync" branding keep loading without you having to rewire anything.

Why it exists

Geekatplay renamed their nodes when the pack settled on the LipSync GAP naming - the repo still ships a sample workflow called workflow_perfect_sync.json next to the newer workflow_lipsync_gap.json. So if you grabbed an early version of this pack, or a friend shared a workflow that predates the rename, your old graph references these class names. The alias keeps that graph valid. New workflows should use the current names, but honestly, picking the alias costs you nothing - it's byte-for-byte the same code path.

What it does

Exactly what the current loader does: it loads ByteDance's LatentSync UNet, a Whisper audio encoder, and your VAE, then hands you a single PERFECT_SYNC_MODELS bundle for the sampler. Same inputs, same meaning:

• unet_model - LatentSync UNet from ComfyUI/models/latentsync/.
• whisper_model - tiny through large; bigger Whisper, stronger mouth articulation.
• precision - fp16, fp32, or fp8_e4m3fn (your VRAM lever).
• vae - a VAE Loader output; the sampler casts it to match the precision.

One models output, wired into the sampler's models input.

Install and troubleshooting

Same pack install either way: ComfyUI Manager search LipSync GAP, or clone into custom_nodes/ and run install.bat. If the alias shows up but the current-named node doesn't after a restart, you've got a stale node registry - a full ComfyUI restart usually clears it.

If you load an old workflow and this node appears red/unplugged, check that the models landed in ComfyUI/models/latentsync/ - the alias doesn't carry its own weights, it reads the same files as the current loader. Model not found is the number-one failure mode, and it's almost always "the download didn't finish" rather than a node bug.