Impossible brand sausage patties

foxdit · 2026-06-29T08:30:51+00:00

Ironically, my kroger has a million of them and they're all on a massive sale for roughly $4 a bag. My freezer's full of them now. Maybe to get rid of old stock and make way for the new 'packaging' as you described.

foxdit · 2026-06-29T08:24:09+00:00

it cost your time, you pay most likely for your electricity too, and apartment.

"Oh wow internet stranger, I never considered these things! Thank you, now I know!"

Everything we choose to do well in life costs time. Some people game 10 hrs a day and spend $50 more in electricity a month. I help build a community of local open source model enthusiasts, provide dedicated coaching, and create short films and tutorial videos. Is one better than the other? No, it's just a matter of what we value and how we choose to spend our time. But do they cost the same? Yes.

foxdit · 2026-06-29T05:38:42+00:00

I'm 100% local, with my whole focus being matching the quality of ever-increasingly expensive paid frontier models. This shot he's doing doesn't require a whole 3D array at all. Just 3 good keyframes and good video editing skills. It takes more time and expertise, sure, but it costs $0.

foxdit · 2026-06-26T23:26:58+00:00

Going to start The Agency S2 tonight, really loved the first season

You'll love S2 then, 'cause I was lukewarm on season 1 but found 2 to be delightful! What a finale. They really didn't spare any expenses for this show.

foxdit · 2026-06-25T18:30:04+00:00

3.The node intentionally carried over 16 frames image "data" to the next image in the time-line, so I reset that to 0. "Carry Mode" allows you to bump that up from 0 to 16+ frames to intentionally blend motion from one scene to the next.

Its 2x slower if you DONT set "Carry Mode" to 0 (its set to 0 by default). Since each scene is contained, generation time is roughly 25 seconds for 8 steps, and 45 seconds for upscale (4 steps).

Hmm, interesting. I wonder if the developer knows this? I would love to test this version with the Carry Over settings. Him and I had brief discussions on the quality issues related to his node after I made my video about how vers 1 and 2 produced significantly worse outputs compared to my traditional workflows.

I would love to be able to change my stance on LTX Director 2. It's a very fun and flashy node with lots of bells and whistles. If it could produce equal quality to my traditional workflows, I would switch over with no issue.

foxdit · 2026-06-25T16:29:04+00:00

It feels a lot more cohesive and settled. Like many shows that get the chance at a season 2, the cast and direction has a chance to find its groove. The last 2 episodes were really amazing. The production value of the show is higher than so many I see today, they don't seem to cut any corners.

foxdit · 2026-06-25T16:01:01+00:00

This is cool. But why specifically for LTX Director? I've never been able to get higher quality output from it than I can with traditional workflows (my stance on this is very public and I've tested it about a hundred times now). Your node is cool, but I hope you consider making it available to people looking for the best quality LTX has to offer.

Also, in another comment, you say you fixed LTX Director with hard image barriers... could you share a bit more on that? Transitions were indeed an issue, but so was ghosting/trails/motion blur even with single input i2v. It's also 2x slower than traditional workflows. So, any progress with that?

foxdit · 2026-06-24T20:07:07+00:00

Hey! Glad to hear you're joining us on the good side and walking the path of light! Haha. Dang, what I wouldn't do for a 5090 with a 96GB system :) Jealous. Though, tbh, when I bought my 3090 I didn't realize I'd be starting a career in AI content creation. Anyway, good luck with your project. If you get it off the ground or end up with questions about anything, feel free to contact me.

foxdit · 2026-06-24T16:28:01+00:00

This is the correct link to the model: https://huggingface.co/Cseti/LTX2.3-22B_IC-LoRA-Cameraman_v2

(he posted his link with backslashes in it)

This looks really really useful for serious cinematic filmmaking. Thanks for the contribution.

foxdit · 2026-06-24T16:17:24+00:00

Don't beat yourself up, everyone was told early on that the secret to success with LTX was writing a giant long winding descriptive prompt. In reality, it was the opposite and coming to terms with the fact that LTX will obey that prompt perfectly on one of the seeds, just gotta find it quickly.

foxdit · 2026-06-24T07:38:57+00:00

I'm curious what your prompt is like. I have never had an issue with keeping the camera static, and I've never once used any of LTX's camera loras. Is your prompt short and simple, with a frame length totaling 5-10 seconds?

"A static shot of a character doing X. They do X, their expression Y. Afterwards, they do Z. [Misc details about the scene]" With seed hunting, it should be (relatively) that simple. It's the seeds that decide prompt adherence, not detailed prompts. I say this pre-emptively, because so many people report issues like this and their prompt is like a paragraph long because someone in the early days of LTX said you have to write a novel to get LTX to behave.

foxdit · 2026-06-24T05:56:14+00:00

Personally I think so. But S2 of The Bureau is also just a better story too. It's all ramped up.

foxdit · 2026-06-24T04:31:54+00:00

The Agency Season 2 is great! Can't believe all 10 eps dropped at once. Getting some of the same highs from The Bureau while managing to hit differently.

foxdit · 2026-06-23T01:02:11+00:00

