<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
    <channel>
        <title>Lowyat.NET: Latest topics by cloudgpu</title>
        <description></description>
        <link>http://forum.lowyat.net/</link>
        <lastBuildDate>Tue, 10 Nov 2026 17:57:11 +0800</lastBuildDate>
        <generator>FeedCreator 1.7.2</generator>
        <item>
            <title>What I would keep after a ComfyUI render session</title>
            <link>http://forum.lowyat.net/topic/5583016</link>
            <description>I work on CloudGPU. One practical habit for short-drama work is to treat every accepted shot as a small handoff folder, rather than keeping only the final video.&lt;br /&gt;&lt;br /&gt;I would put the clip, workflow JSON, input filenames, content hashes and a brief review note together. Give each shot and take unique names. Reusing a character filename across queued shots can make it hard to know which image a workflow actually read.&lt;br /&gt;&lt;br /&gt;Before ending a rented session, check that the downloaded clips open in the editor and that the expected number of files is present. A remote success message does not establish that the local transfer completed. Keep partial takes separate from accepted ones so that a later batch does not accidentally replace an approved edit.&lt;br /&gt;&lt;br /&gt;For a first batch, agree on one small set of shots and a stopping condition. Review those files before committing to another batch. Which other files do you keep with a take so that a different editor can recover it?</description>
            <author>cloudgpu</author>
            <category>Software</category>
            <pubDate>Mon, 09 Nov 2026 20:09:20 +0800</pubDate>
        </item>
    </channel>
</rss>
