# SadTalker and NVIDIA GeForce RTX 5060 Ti

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%3E%5C
**Category:** Beginners\
**Created:** [November 8, 2025, 4:59pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105 "2025-11-08T16:59:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 8, 2025, 4:59pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F1 "2025-11-08T16:59:05Z")

</div>

Hello,

Can SadTalker work with the NVIDIA GeForce RTX 5060 Ti with 8GB VRAM?

Thank you.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 9, 2025, 12:36am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F2 "2025-11-09T00:36:46Z")

</div>

SadTalker will likely run with 8GB VRAM on low graphics settings. It’s mostly a speed issue. Once it boots up…

However, like all older Python libraries, the surrounding libraries’ maintenance has stopped, so resolving dependencies might be a pain. Especially on 50x0 systems, PyTorch is locked to newer versions only, so that will likely be a hassle.

In such cases, feeding the error message as is to a generative AI can be effective. Alternatively, isolating older Python versions in a virtual environment is the quickest solution.

* * *

SadTalker runs on a GeForce RTX 5060 Ti with 8 GB VRAM if you use the 256-px face model and current CUDA-12-series PyTorch. The 512-px model can work too, but start at 256 for stability and headroom. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker"))

# What this means in practice

- **GPU support:** RTX 5060 Ti is an official 50-series card (8 GB or 16 GB). Any recent NVIDIA driver + CUDA-12-compatible PyTorch works. ([NVIDIA](https://www.nvidia.com/en-us/geforce/news/rtx-5060-desktop-family-laptop-5060-coming-soon/ "Announcing The GeForce RTX 5060 Desktop Family ..."))
- **VRAM headroom:** Community runs show 6 GB often OOMs. 8 GB is a workable floor when you keep resolution and extras modest. If you use the A1111/Forge extension, headroom is tighter than the standalone script. ([GitHub](https://github.com/Winfredy/SadTalker/issues/118 "minimum vram requirements? - OpenTalker/SadTalker"))
- **Model size switch:** SadTalker exposes `--size 256|512`. Use **256** first to minimize memory; 512 is heavier. The official Space UI also defaults to 256. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker"))

# Beginner-safe setup for RTX 5060 Ti (8 GB)

Use a clean env, install PyTorch first, then SadTalker.

```bash
# 0) New environment
conda create -n sadtalker python=3.10 -y
conda activate sadtalker

# 1) Install PyTorch that matches your driver (CUDA 12.x)
# Use the official selector and copy the command it shows for your OS/CUDA.
# https://pytorch.org/get-started/locally/
pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu128 # example: CUDA 12.8

# 2) Get SadTalker
git clone https://github.com/OpenTalker/SadTalker.git # repo: https://github.com/OpenTalker/SadTalker
cd SadTalker
pip install -r requirements.txt
bash scripts/download_models.sh

# 3) First run: lowest VRAM footprint
python inference.py \
  --source_image face.png \
  --driven_audio voice.wav \
  --size 256 \ # release notes mention 256/512 # https://github.com/OpenTalker/SadTalker/releases
  --preprocess crop \ # keep crops tight
  --result_dir results

```

Why this works: PyTorch’s current wheels target CUDA-12.x (e.g., cu126/cu128), which covers new-generation GPUs. SadTalker’s 256-px face model is explicitly supported and lighter. ([PyTorch](https://pytorch.org/get-started/locally/ "Get Started"))

# Low-VRAM operating tips

- Keep **`--size 256`** and **batch size = 1**. Try 512 only after 256 is stable. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker"))

- Turn **enhancers** (e.g., GFPGAN) off during generation; run them afterward if needed.

- If you use the **AUTOMATIC1111/Forge extension** , expect more VRAM use than the standalone CLI; close other heavy extensions. ([GitHub](https://github.com/Winfredy/SadTalker/issues/124 "TAB won't appear ? · Issue #124 · OpenTalker/SadTalker"))

- If you hit borderline OOM, set the PyTorch allocator hint before launching:

# Common dependency pitfalls and quick fixes

- **NumPy conflicts:** If the run fails after `pip install -r requirements.txt`, pin **`numpy<2`** and retry. This resolves many SadTalker reports where libs were built against NumPy 1.x. ([GitHub](https://github.com/OpenTalker/SadTalker/issues/839 "Wrong Numpy Version - error · Issue #839"))
- **Gradio/Space drift:** Old Spaces and tutorials used older Gradio and Torch pins; prefer current PyTorch and keep the Space/Gradio versions consistent. The official Space shows 256/512 and preprocess options you can mirror locally. ([Hugging Face](https://huggingface.co/spaces/vinthony/SadTalker/blob/main/app.py "app.py · vinthony/SadTalker at main"))

# If you don’t want to fight drivers

- **Hugging Face Spaces:** Your local GPU is irrelevant in the cloud. The free **CPU Basic** tier runs but is slow; pick a **GPU Space** like T4 16 GB or L4 24 GB for smooth 512-px runs. Hardware tables and pricing are public. ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-overview "Spaces Overview"))

# Context you asked for

- **SadTalker capabilities and size switch** are documented in the repo’s releases and reflected in the Gradio Space UI. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker"))
- **The RTX 5060 Ti exists in 8 GB and 16 GB variants** and launched in April 2025; the family page is live. ([NVIDIA](https://www.nvidia.com/en-us/geforce/news/rtx-5060-desktop-family-laptop-5060-coming-soon/ "Announcing The GeForce RTX 5060 Desktop Family ..."))
- **Community VRAM experience:** 6 GB often OOMs; 8 GB is workable if you keep settings conservative. ([GitHub](https://github.com/Winfredy/SadTalker/issues/118 "minimum vram requirements? - OpenTalker/SadTalker"))

# Curated starter materials

**Core docs and knobs**

- SadTalker GitHub (README, CLI flags) and Releases (shows `--size 256|512`, preprocess modes). ([GitHub](https://github.com/OpenTalker/SadTalker "[CVPR 2023] SadTalker:Learning Realistic 3D Motion ..."))
- Official HF Space source (shows 256 default, preprocess radio). Useful to mirror UI choices locally. ([Hugging Face](https://huggingface.co/spaces/vinthony/SadTalker/blob/main/app.py "app.py · vinthony/SadTalker at main"))
- PyTorch “Get Started” installer (pick CUDA-12.x command for your OS). ([PyTorch](https://pytorch.org/get-started/locally/ "Get Started"))

**Cloud options**

- Spaces hardware tables and pricing if you prefer a managed GPU. ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-overview "Spaces Overview"))

**Troubleshooting**

- NumPy version breakage threads for SadTalker and general NumPy-2 migration notes. ([GitHub](https://github.com/OpenTalker/SadTalker/issues/1002 "Multiple issues related to version compatibilities #1002"))

**Bottom line:** With an RTX 5060 Ti 8 GB you can run SadTalker today. Use **PyTorch CUDA-12.x** , start at **`--size 256`** , keep **batch=1** and enhancers off, then scale up only if memory allows. ([PyTorch](https://pytorch.org/get-started/locally/ "Get Started"))

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 9, 2025, 5:17am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F3 "2025-11-09T05:17:49Z")

</div>

Hello,

Can I use SadTalker on ComfyUI?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 9, 2025, 6:56am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F4 "2025-11-09T06:56:07Z")

</div>

Seems [barely you can](https://github.com/haomole/Comfyui-SadTalker)…?

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 9, 2025, 12:43pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F5 "2025-11-09T12:43:42Z")

</div>

Hello,

Do I need to manually create the `customـnodes\Comfyui-SadTalker\SadTalker\checkpoint\` and `(comfyui root)\gfpgan\weights\` directories?

How do I install the program?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 9, 2025, 1:34pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F6 "2025-11-09T13:34:48Z")

</div>

Probably just install it like this…? I’m not a ComfyUI user, so I don’t really know…

* * *

Here’s a setup for **Comfyui-SadTalker** in ComfyUI.

1. Install or open ComfyUI

2. Install the Comfyui-SadTalker node

3. Add the four SadTalker model files

4. Add the GFPGAN/facexlib weights

5. Install FFmpeg and verify PATH

6. Restart ComfyUI

7. Load the sample workflow and test

8. Low-VRAM defaults for an 8 GB GPU

**Where the files come from (for double-checking):**

- Node README: exact folders and filenames for checkpoints and weights. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))
- SadTalker Releases: 256/512 face models and the two MappingNet files. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker · GitHub"))
- facexlib + GFPGAN: official weight downloads. ([GitHub](https://github.com/xinntao/facexlib/releases "Releases · xinntao/facexlib"))

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 10, 2025, 7:34am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F7 "2025-11-10T07:34:21Z")

</div>

Hello,

I’m really thankful for your help.

When I opened the workflow, I got the following error:

 ![SadTalker](https://us1.discourse-cdn.com/hellohellohello/original/3X/5/5/55dec03384c911b57630be9aee4f8cb77d7a7edb.png)

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 10, 2025, 9:20am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F8 "2025-11-10T09:20:01Z")

</div>

Hmm… The necessary prerequisite programs or data are missing or cannot be found (especially common in Windows environments), the versions are incompatible (too new or too old), or they are not installed correctly…

* * *

You opened a workflow that references nodes your ComfyUI does not have loaded. The pop-up lists them: **SadTalker, ShowAudio, LoadRefVideo, ShowVideo, ShowText**. In ComfyUI, a “missing node” means the custom node that defines that class is not installed or failed to import. Fix = install the right custom nodes, their weights and Python deps, ensure FFmpeg is available, then restart.

# Why this happens

- Workflows are JSON that name exact node types. If ComfyUI can’t import a node class, it shows this dialog. Causes: the node repo isn’t installed, it failed to import due to missing Python deps, or your ComfyUI build is too old for that node. ([ComfyUI Official Documentation](https://docs.comfy.org/installation/install_custom_node "How to Install Custom Nodes in ComfyUI"))
- The **Comfyui-SadTalker** node’s README explicitly warns about two common symptoms when it loads but parts fail: “audio … undefined → update ComfyUI” and “mp4 save error → FFmpeg not on PATH.” It also shows the exact folders for the required model and GFPGAN/facexlib weights. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "haomole/Comfyui-SadTalker"))
- Video I/O nodes like **Load Video / Video Combine** live in **ComfyUI-VideoHelperSuite** and require FFmpeg for audio mux. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))
- **ShowText** comes from **ComfyUI-Custom-Scripts** ; many workflows rely on it for UI text. ([GitHub](https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/364 "ShowText Node is no longer displaying text. #364"))

# Step-by-step fix (beginner-safe)

1. Update ComfyUI  
Update to a recent build, then restart. Older builds trigger the “audio undefined” issue with the SadTalker node. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "haomole/Comfyui-SadTalker"))

2. Use ComfyUI-Manager to install what the workflow needs  
Open **Manager → Install Custom Nodes** , search and install:

3. Put the SadTalker model files in the exact folder it expects  
Create the folder if missing:  
`ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/`  
Place **all four** files:

4. Put the GFPGAN/facexlib weights where ComfyUI looks for them  
Create: `ComfyUI/gfpgan/weights/`  
Add:

5. Install Python dependencies for the SadTalker node  
In the **same Python env ComfyUI uses** :

6. Install FFmpeg and verify PATH  
FFmpeg is required by VHS (VideoHelperSuite) to mux audio when combining frames to MP4. After installation, verify with: `ffmpeg -version`. If missing, video save nodes will fail. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

7. Restart ComfyUI fully  
Close the server, relaunch, and reload the workflow. If a node type still shows missing, run **Manager → Install Missing Custom Nodes** again. ([ComfyUI Official Documentation](https://docs.comfy.org/installation/install_custom_node "How to Install Custom Nodes in ComfyUI"))

# If your workflow mentions **LoadRefVideo**

Some workflows use differently named video-loader nodes. If **LoadRefVideo** stays missing, replace it with **VHS → Load Video** or **Load Video (Path)** from VideoHelperSuite; they provide equivalent video-to-frames I/O in most graphs. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

# Quick verification

- **SadTalker node appears** in the node list. No startup import errors in the console.
- **Weights present** at the exact paths above.
- **FFmpeg OK:** `ffmpeg -version` prints a version and VHS nodes can save video with audio. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

# References

- Comfyui-SadTalker README: required folders, model names, FFmpeg/PATH and “audio undefined → update ComfyUI.” ([GitHub](https://github.com/haomole/Comfyui-SadTalker "haomole/Comfyui-SadTalker"))
- SadTalker Releases: `SadTalker_V0.0.2_256/512.safetensors`, `mapping_00109/00229` assets. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker"))
- ComfyUI-VideoHelperSuite README: video I/O nodes and FFmpeg requirement. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))
- ComfyUI Manager docs and issue thread: how to install nodes, “Install Missing Custom Nodes,” and restart. ([ComfyUI Official Documentation](https://docs.comfy.org/installation/install_custom_node "How to Install Custom Nodes in ComfyUI"))
- ShowText node in ComfyUI-Custom-Scripts. ([GitHub](https://github.com/pythongosssss/ComfyUI-Custom-Scripts/issues/364 "ShowText Node is no longer displaying text. #364"))

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 10, 2025, 10:30am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F9 "2025-11-10T10:30:11Z")

</div>

Thanks again.

Unfortunately, there is no such thing as **Comfyui-SadTalker** :

 ![SadTalker-3](https://us1.discourse-cdn.com/hellohellohello/original/3X/1/e/1e4ad37f8194fa9f8af75cd1a38807283ecfee12.png)

About the files and directories:

`$ pwd`  
`/home/localai/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints`  
`localai@LocalAI:~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints$ ls`  
`mapping_00109-model.pth.tar mapping_00229-model.pth.tar SadTalker_V0.0.2_256.safetensors SadTalker_V0.0.2_512.safetensors`

And:

`$ pwd`  
`/home/localai/comfy/ComfyUI/gfpgan/weights`  
`localai@LocalAI:~/comfy/ComfyUI/gfpgan/weights$ ls`  
`alignment_WFLW_4HG.pth detection_Resnet50_Final.pth GFPGANv1.4.pth parsing_parsenet.pth`

The **ffmpeg** version is:

`$ ffmpeg -version`  
`ffmpeg version 7.1.2-0+deb13u1 Copyright (c) 2000-2025 the FFmpeg developers`  
`built with gcc 14 (Debian 14.2.0-19)`

The problem was not solved.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 10, 2025, 11:56pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F10 "2025-11-10T23:56:28Z")

</div>

Hmm…

* * *

Your weights and FFmpeg are fine. The node pack itself isn’t loading, and your workflow also references nodes that live in other packs. Fix it in this order.

# What’s happening (context)

- **Manager shows 0 results** because the registry view is channel-based and not every repo is indexed. Use **Install via Git URL** or clone manually. Manager docs explain the DB modes and “Try Install.” ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "GitHub - Comfy-Org/ComfyUI-Manager: ComfyUI-Manager is an extension designed to enhance the usability of ComfyUI. It offers management functions to install, remove, disable, and enable various custom nodes of ComfyUI. Furthermore, this extension provides a hub feature and convenience functions to access a wide range of information within ComfyUI."))
- **Comfyui-SadTalker** targets a specific ComfyUI build (“ComfyUI-aki v1.3”). The README lists the exact checkpoint locations and common errors (audio undefined → update ComfyUI; MP4 error → add FFmpeg to PATH). Your folders match those paths, so the remaining blocker is Python deps or API drift. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))
- Your workflow also expects **video I/O/preview** and **text display** nodes that are **not** in SadTalker: they come from **VideoHelperSuite** and a **Show Text** extension. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "GitHub - Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to video workflows"))

# Do this (Linux, matches your paths)

1. Start ComfyUI from a terminal and read import errors

```bash
cd ~/comfy/ComfyUI
python3 main.py

```

If a custom node fails, ComfyUI prints a `ModuleNotFoundError` or similar during “loading custom nodes…”. This is the fastest way to see what dependency is missing. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "GitHub - Comfy-Org/ComfyUI-Manager: ComfyUI-Manager is an extension designed to enhance the usability of ComfyUI. It offers management functions to install, remove, disable, and enable various custom nodes of ComfyUI. Furthermore, this extension provides a hub feature and convenience functions to access a wide range of information within ComfyUI."))

1. Make sure the SadTalker node is actually installed and up to date

```bash
cd ~/comfy/ComfyUI/custom_nodes
# if you already cloned it, pull; otherwise clone it
[-d Comfyui-SadTalker] && (cd Comfyui-SadTalker && git pull) || git clone https://github.com/haomole/Comfyui-SadTalker.git

```

The repo is the correct one. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))

1. Install SadTalker node dependencies in the **same** Python env you run ComfyUI with

```bash
cd ~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker
python3 -m pip install -r requirements.txt

```

This repo ships a `requirements.txt`; installing it fixes most import failures. ([GitHub](https://github.com/haomole/Comfyui-SadTalker/blob/main/requirements.txt "Comfyui-SadTalker/requirements.txt at main · haomole/Comfyui-SadTalker · GitHub"))

1. Install the two supporting packs your workflow needs

```bash
cd ~/comfy/ComfyUI/custom_nodes
git clone https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite.git
git clone https://github.com/fairy-root/ComfyUI-Show-Text.git # or: pythongosssss/ComfyUI-Custom-Scripts
# VHS deps:
cd ComfyUI-VideoHelperSuite
python3 -m pip install -r requirements.txt

```

- **VideoHelperSuite (VHS)** provides **Load Video** , **Load Audio** , **Video Combine** , and animated previews. It calls **ffmpeg** for previews and for combining frames + audio. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "GitHub - Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to video workflows"))
- **Show Text** provides the **ShowText** node used by many workflows. ([GitHub](https://github.com/pythongosssss/ComfyUI-Custom-Scripts "pythongosssss/ComfyUI-Custom-Scripts"))

1. Keep your weights where they already are

- SadTalker checkpoints:  
`~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/` → `SadTalker_V0.0.2_256.safetensors`, `SadTalker_V0.0.2_512.safetensors`, `mapping_00109-model.pth.tar`, `mapping_00229-model.pth.tar`. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))
- GFPGAN/facexlib weights:  
`~/comfy/ComfyUI/gfpgan/weights/` → `GFPGANv1.4.pth`, `alignment_WFLW_4HG.pth`, `detection_Resnet50_Final.pth`, `parsing_parsenet.pth`. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))

1. Confirm FFmpeg from the **same shell** that launches ComfyUI

```bash
ffmpeg -version

```

VHS passes ffmpeg arguments for video formats and advanced previews. Your version 7.1 is fine. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "GitHub - Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to video workflows"))

1. Restart ComfyUI, then reload the workflow

- If **SadTalker** still doesn’t appear in the node list, read the terminal output and `pip install` any module it complains about.
- If the workflow still shows **LoadRefVideo** missing, replace it with **VHS → Load Video (Upload/Path)**. VHS covers the same role for most graphs. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "GitHub - Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to video workflows"))

1. Optional: use Manager effectively

- Manager has DB modes; switch to **Channel (remote)** and **Fetch Updates** if lists look empty. Use **Try Install** or **Install via Git URL** for repos not in the index. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "GitHub - Comfy-Org/ComfyUI-Manager: ComfyUI-Manager is an extension designed to enhance the usability of ComfyUI. It offers management functions to install, remove, disable, and enable various custom nodes of ComfyUI. Furthermore, this extension provides a hub feature and convenience functions to access a wide range of information within ComfyUI."))

# Why this works

- The SadTalker README confirms the exact folder layout, the four SadTalker files, and the four GFPGAN/facexlib weights you already placed, plus the two common runtime errors. That leaves **node import** as the blocker, which steps 2–4 address. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))
- VHS supplies the video/audio nodes and uses ffmpeg for combining frames and audio and for previews, matching the missing **LoadRefVideo/ShowVideo/ShowAudio** functionality. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "GitHub - Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to video workflows"))
- Manager’s registry can be empty by channel; direct Git install avoids that failure mode, and its README documents the channel system and “Try Install.” ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "GitHub - Comfy-Org/ComfyUI-Manager: ComfyUI-Manager is an extension designed to enhance the usability of ComfyUI. It offers management functions to install, remove, disable, and enable various custom nodes of ComfyUI. Furthermore, this extension provides a hub feature and convenience functions to access a wide range of information within ComfyUI."))

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 11, 2025, 5:48am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F11 "2025-11-11T05:48:05Z")

</div>

Thank you so much.

I restart ComfyUI and got the following error:

```auto
…
0.0 seconds (IMPORT FAILED): /home/localai/comfy/ComfyUI/custom_nodes/comfyui-minimal-workflow-image
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/comfyui-text-randomizer
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/comfyui-show-text
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-GGUF
0.0 seconds (IMPORT FAILED): /home/localai/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker
0.0 seconds (IMPORT FAILED): /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Vaja-Ai4thai
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Custom-Scripts
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/comfyui_ultimatesdupscale
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/comfyui-impact-subpack
0.0 seconds: /home/localai/comfy/ComfyUI/custom_nodes/comfyui-ollama-describer
0.1 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Manager
0.1 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Impact-Pack
0.1 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Copilot
0.2 seconds: /home/localai/comfy/ComfyUI/custom_nodes/comfyui-videohelpersuite
0.2 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI_fsdymy
0.2 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Easy-Use
0.4 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-Text
0.5 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-WanVideoWrapper
0.6 seconds: /home/localai/comfy/ComfyUI/custom_nodes/ComfyUI-SwissArmyKnife

Context impl SQLiteImpl.
Will assume non-transactional DDL.
No target revision found.
Starting server

To see the GUI go to: http://172.21.50.69:8188

```

I tried to install **Comfyui-SadTalker** via the **Install via Git URL** option but I got the following error:

`This action is not allowed with this security level configuration.`

And about the dependencies:

```auto
$ python3 -m pip install -r requirements.txt
Collecting numpy==1.23.4 (from -r requirements.txt (line 1))
Using cached numpy-1.23.4.tar.gz (10.7 MB)
Installing build dependencies … done
Getting requirements to build wheel … error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [32 lines of output]
Traceback (most recent call last):
File “/home/localai/ComfyUI/comfy-env/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py”, line 389, in
main()
~~~~ ^^
File “/home/localai/ComfyUI/comfy-env/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py”, line 373, in main
json_out[“return_val”] = hook(**hook_input[“kwargs”])
~~~~ ^^^^^^^^^^^^^^^^^^^^^^^^
File “/home/localai/ComfyUI/comfy-env/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py”, line 137, in get_requires_for_build_wheel
backend = _build_backend()
File “/home/localai/ComfyUI/comfy-env/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py”, line 70, in _build_backend
obj = import_module(mod_path)
File “/usr/lib/python3.13/importlib/init.py”, line 88, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
~~~~~~~~~~~~~~~~~~~~~~ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “”, line 1387, in _gcd_import
File “”, line 1360, in _find_and_load
File “”, line 1310, in _find_and_load_unlocked
File “”, line 488, in _call_with_frames_removed
File “”, line 1387, in _gcd_import
File “”, line 1360, in _find_and_load
File “”, line 1331, in _find_and_load_unlocked
File “”, line 935, in _load_unlocked
File “”, line 1026, in exec_module
File “”, line 488, in _call_with_frames_removed
File “/tmp/pip-build-env-4se_n3yz/overlay/lib/python3.13/site-packages/setuptools/init.py”, line 16, in
import setuptools.version
File “/tmp/pip-build-env-4se_n3yz/overlay/lib/python3.13/site-packages/setuptools/version.py”, line 1, in
import pkg_resources
File “/tmp/pip-build-env-4se_n3yz/overlay/lib/python3.13/site-packages/pkg_resources/init.py”, line 2172, in
register_finder(pkgutil.ImpImporter, find_on_path)
^^^^^^^^^^^^^^^^^^^
AttributeError: module ‘pkgutil’ has no attribute ‘ImpImporter’. Did you mean: ‘zipimporter’?
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed to build ‘numpy’ when getting requirements to build wheel

```

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 11, 2025, 6:43am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F12 "2025-11-11T06:43:58Z")

</div>

As of today, Python 3.13 is a landmine when using generative AI-related software. Library compatibility is still poor. This isn’t limited to ComfyUI… Python 3.10-3.12 is recommended.

While newer Python versions seem to offer better execution speed, it’s meaningless if it doesn’t work.

* * *

Root cause: your ComfyUI runtime is Python 3.13, but the Comfyui-SadTalker node pins `numpy==1.23.4`. NumPy 1.23.x has wheels for Python ≤3.11, not for 3.12/3.13, so `pip` tries to build from source and crashes because Python ≥3.12 removed `pkgutil.ImpImporter` which old build tooling still touches. Result: “IMPORT FAILED” for Comfyui-SadTalker and a `numpy` build error. ([PyPI](https://pypi.org/project/numpy/1.23.4/ "numpy · PyPI"))

Secondary blocker: ComfyUI-Manager refused “Install via Git URL” due to its security level. You must lower it temporarily to install or fix nodes. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "Comfy-Org/ComfyUI-Manager"))

Also note: the Comfyui-SadTalker README says it was built against an older ComfyUI build and may not be adapted to “new versions,” so running it on modern ComfyUI requires a compatible Python and deps. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))

* * *

## Fix in 3 steps

### 1) Switch ComfyUI to Python 3.11 (new venv)

Do **not** reuse the 3.13 env.

**Debian/Ubuntu approach**

```bash
# install Python 3.11 and venv (if not present)
sudo apt-get update
sudo apt-get install -y python3.11 python3.11-venv

# create a fresh env for ComfyUI
cd ~/comfy/ComfyUI
python3.11 -m venv ~/comfy/venvs/comfy311
source ~/comfy/venvs/comfy311/bin/activate

# base ComfyUI deps
python -m pip install -U pip setuptools wheel
python -m pip install -r requirements.txt

```

**If apt can’t give you 3.11** use `pyenv` quickly:

```bash
curl https://pyenv.run | bash
export PATH="$HOME/.pyenv/bin:$PATH"; eval "$(pyenv init -)"; eval "$(pyenv virtualenv-init -)"
pyenv install 3.11.9
pyenv virtualenv 3.11.9 comfy311
pyenv activate comfy311
cd ~/comfy/ComfyUI
python -m pip install -U pip setuptools wheel
python -m pip install -r requirements.txt

```

Why 3.11: NumPy 1.23.4 has prebuilt wheels for Python 3.8–3.11, so installs cleanly. ([PyPI](https://pypi.org/project/numpy/1.23.4/ "numpy · PyPI"))

### 2) Let Manager install node dependencies (temporarily weaken security)

Edit Manager config and restart ComfyUI.

- Open: `~/comfy/ComfyUI/user/default/ComfyUI-Manager/config.ini`

- Set:

- Save, restart ComfyUI, then in **Manager** click **Check Missing** on the SadTalker node to auto-install its Python requirements. Revert `security_level` to `normal` after installing. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "Comfy-Org/ComfyUI-Manager"))

If you can’t edit through the UI, edit the file on disk at the same path and restart. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "Comfy-Org/ComfyUI-Manager"))

### 3) Manually install missing bits (if Manager can’t)

You already placed the model files correctly. Now finish Python deps in the 3.11 venv:

```bash
# still inside comfy311 venv
# SadTalker node deps
python -m pip install -r custom_nodes/Comfyui-SadTalker/requirements.txt

# Video + audio helpers often used by the workflow
python -m pip install -r custom_nodes/comfyui-videohelpersuite/requirements.txt
python -m pip install imageio-ffmpeg

```

VideoHelperSuite and SadTalker expect a working `ffmpeg` in PATH; your system `ffmpeg 7.x` is fine. If nodes still complain, ensure `which ffmpeg` returns a path visible to the venv, or install OS ffmpeg. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

* * *

## Quick sanity checks

```bash
# 1) confirm Python and NumPy versions
python - << 'PY'
import platform, numpy; print("Python", platform.python_version(), "NumPy", numpy. __version__ )
PY
# Expect: Python 3.11.x, NumPy 1.23.4 (or 1.23.x)

# 2) start ComfyUI with the 3.11 venv
python main.py --listen 0.0.0.0 --port 8188

```

Load your SadTalker workflow again. The “Some Nodes Are Missing” list should be gone once `Comfyui-SadTalker` and display nodes load.

* * *

## Why the previous installs failed

- `numpy==1.23.4` is too old for Python 3.12/3.13, so pip tried to build from source and hit the Python 3.12+ removal of `pkgutil.ImpImporter`, yielding the exact error you pasted. Using Python 3.11 resolves this by using a wheel. ([PyPI](https://pypi.org/project/numpy/1.23.4/ "numpy · PyPI"))
- ComfyUI-Manager blocked Git installs because of its security level; change it to `weak` to install, then restore. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "Comfy-Org/ComfyUI-Manager"))
- The node itself warns it’s built for an older ComfyUI package, so a conservative Python/runtime is safer. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))

* * *

## Reference links

- Comfyui-SadTalker repo and notes about older ComfyUI compatibility and required model files. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))
- NumPy release info showing Python support boundaries; 1.23.x supports up to 3.11. ([PyPI](https://pypi.org/project/numpy/1.23.4/ "numpy · PyPI"))
- Python ≥3.12 removes `pkgutil.ImpImporter`, which triggers the pip/setuptools error you saw. ([Stack Overflow](https://stackoverflow.com/questions/77364550/attributeerror-module-pkgutil-has-no-attribute-impimporter-did-you-mean "AttributeError: module 'pkgutil' has no attribute 'ImpImporter ..."))
- ComfyUI-Manager config paths and the `security_level` fix. ([GitHub](https://github.com/Comfy-Org/ComfyUI-Manager "Comfy-Org/ComfyUI-Manager"))
- VideoHelperSuite ffmpeg expectation. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

If you must stay on Python 3.13, the workaround is to **edit** `custom_nodes/Comfyui-SadTalker/requirements.txt` and replace `numpy==1.23.4` with `numpy>=1.26` and then reinstall. It can work, but it’s unsupported by the node author and may break other pinned deps; 3.11 is the low-risk route. ([numpy.org](https://numpy.org/news/ "News"))

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 12, 2025, 5:27am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F13 "2025-11-12T05:27:47Z")

</div>

Thanks again.  
For the previous installation, I followed the following procedure. I added the following lines to the `.bashrc` file:

```auto
export PYENV_ROOT="$HOME/.pyenv"
[[-d $PYENV_ROOT/bin]] && export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init - bash)"
eval "$(pyenv virtualenv-init -)"

```

Then:

```auto
$ sudo apt install python3 python3-pip python3-venv git
$ python3 -m venv comfy-env
$ source comfy-env/bin/activate
$ pip install comfy-cli
$ comfy install
$ pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

```

Now I want to install another ComfyUI, but I don’t want it to interfere with the previous one. What is the solution?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 12, 2025, 7:02am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F14 "2025-11-12T07:02:05Z")

</div>

Hmm… Like this?

* * *

Run a second ComfyUI in its **own folder** , **its own Python venv** , and **on a different port**. You can also **share the models/** tree via a symlink to save disk. This keeps both installs isolated.

Below is a clean Linux plan that matches your setup.

# Plan A — Use comfy-cli with a separate workspace (easiest)

**Why this works:** `comfy-cli` lets you target a specific install path with `--workspace`, and you can launch each instance on its own port. ([GitHub](https://github.com/Comfy-Org/comfy-cli "GitHub - Comfy-Org/comfy-cli: Command Line Interface for Managing ComfyUI"))

1. Create a new venv (use Python 3.11 for widest custom-node compatibility)

```bash
# keep your existing venv untouched
python3.11 -m venv ~/venvs/comfy-sadtalker
source ~/venvs/comfy-sadtalker/bin/activate
pip install -U pip setuptools wheel
pip install comfy-cli

```

(If `python3.11` isn’t present, install it or use pyenv to add 3.11.)

1. Install ComfyUI **into a new workspace directory**

```bash
# this will create ~/comfy/sadtalker/ComfyUI
comfy --workspace=~/comfy/sadtalker install

```

`--workspace=<path>` installs ComfyUI under that path instead of reusing your first install. ([GitHub](https://github.com/Comfy-Org/comfy-cli "GitHub - Comfy-Org/comfy-cli: Command Line Interface for Managing ComfyUI"))

1. Launch it on a different port (example 8190)

```bash
# listen locally and avoid port clash with your first instance
comfy --workspace=~/comfy/sadtalker launch -- --listen 127.0.0.1 --port 8190

```

`--listen` and `--port` are standard ComfyUI server flags; running two instances on different ports is supported. ([GitHub](https://github.com/Comfy-Org/comfy-cli "GitHub - Comfy-Org/comfy-cli: Command Line Interface for Managing ComfyUI"))

1. (Optional) Make this workspace the default _only when you want to_

```bash
comfy set-default ~/comfy/sadtalker
# undo later by setting your other workspace as default

```

The CLI supports selecting which workspace subsequent `comfy` commands act on. ([GitHub](https://github.com/Comfy-Org/comfy-cli "GitHub - Comfy-Org/comfy-cli: Command Line Interface for Managing ComfyUI"))

1. (Optional) Share the big **models/** folder to save disk

```bash
# inside the new ComfyUI folder
cd ~/comfy/sadtalker/ComfyUI
rm -rf models
ln -s ~/comfy/ComfyUI/models models # point to your first install's models

```

ComfyUI’s folder layout includes a top-level **models/** directory; a symlink lets both installs see the same checkpoints. ([comfyui-wiki.com](https://comfyui-wiki.com/en/interface/files "ComfyUI Installation Package Folder Structure Explained"))

# Plan B — Manual second install (no comfy-cli)

1. New venv + new folder

```bash
python3.11 -m venv ~/venvs/comfy-sadtalker
source ~/venvs/comfy-sadtalker/bin/activate
git clone https://github.com/comfyanonymous/ComfyUI.git ~/comfy/sadtalker/ComfyUI
cd ~/comfy/sadtalker/ComfyUI
pip install -U pip setuptools wheel
pip install -r requirements.txt

```

Manual install in its own directory keeps it separate by design. ([ComfyUI](https://docs.comfy.org/installation/manual_install "How to install ComfyUI manually in different systems"))

1. Launch on another port

```bash
python main.py --listen 127.0.0.1 --port 8190

```

These flags are the standard way to bind address/port. ([Reddit](https://www.reddit.com/r/comfyui/comments/15jxydu/comfyui_command_line_arguments_informational/ "ComfyUI Command Line Arguments: Informational"))

1. (Optional) Share **models/** via symlink as shown above. ([comfyui-wiki.com](https://comfyui-wiki.com/en/interface/files "ComfyUI Installation Package Folder Structure Explained"))

# Tips that prevent cross-talk

- **Never reuse the same venv.** One venv per ComfyUI keeps Python packages isolated. Official docs recommend virtual environments for this reason. ([ComfyUI](https://docs.comfy.org/installation/manual_install "How to install ComfyUI manually in different systems"))

- **Different ports.** Keep the first on 8188 and the second on 8190 (or any free port). Running multiple servers on different ports is a common pattern; several users do this. ([GitHub](https://github.com/comfyanonymous/ComfyUI/issues/5043 "I'm running two installations of ComfyUI. One on port 8188 ..."))

- **Use `--workspace` with comfy-cli** so node installs and updates target the right copy. You can check which workspace you’re operating on with `comfy which` or prefix commands with `--workspace=...`. ([GitHub](https://github.com/Comfy-Org/comfy-cli "GitHub - Comfy-Org/comfy-cli: Command Line Interface for Managing ComfyUI"))

- **FFmpeg and GPU libs are system-wide** and can be shared. Only Python packages and ComfyUI files need isolation.

- **If you run both concurrently** , start each from its own venv and folder:

# Why this is safe

- **Workspaces** let comfy-cli install and run ComfyUI in a path you choose, so nothing touches your first install. ([GitHub](https://github.com/Comfy-Org/comfy-cli "GitHub - Comfy-Org/comfy-cli: Command Line Interface for Managing ComfyUI"))
- **Virtual environments** isolate Python deps (a frequent source of conflicts with custom nodes like SadTalker). Official Comfy docs also advocate venvs for clean installs. ([ComfyUI](https://docs.comfy.org/installation/manual_install "How to install ComfyUI manually in different systems"))
- **Binding to different ports** cleanly separates running servers; ComfyUI supports `--listen/--port` and the community uses this for multiple instances. ([Reddit](https://www.reddit.com/r/comfyui/comments/15jxydu/comfyui_command_line_arguments_informational/ "ComfyUI Command Line Arguments: Informational"))

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 12, 2025, 7:19am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F15 "2025-11-12T07:19:22Z")

</div>

Can two ComfyUIs run at the same time? I guess the first ComfyUI is taking over the GPU and the other version can’t run!

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 12, 2025, 12:11pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F16 "2025-11-12T12:11:36Z")

</div>

Hello,  
To make sure there was no interference, I created another username and installed ComfyUI and SadTalker as follows:

```auto
$ git clone https://github.com/pyenv/pyenv.git ~/.pyenv
$ git clone https://github.com/pyenv/pyenv-virtualenv.git ~/.pyenv/plugins/pyenv-virtualenv

$ cp ~/.bashrc ~/.bashrc.backup 
$ grep -v 'pyenv\|PYENV' ~/.bashrc > ~/.bashrc.temp
$ mv ~/.bashrc.temp ~/.bashrc

$ cat >> ~/.bashrc << 'EOF'
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init - bash)"
eval "$(pyenv virtualenv-init -)"
EOF

$ source ~/.bashrc

$ pyenv install 3.11.9
$ pyenv global 3.11.9
$ python3 -m venv comfy-env
$ source comfy-env/bin/activate
$ pip install -U pip setuptools wheel
$ pip install comfy-cli
$ comfy install
$ pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124
$ comfy --workspace=~/comfy/sadtalker install
$ comfy --workspace=~/comfy/sadtalker launch -- --listen 172.21.50.69 --port 8190

```

Now:

```auto
(comfy-env) sadtalker@LocalAI:~/comfy$ ls
ComfyUI sadtalker

```

Now what are the next steps? Should I create the `checkpoints` directory?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 12, 2025, 1:32pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F17 "2025-11-12T13:32:00Z")

</div>

Yeah. There’s not much point in running them simultaneously. It’s just that you can. What’s important is that you can install two or three separately. Well, you probably wouldn’t use them at the same time anyway…😅

* * *

You can run two ComfyUIs concurrently. They must use different folders, different Python venvs, and different ports. The GPU is shared. If both instances run heavy graphs at the same time, VRAM contention can cause OOM in one or both. One-GPU hosts: stagger jobs or expect queueing. Multi-GPU hosts: pin one ComfyUI process per GPU. ([Reddit](https://www.reddit.com/r/comfyui/comments/15jxydu/comfyui_command_line_arguments_informational/ "ComfyUI Command Line Arguments: Informational"))

# What to do next in your new workspace (`~/comfy/sadtalker/ComfyUI`)

You already launched on `--port 8190`. Finish node install and weights, then relaunch.

## 1) Install the SadTalker node and its deps

```bash
# in the new workspace
cd ~/comfy/sadtalker/ComfyUI/custom_nodes
git clone https://github.com/haomole/Comfyui-SadTalker
# deps (same venv you launched with)
python -m pip install -r Comfyui-SadTalker/requirements.txt

```

The repo expects an older ComfyUI but works if deps are satisfied. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "haomole/Comfyui-SadTalker"))

## 2) Install helpers your workflow expects

```bash
# Video I/O + MP4 muxing
git clone https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite
python -m pip install -r ComfyUI-VideoHelperSuite/requirements.txt

# Text display node (if your workflow references ShowText)
git clone https://github.com/fairy-root/ComfyUI-Show-Text

```

VHS needs a working `ffmpeg` in PATH; you already have it. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

## 3) Create the SadTalker **checkpoints** folder (yes, you need it here too)

Option A— **copy** the four model files into the new workspace:

```bash
mkdir -p ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints
cp ~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/* \
   ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/

```

Option B— **symlink** to avoid duplication:

```bash
mkdir -p ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints
ln -s ~/comfy/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/* \
      ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints/

```

Required files in that folder:

```auto
SadTalker_V0.0.2_256.safetensors
SadTalker_V0.0.2_512.safetensors
mapping_00109-model.pth.tar
mapping_00229-model.pth.tar

```

These are the official release assets. ([GitHub](https://github.com/OpenTalker/SadTalker/releases "Releases · OpenTalker/SadTalker"))

## 4) Add the GFPGAN/facexlib weights again (or symlink)

```bash
mkdir -p ~/comfy/sadtalker/ComfyUI/gfpgan/weights
# copy or symlink from the other install:
cp ~/comfy/ComfyUI/gfpgan/weights/* ~/comfy/sadtalker/ComfyUI/gfpgan/weights/
# or
ln -s ~/comfy/ComfyUI/gfpgan/weights/* ~/comfy/sadtalker/ComfyUI/gfpgan/weights/

```

VHS and many face-enhance pipelines assume these standard filenames and location. ([GitHub](https://github.com/Kosinkadink/ComfyUI-VideoHelperSuite "Kosinkadink/ComfyUI-VideoHelperSuite: Nodes related to ..."))

## 5) Relaunch the second ComfyUI cleanly

```bash
# still in your 3.11 venv
comfy --workspace=~/comfy/sadtalker launch -- --listen 172.21.50.69 --port 8190
# or bind locally:
comfy --workspace=~/comfy/sadtalker launch -- --listen 127.0.0.1 --port 8190

```

CLI flags `--listen` and `--port` are standard. ([Comfy Docs](https://docs.comfy.org/comfy-cli/reference "Reference"))

# Running two ComfyUIs on one GPU without stepping on each other

- **It works, but VRAM is first-come, first-served.** One instance doing a large render can starve the second. On a single GPU, prefer one heavy job at a time. Monitor with `nvidia-smi`. PyTorch allocators do not “pool VRAM” across processes. ([PyTorch Forums](https://discuss.pytorch.org/t/cuda-out-of-memory-error-when-using-multi-gpu/72333 "CUDA: Out of memory error when using multi-gpu"))

- **Pin by GPU on multi-GPU hosts.** Run one instance per GPU. Use ComfyUI’s device flag or environment variable:

- **Reserve headroom if needed.** Some builds support `--reserve-vram` to keep a margin for the OS/encoders, but behavior varies; test on your driver.

- **Production pattern:** one ComfyUI process per GPU, each with its own queue; route jobs externally. There is no fair-share scheduler inside a single process.

# Quick health checks

```bash
# In the second venv/workspace
python - << 'PY'
import torch, os
print("CUDA available:", torch.cuda.is_available(), "CUDA:", torch.version.cuda)
print("VISIBLE:", os.environ.get("CUDA_VISIBLE_DEVICES"))
PY

# Confirm nodes are registered
grep -E "custom_nodes|IMPORT FAILED" -n ~/comfy/sadtalker/ComfyUI/log* || true

```

Install PyTorch wheels that match CUDA 12.x if you haven’t already. Verify `torch.cuda.is_available()` is True. ([GitHub](https://github.com/Comfy-Org/comfy-cli "Comfy-Org/comfy-cli: Command Line Interface for ..."))

# Summary

- Two ComfyUIs can run at once. Use different venvs, folders, and ports. Queue contention and VRAM are the limits on one GPU. ([Reddit](https://www.reddit.com/r/comfyui/comments/15jxydu/comfyui_command_line_arguments_informational/ "ComfyUI Command Line Arguments: Informational"))
- In the new workspace, install the **Comfyui-SadTalker** node, VideoHelperSuite, and Show-Text; then create or symlink the **checkpoints** and **gfpgan/weights** directories. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "haomole/Comfyui-SadTalker"))
- For multi-user reliability, prefer “one process per GPU” and route jobs; ComfyUI does not share VRAM or schedule fairly by itself.

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 15, 2025, 5:55am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F18 "2025-11-15T05:55:47Z")

</div>

Hello,  
I copied the files:

```auto
$ ls ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker/SadTalker/checkpoints
mapping_00109-model.pth.tar mapping_00229-model.pth.tar SadTalker_V0.0.2_256.safetensors SadTalker_V0.0.2_512.safetensors
$
$ ls ~/comfy/sadtalker/ComfyUI/gfpgan/weights
alignment_WFLW_4HG.pth detection_Resnet50_Final.pth GFPGANv1.4.pth parsing_parsenet.pth

```

And I installed the following sections through Custom Node Manager:

```auto
ComfyUI-VideoHelperSuite
ComfyUI-Custom-Scripts
ComfyUI-Show-Text

```

But I got the same error as before:

 ![SadTalker](https://us1.discourse-cdn.com/hellohellohello/original/3X/f/3/f36f0ccfb8f1189204ae0ea84d418235c198752c.png)

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 15, 2025, 1:35pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F19 "2025-11-15T13:35:33Z")

</div>

I don’t really know about ComfyUI errors… Anyway, since it’s not behaving as expected, it seems best to isolate the problem first.

In cases like this, there’s usually a pitfall somewhere unrelated, and we’re falling into it…

* * *

You already did the “data” part correctly (checkpoints + GFPGAN weights).  
The remaining problem is **code** , not files: the SadTalker plugin itself is still not loading, so ComfyUI never registers these node types:

- `SadTalker`
- `ShowAudio`
- `LoadRefVideo`
- `ShowVideo`

Copying model files does not affect that. To isolate and fix this, you want to debug **plugin import** step-by-step.

Below is a safe, beginner-friendly debugging procedure.

* * *

## 1. Understand what the popup actually means

When ComfyUI shows:

> “Some Nodes Are Missing … SadTalker, ShowAudio, LoadRefVideo, ShowVideo”

it means:

- On startup, ComfyUI **did not register any node with those names**.

- That happens only if:

The official advice from ComfyUI docs and the SadTalker Reddit thread is:  
**look at the terminal and find the import error for that custom node.** ([ComfyUI](https://docs.comfy.org/troubleshooting/overview "How to Troubleshoot and Solve ComfyUI Issues"))

The checkpoints/weights are used later, at runtime. They do not affect whether the node exists or not.

* * *

## 2. Make sure you’re in the right ComfyUI + venv

You now have two installs. For debugging, focus on **only the new one**.

```bash
# 1) activate the venv you created for the new ComfyUI
source ~/comfy/comfy-env/bin/activate # adjust if your venv path is different

# 2) go to the new workspace
cd ~/comfy/sadtalker/ComfyUI

```

From now on, **every** `pip install` and **every** `comfy launch` should be run with this venv active.

* * *

## 3. Confirm the plugin folder is correct

Still in that directory:

```bash
cd ~/comfy/sadtalker/ComfyUI/custom_nodes
ls

```

You should see `Comfyui-SadTalker` in the list.

Then:

```bash
ls Comfyui-SadTalker

```

You should see (at least):

- `SadTalker/`
- `nodes/`
- `web/`
- `workflow/`
- ` __init__.py`
- `requirements.txt`

This is the layout from the official repo. ([GitHub](https://github.com/haomole/Comfyui-SadTalker "GitHub - haomole/Comfyui-SadTalker: Comfyui-SadTalker"))

If something big is missing (for example ` __init__.py` or `nodes/`), delete the folder and re-clone:

```bash
rm -rf Comfyui-SadTalker
git clone https://github.com/haomole/Comfyui-SadTalker.git

```

Your checkpoints/weights paths are already correct and can stay as they are; they live under that folder.

* * *

## 4. Start ComfyUI from the terminal and capture the _real_ error

Now run ComfyUI **from the terminal** , not from a desktop launcher:

```bash
# venv should still be active
cd ~/comfy/sadtalker
comfy --workspace=~/comfy/sadtalker launch -- --listen 127.0.0.1 --port 8190

```

On startup you will see a list like:

```plaintext
0.0 seconds: .../custom_nodes/comfyui-videohelpersuite
0.0 seconds: .../custom_nodes/ComfyUI-Show-Text
0.0 seconds (IMPORT FAILED): .../custom_nodes/Comfyui-SadTalker <-- problem
...

```

Right **above** the `(IMPORT FAILED)` line you will see a Python traceback. For this plugin, a very common one is:

```plaintext
ComfyUI/custom_nodes/Comfyui-SadTalker module for custom nodes:
No module named 'moviepy.editor'

```

This exact case is reported in a SadTalker ComfyUI Reddit thread with the same “Missing Node Types: SadTalker, ShowAudio, LoadRefVideo, ShowVideo” error. ([Reddit](https://www.reddit.com/r/comfyui/comments/1hfsii6/missing_node_types_in_comfyui_sadtalker/ "Missing Node Types in ComfyUI SadTalker Integration : r/comfyui"))

Whatever text you see just above `(IMPORT FAILED)` tells you **which dependency is missing**.

Think of this as “find the first red `(IMPORT FAILED)` line; read the line or two above; that string is what you must fix”.

* * *

## 5. Install the missing Python dependency in this venv

### 5-A. If the error mentions `moviepy.editor`

This is the most common one:

```plaintext
No module named 'moviepy.editor'

```

Install the exact version the Reddit thread recommends **inside your ComfyUI venv** :

```bash
# venv: comfy-env must be active
cd ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker
python -m pip install moviepy==1.0.3

```

That thread solved the “missing node types” problem by doing exactly this, but using the ComfyUI Python executable on Windows instead; on Linux it’s the same equivalent idea: install `moviepy` into the ComfyUI environment, not system Python. ([Reddit](https://www.reddit.com/r/comfyui/comments/1hfsii6/missing_node_types_in_comfyui_sadtalker/ "Missing Node Types in ComfyUI SadTalker Integration : r/comfyui"))

### 5-B. If the error mentions some other module

For example:

- `No module named 'librosa'`
- `No module named 'soundfile'`
- `No module named 'imageio_ffmpeg'`

Then:

```bash
python -m pip install librosa soundfile imageio[ffmpeg]

```

Or, to be safe, you can use the plugin’s `requirements.txt` in this venv:

```bash
cd ~/comfy/sadtalker/ComfyUI/custom_nodes/Comfyui-SadTalker
python -m pip install -r requirements.txt

```

This file is provided by the plugin author for exactly this purpose. ([GitHub](https://github.com/haomole/Comfyui-SadTalker/blob/main/requirements.txt "Comfyui-SadTalker/requirements.txt at main · haomole/Comfyui-SadTalker · GitHub"))

If `pip install -r` ever fails again, install whatever module it complains about manually (same venv), then retry.

* * *

## 6. Restart ComfyUI and re-check the import line

After installing dependencies:

```bash
cd ~/comfy/sadtalker
comfy --workspace=~/comfy/sadtalker launch -- --listen 127.0.0.1 --port 8190

```

Check the “Import times for custom nodes” section again. You want to see:

```plaintext
0.0 seconds: .../custom_nodes/Comfyui-SadTalker

```

(without `(IMPORT FAILED)` and without a traceback above it).

Official ComfyUI troubleshooting docs also say: if you suspect a custom node, disable others and then re-enable half at a time until you find the broken one. In your case, we already know the broken one (Comfyui-SadTalker), so you use the same idea but focused: **fix whatever import error that node prints until it no longer fails.** ([ComfyUI](https://docs.comfy.org/troubleshooting/overview "How to Troubleshoot and Solve ComfyUI Issues"))

* * *

## 7. Verify in the UI that the nodes now exist

Once Comfyui-SadTalker imports cleanly:

1. Open ComfyUI in your browser on port 8190.
2. Right-click on the canvas, or use the node search.
3. Type `SadTalker`.

If the plugin loaded, you should see:

- `SadTalker`
- `ShowAudio`
- `LoadRefVideo`
- `ShowVideo`

and be able to add them to the graph. These node names are defined by this plugin and documented on comfyai.run’s node pages. ([ComfyAI](https://comfyai.run/documentation/ShowVideo "ShowVideo Node Documentation (Comfyui-SadTalker)"))

If you can add them manually, loading the workflow will no longer show the “Some Nodes Are Missing” dialog.

* * *

## 8. Optional: isolate with “only one node pack active”

If you ever suspect that a different custom node is interfering (rare, but possible):

1. Temporarily **rename** other custom node folders:

2. Restart ComfyUI and see if Comfyui-SadTalker still says `(IMPORT FAILED)`.

This is the same “binary search on custom nodes” method the official docs recommend, just simplified to “test SadTalker alone first”. ([ComfyUI](https://docs.comfy.org/troubleshooting/custom-node-issues "How to Troubleshoot and Solve ComfyUI Issues"))

If it loads fine alone, then some other pack is conflicting and you can re-enable them one by one.

* * *

## 9. Mental model summary (beginner-safe)

- **The popup cares about node classes, not model files.**  
Until Comfyui-SadTalker imports successfully, `SadTalker` / `ShowAudio` / `LoadRefVideo` / `ShowVideo` do not exist at all.

- **Your checkpoints and GFPGAN weights are correct.**  
Those matter later, when the node runs. They will not fix a missing-node error.

- **Isolation recipe:**

Once that import line is clean, your SadTalker workflow should load without any “Some Nodes Are Missing” dialog.

---

<div class="post-metadata">

**Author:** ![Vihaananand](https://avatars.discourse-cdn.com/v4/letter/v/47e85d/32.png) [@Vihaananand](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FVihaananand)%5C
**Post date:** [November 17, 2025, 5:43am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105%2F20 "2025-11-17T05:43:28Z")

</div>

Hello,  
Please take a look at this:

```auto
(comfy-env) sadtalker@LocalAI:~/comfy/sadtalker/ComfyUI$ cd ~/comfy/sadtalker/ComfyUI/custom_nodes
(comfy-env) sadtalker@LocalAI:~/comfy/sadtalker/ComfyUI/custom_nodes$ ls
Comfyui-SadTalker
(comfy-env) sadtalker@LocalAI:~/comfy/sadtalker/ComfyUI/custom_nodes$ ls Comfyui-SadTalker
SadTalker

```

I went into the `SadTalker` directory and the `checkpoints` directory was there.

[Next page](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsadtalker-and-nvidia-geforce-rtx-5060-ti%2F170105.md%3Fpage%3D2)
