-
-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Environment
- OS: Windows 10 x64
- GPU: NVIDIA RTX 3070 8 GB (Studio Driver, latest)
- DaVinci Resolve: 20.3 Free
- Python: 3.10.11 (installed from python.org)
- Rembg-Fuse: latest commit / latest release at the time of writing
What I did
- Installed Python 3.10.11 and added it to PATH.
- Downloaded the Rembg-Fuse repo and copied the
Rembgfolder to the Fuses path shown in Fusion Settings → Path Map → Fuses. - Restarted Resolve, opened the Fusion page and added the Rembg node with
MediaIn → Rembg → MediaOut. - Clicked Open Setup in the Inspector and first tried GPU (CUDA), later also tried the “CPU / Standard” option.
- Installed rembg and the models as requested by the setup tool.
What happens
Every time I try to use the Rembg node on a clip (video or still), Resolve’s console shows this error:
Failed to save input image to: C:\Users\samyv\AppData\Local\Temp\\rembg_input_0.jpg
The node never processes the frame. The important part is that the path shows a double backslash \\ before the filename, and the file is never written in the Temp folder.
Things I already tried:
- Run Resolve as Administrator.
- Clear
%TEMP%and also try a custom temp folder likeC:\RembgTempwith full permissions. - Verify from the Resolve Python console that
os.environ["TEMP"]is correct. - Reinstall Python and rembg several times (CPU‑only and GPU versions).
- Test rembg from the command line: with Python 3.10.11 and
onnxruntime(CPU only), the command
rembg i entrada.png salida.png
works perfectly and returns a PNG with the background removed.
So rembg itself is working fine on this machine; the problem only appears inside DaVinci Resolve through the fuse.
Expected behavior
The fuse should be able to save the temp input image (e.g. rembg_input_0.jpg) in the Temp folder and pass it to rembg, so the node can process each frame of the video.
Notes
- I also hit the CUDA / cuDNN DLL errors that are mentioned in Issue CPU used instead of GPU #1 when trying the GPU option, but even after switching to CPU‑only rembg (no onnxruntime‑gpu installed), this specific error about failing to save
rembg_input_0.jpgpersists. - It looks like there might be a Windows‑specific bug in how the fuse builds or writes the temp path (the
\\in the path and the consistent failure to create the file).
If you need logs or extra tests, I can provide them.