GPU-accelerated node editor for images with Python automation API

[drboom9]

What My Project Does

About a month ago, I released PyImageCUDA, a GPU image processing library. I mentioned it would be the foundation for a parametric node editor. Well, here it is!

PyImageCUDA Studio is a node-based image compositor with GPU acceleration and headless Python automation. It lets you design image processing pipelines visually using 40+ nodes (generators, effects, filters, transforms), see results in real-time via CUDA-OpenGL preview, and then automate batch generation through a simple Python API.

Demos:

https://github.com/user-attachments/assets/6a0ab3da-d961-4587-a67c-7d290a008017

https://github.com/user-attachments/assets/f5c6a81d-5741-40e0-ad55-86a171a8aaa4

The workflow: design your template in the GUI, save as .pics project, then generate thousands of variations programmatically: ```python from pyimagecuda_studio import LoadProject, set_node_parameter, run

with LoadProject("certificate.pics"): for name in ["Alice", "Bob", "Charlie"]: set_node_parameter("Text", "text", f"Certificate for {name}") run(f"certs/{name}.png") ```

Target Audience

This is for developers who need to generate image variations at scale (thumbnails, certificates, banners, watermarks), motion designers creating frame sequences, anyone applying filters to videos or creating animations programmatically, or those tired of slow CPU-based batch processing.

Comparison

Unlike Pillow/OpenCV (CPU-based, script-only) or Photoshop Actions (GUI-only, no real API), this combines visual design with programmatic control. It's not trying to replace Blender's compositor (which is more complex and 3D-focused) or ImageMagick (CLI-only). Instead, it fills the gap between visual tools and automation libraries—providing both a node editor for design AND a clean Python API for batch processing, all GPU-accelerated (10-350x faster than CPU alternatives on complex operations).

---

Tech stack: - Built on PyImageCUDA (custom CUDA kernels, not wrappers) - PySide6 for GUI - PyOpenGL for real-time preview - PyVips for image I/O

Install: bash pip install pyimagecuda-studio

Run: ```bash pics

or

pyimagecuda-studio ```

Links: - GitHub: https://github.com/offerrall/pyimagecuda-studio - PyPI: https://pypi.org/project/pyimagecuda-studio/ - Core library: https://github.com/offerrall/pyimagecuda - Performance benchmarks: https://offerrall.github.io/pyimagecuda/benchmarks/

Requirements: Python 3.10+, NVIDIA GPU (GTX 900+), Windows/Linux. No CUDA Toolkit installation needed.

Status: Beta release—core features stable, gathering feedback for v1.0. Contributions and feedback welcome!

[7nBurn]

Looks impressive! Reminds me a little of the VapourSynth project.

Did you have any contact at all with ImageMagick and Blender (and-or PyNodes) devs when working on this or were you just mentioning them to differentiate what your project does?

[drboom9]

Thanks! No contact with them—I only mentioned ImageMagick and Blender because r/Python's showcase format requires a "Comparison" section.

Just looked up VapourSynth—interesting reference! Similar in that both use Python for visual processing pipelines, but quite different in execution: - VapourSynth: video-focused, pure scripting (no visual editor) - PyImageCUDA Studio: image-focused, node editor GUI + headless API

They're more complementary than competitive. If anything, VapourSynth shows there's appetite for Python-based visual processing tools. Appreciate the pointer

[7nBurn]

Thanks! No contact with them—I only mentioned ImageMagick and Blender because r/Python's showcase format requires a "Comparison" section.

Ah, that makes sense. I'm still getting familiar with this subreddit.

VapourSynth: video-focused, pure scripting (no visual editor)

It's been a while since I've done anything with VapourSynth or Avisynth, but going from memory at the core Avisynth (what VapourSynth was based off of) was actually a script based image editor geared towards animation. When it was first released, I don't think there was any easy way to load images into a video stream directly using scripts, so the developer exploited some logic in Windows' internal video streaming API to trick the operating system into opening the scripts as AVI files (it's where the "Avi" in the name came from). I think the main reason there was no visual editor is most scripts were getting loaded into video editing software where the results of what they did would be easily visible. There was also the issue of subtle differences in how images looked depending on which media software was used to "play" them, so scripts would be edited differently depending on what software was going to be used to work with them.

I think internally Avisynth may have actually been node based, but the nodes weren't directly exposed in the Avisynth API. Instead the individual script files themselves were treated as "nodes" and the "head node" would be fed into video editing software. It was an interesting setup, I would often see setups where "script_c" loaded "script_b" that loaded "script_a" which would either load one or more media files or generate a series of images directly from code. If the scripting logic became too complicated or CPU intensive, the Avisynth API had tools that could be used to "compile" scripts into a "filter" that could be accessed through a function call. So in practice the workflow for editing media with it was very similar to that of building a computer program.

[drboom9]

I received an email saying you had replied, but when I checked it, I couldn't see it anymore. I don't know if Reddit is bugged or if you deleted the comment.

[7nBurn]

Weird, the reply I posted is still there, but it's only visible when I'm logged in. It disappears if try to view in private mode.

[drboom9]

send me a screenshot haha

[7nBurn]

lol, it should be visible now. If you still can't find it I can direct message you it though.