ComfyUI users document local video setups for LTX2, loops, and TTS

• HyperSpazdik’s loop post found that an LTX2.3 first-frame-last-frame subgraph could loop cleanly when the same image was fed as both the first and final frame.
• The local Camacho workflow packed TTS audio, key-frame face replacement, LTX2 footage generation, and DaVinci Resolve assembly into a fully local pipeline on an 8 GB RTX 3060.
• The inbetweening question framed ComfyUI as a way around online tools that cap animation interpolation at five seconds.
• The workstation build post put local image-to-video for band and music-promo clips inside a $2,700 offline PC budget with an RTX 5070 Ti under consideration.

ComfyUI is showing up less as a one-click video app and more as a patch bay for local motion workflows. One creator’s loop fix came down to a first-frame-last-frame setup, while another creator’s finished scene chained speech generation, masked key frames, LTX2, and editing. The named stack points back to public project anchors like ComfyUI, LTX-Video, and DaVinci Resolve, but the Reddit posts are useful because they show the seams creators are actually fighting.

The original looping attempt had four steps:

1. Run image-to-video with LTX2.3.
2. Save the last frame as an image.
3. Run an LTX2.3 first-frame-last-frame node with that saved frame as the first frame and the original image as the last frame.
4. Merge the two videos.

That produced a visible shift at the join. After fixing the first-frame-last-frame subgraph, HyperSpazdik reported that using the same image as both the first and last frame created the loop.

The clearest finished workflow came from a creator who said the whole clip was made locally on a 3060 with 8 GB VRAM and 48 GB system RAM.

Their pipeline:

1. Sample Camacho addressing Congress, then use the WAV with tts_audio_suite and indexTTS2 in ComfyUI to generate speech audio.
2. Use screen caps, klein9b, and seg3 masking to swap Bill Pullman with Camacho in three key frames.
3. Feed the audio files and key frames into LTX2 to generate footage.
4. Splice the result in DaVinci Resolve.

That is a creator stack, not a model demo: voice, identity swap, video synthesis, then an editor pass.

The talking-character question was narrower than generic AI video. The target was a faceless-video format where an AI character talks to camera in sync with the creator’s own voiceover.

The reference was a YouTube example shared in the post. The open workflow problem: character consistency, camera-facing performance, and voice sync in one repeatable pipeline.

An animator asked for open-source ComfyUI models for inbetweening because online tools generate five-second videos when the job sometimes needs only half a second or one second.

The useful detail is the duration constraint. For animators, the appeal of a custom ComfyUI graph is not just local generation, it is control over the length of the interpolation.

The hardware-shopping post described a basic local offline AI workstation for image-to-video work on band and music-promotion clips.

The constraints were specific:

• 8 to 10 second videos.
• No sound required.
• Roughly $2,700 build budget.
• RTX 5070 Ti suggested by someone else.

That frames local video generation as a production workstation question before it becomes a model comparison.

A separate creator asked for the current local-video realism meta because they were tired of limited cloud-hosted video generators.

That post adds the pressure behind the rest of the thread cluster: local creators are comparing loops, inbetweening, talking characters, hardware, and realism because hosted systems still impose workflow limits.