ComfyUI Node

TS Studio Output

The node that tells TS Image Studio 'this run is done'

By AlexYez·Created 2 years ago·Updated about 20 hours ago· 12
TS Studio Output
  • image
    filename_prefixts_studio/session
    folderoutput
    studio_state

    Every backend workflow for TS Image Studio ends the same way: at a TS_StudioOutput marker. It's THE result node of the backend - the one whose image the studio treats as the finished output. When it runs, it saves the image under the studio's session prefix and reports back through the executed event. That report is how the studio's gallery learns a run finished and can show the result. One per workflow. That's the contract.

    This matters more than it sounds, because it's also the node that decides what counts as the result. You can have debug SaveImage nodes scattered through a backend - the studio ignores them. Only the image that lands in TS_StudioOutput becomes the session result. If you're authoring a backend and the gallery shows nothing, this is the first place to look: is the final image actually wired into this node?

    The inputs that matter

    • image - the final image of the backend workflow. Wire the end of your generation chain here.
    • filename_prefix - where the file lands, default ts_studio/session. The studio sets this per session, so you usually don't touch it; running the workflow by hand, you'd change it so your test renders don't collide with studio sessions.
    • folder - output or temp. This one's genuinely useful, because the distinction is about your sanity: output is the library, what you keep. temp is a draft - it still comes back to the studio and its session strip, but it never joins the library. So a dozen tries at one repaint don't bury the one picture you actually wanted. Use temp for iterations, output for the keeper.
    • studio_state - a JSON snapshot of the studio run. The studio fills this in and it gets saved into the PNG's ts_studio text chunk, alongside the standard prompt/workflow metadata, so the exact session can be recreated from the image later. Leave it empty when running the workflow by hand.

    There are no outputs - this is an output node, the end of the line.

    Installing it

    It ships in comfyui-timesaver: ComfyUI Manager → search Timesaver, or

    cd ComfyUI/custom_nodes
    git clone https://github.com/AlexYez/comfyui-timesaver
    cd comfyui-timesaver
    python -m pip install -r requirements.txt
    

    then restart ComfyUI.

    Gotchas

    Two, both real. First: if you drop one of these into a normal graph that has nothing to do with the studio, it still works as a save node - it just saves an image with a prefix. Nothing breaks, but a regular SaveImage is the better tool there. Second: the "one per workflow" rule is hard. Multiple TS_StudioOutput markers and the studio can't tell which result to show. And a small nicety that says a lot about this pack's attention to detail - since the ts_studio chunk rides in its own extra_pnginfo slot, it doesn't collide with ComfyUI's own or Artius's metadata. The pack is built on the V3 API (comfy_api.v0_0_2), pinned so these markers keep loading across updates.

    CategoryTS/Studio

    Inputs (4)

    NameTypeDefaultDescription
    imageIMAGEThe final image of the backend workflow.
    filename_prefixSTRINGts_studio/sessionSave path prefix under output/. The studio sets it per session.
    folderoptCOMBOoutputWhere the result lands. 'output' is the library — what the person keeps. 'temp' is a draft: it still comes back to the studio and its session strip, but never joins the library, so a dozen tries at one repaint do not bury the one picture that was wanted.
    studio_stateoptSTRINGJSON snapshot of the studio run, saved into the PNG's 'ts_studio' text chunk so the studio can recreate the exact session from the image. The studio fills it in; leave it empty when running the workflow by hand.

    Outputs (0)

    No outputs