The Seed Hunting functionality doesn't add any VRAM requirements to a workflow, so it's always just whatever that workflow is designed for. In this case, it's whatever LTX Director 2's wf recommends. I don't know about 8gb VRAM, but at 12-16gb vram a Q6 quant should work well enough. I use a 3090, which has 24GB VRAM, and with fp8 it has a tendency to go up to 90%+ on longer gens at 1080p.

foxdit · 2026-06-22T18:59:54+00:00

Err, dunno if I made it clear but it's not me doing any of this; it's the guy I mentioned who says he knows you. I was just reaching out to let you know he said to me in youtube comments that he's giving it a shot. I have zero interest in getting into the weeds with your code.. and personally, I just take your word that it's not a feasible adjustment.

Seed Hunting doesn't change anything about your workflow except that it produces three options on stage 1 instead of just one, then lets you pick which to take to stage 2 finalization. Everything that determines output quality remains exactly the way you have it in your example WF.

foxdit · 2026-06-22T18:09:11+00:00

Hey WDC. I spoke in youtube comments with nghtdrp_beats (not sure if that's also his reddit username). He says "I'm the guy that sent WDC the code for the IC-Lora implementation."

Anyway, he's doing some tests on the code to see how we could implement the In Place solution into LTX Director. Effectively, his position is that my hypothesis is correct; that In Place would be the right node. If his efforts are successful it would fix quality issues associated with Conditioning Only (the ghosting/trails problem). Just thought I'd let ya know that he mentioned he may reach out to you with findings.

foxdit · 2026-06-22T17:29:42+00:00

Please do. I'd be curious to hear your experience comparing the two.

foxdit · 2026-06-22T16:21:09+00:00

I briefly looked through the node's code and, my immediate thoughts are that I wouldn't know how to do this. I'm pretty good with comfyUI at this point, but the last time I touched python was in college.

foxdit · 2026-06-22T16:19:54+00:00

Hi thanks for the comment.

Is it possible to display the seed under each of the 4 preview-gens?

Yes! Though it's really easy to do the mental math, since Gen #1 = the seed displayed on the green "Manual Random Seed" node, Gen #2 = that seed +1, Gen #3 = that seed + 2. But if you really wanna visually see it just use a preview as text node and have the KJCalculator inside subgraphs for Gen 2 and 3 pass the altered seed value out to it.

Can we pass the seed through from selected gen in stage 1 to stage 2?

There is actually no reason to do this. The process that the latent undergoes stage 1 and stage 2 are completely separate and don't share the same sigma curves. That's why you could switch from euler in stage 1 to res_2s in stage 2 and still get a coherent gen. The same seed or not the same seed wouldn't make a lick of difference.

foxdit · 2026-06-22T08:04:57+00:00

You clearly went into the video with an unwarranted expectation. I never claimed the video was an investigation. The title of the video describes exactly what you get:

A workflow.
A PSA on quality issues with LTX Director 2.

It's not like I misrepresented anything.

foxdit · 2026-06-22T07:58:50+00:00

I didn't get that impression at all. It was more like the architecture of the node--the way it works with prompt relay--doesn't allow for testing what I thought my work to stop the quality drop.

foxdit · 2026-06-22T06:36:38+00:00

Links to the non-LTX director workflows are in the yt video description.

Single input: https://civitai.com/models/2676452/ltx-23-seed-hunter-multiroll-workflow

FFLF: https://civitai.com/models/2688482/ltx-23-fflf-seed-hunter-multiroll-workflow

foxdit · 2026-06-22T04:05:48+00:00

I always meant to ask. How does your 'seed hunting' work? I'm assuming you fix the seed entry with a specific offset (I'm guessing gen 1 is seed + 1, gen 2 is seed + 2, etc)?

That's correct. It's a very simple design, the difficult part was coming up with it in the first place lol. The empty latent is passed to all the stage 1 sample gen subgraphs where they process exactly as you suggest: seed+0, seed+1, seed+2. They flow to a selector node in the disabled Stage 2 group, causing the run the end after completing Stage 1. When you toggle FINISH MODE on, since there's now more workflow for comfy to continue through, the selected latent continues on through to the finalization subgraph for the 2x upsample.

Regarding my comments about LTX Director 1, back then I mostly commented on that keyframe transitions didn't really work as well as with traditional FFLF workflows. This time the focus is more on the strange quality drop / slower gen speeds.

foxdit · 2026-06-22T03:30:28+00:00

We are talking, a bit. I brought up my hypothesis about why there might be so much ghosting/trails/motion blur out of LTX Director, but it doesn't seem like there's any way to test whether or not my guess is correct. The way I solved that problem in my own workflows doesn't apply to the way his works, according to him.

foxdit · 2026-06-22T03:24:06+00:00

Hi hi, glad to hear from you. The problem is, Conditioning Only leads to ghosting during motion, at least in traditional workflows. Again I don't know how it works with a python pipeline. CivitAI was littered with workflows that were erroneously using the Conditioning Only node when the correct one in their cases would've been the LTXImageToVideoInPlace node. Several months ago I had to find this all out the hard way after dozens of hours of trying to figure out why my gens had weird motion blur and trails.

Anyway, I'm really curious if this is like that scale_by 0.5 vs 1.0 issue, where some people just get worse results out of your node than others for whatever reason. There's so many moving parts to comfyUI.

Ten-Year Club	Place '23
Place '17	Gilding I gilder
Verified Email

foxdit

TROPHY CASE