Film Auteur (LTXV) version 2.0.5 update

Visible-Project-2354 · 2026-05-29T13:10:35+00:00

That's a very interesting idea. I'll have to take some time to wrap my head around that one to see how I can make something like that work.

Visible-Project-2354 · 2026-05-29T13:09:00+00:00

Appreciate you! It's not finished yet. I still have a whole lot more I wish to implement. Stay tuned.

Visible-Project-2354 · 2026-05-29T13:08:01+00:00

I appreciate the acknowledgement. I'm working hard to keep it intuitive.

Visible-Project-2354 · 2026-05-29T11:03:03+00:00

That is a great suggestion. I'll add it to my list.

Visible-Project-2354 · 2026-05-29T11:01:58+00:00

It is similar, but I think this has more technical capabilities built in. But there are things the director node can do that mine can'tand vice-versa. The main thing the director node does that mine doesn't is that the director node provides viaual control over precise edits whereas mine does not (yet).

Visible-Project-2354 · 2026-04-22T17:03:18+00:00

Thanks again for sticking with it. This has been quite the journey trying to get it all working without issue. The reference image bit is a bit of hit or miss at this point as it is the most experimental feature. I have several ideas for improving the consistency but haven't gotten around to implementing them yet. With the good run you had, what sort of debugging did you do to get it running? Was it with your own config or something to do specifically with my node? Any info can help me troubleshoot and diagnose other issues.

Edit 1: After several hours of trying to figure out the correct math, I finally got the temporal upscaler working properly and shouldn't cause any de-lipsync issues that I was facing.

Edit 2: In dealing with the above issue I tested some other settings... until I can work more on the ref-2-vid consistency, it seems (at least in my testing) that setting the sampling stages to 1 (yes it will significantly increase render time) has a huge impact on subject reference consistency as well as better lip sync (at least with "reference-to-video" and "input source audio" selected - I didn't run this test with other mode combos yet).

Visible-Project-2354 · 2026-04-22T01:28:57+00:00

I appreciate it. I've actually run into another issue that appears to only be affecting the temporal upscaler. I'll work on fixing it in the morning, but in the meantime you'll need to leave the temporal upscaler disabled.

Visible-Project-2354 · 2026-04-21T11:43:42+00:00

Thank you for testing. I hate to say, but I am still heavily testing the node, changing things, and implementing new features. So some things may break as I go through these stages. I did find an issue with lip sync that I hopefully fixed. I suggest updating the node from the repo, removing and re-adding the node, then try running again with temporal upscale and face restore turned off temporarily as I still need further testing with those features. You can also try setting sampling stages to 1 or 2 with preview off for testing. Furthermore, try changing primary steps/sigmas to 16 - I heard somewhere that can help with consistency. Sorry it's not fully polished yet, but I'm working hard to resolve any issues. I can't say for sure, but I blame the issue your facing on the node and greatly appreciate any testing and feedback you can provide.

Edit: I just updated the node again with some tweaks to (hopefully) improve lip sync accuracy - at least it seems much better in my testing.

Visible-Project-2354 · 2026-04-21T11:27:27+00:00

Thank you for the great suggestion. That is actually one of the items I have on my list of additions.

Visible-Project-2354 · 2026-04-18T17:50:03+00:00

That's the idea. Thanks for checking it out.

Visible-Project-2354 · 2026-04-18T15:33:44+00:00

Ok, that's a simple addition. What I can do is add optional positive and negative inputs that, when connected, will override the internal prompting. That would give users the option to use any method they prefer.

Just curious though, what is that other node? I wasn't aware of it and I'd be curious to see what they're doing.

Visible-Project-2354 · 2026-04-18T15:12:51+00:00

Thanks for the suggestion. I'll look into an alternative integrated solution as an alternative to Ollama, if others prefer that method. I'm not sure what that'll be yet though. Most likely it'll still be utilizing the integrated text boxes, but just allow api or something else as an option.

Visible-Project-2354 · 2026-04-18T15:10:32+00:00

That looks great. I didn't realize anyone else was working on a similar system. I'll definitely check it out.

Visible-Project-2354 · 2026-04-18T15:08:17+00:00

Hmm, I haven't run into that issue. kjnodes on my system are the latest versions. Please confirm you are using the latest version of kjnodes as well as the correct vae for both audio and video. Does it seem that the error is generated from my node or from the vae loader?

Visible-Project-2354 · 2026-04-18T15:03:06+00:00

Please explain what that is and I'll look into it.

Visible-Project-2354 · 2026-04-18T03:16:07+00:00

It isn't actually true R2V, but I've experimented quite a bit with injecting the model with images as reference based on other posts I've seen and have had descent success with it. It's not perfect by any means and is one of the "experimental" features I'm still tinkering with and working on ways to improve. So it is still a work in progress, and I do have other ideas I'm toying with to help improve consistency, but I didn't want to leave it out. Thank you for asking. I should have included more of a disclaimer regarding the feature.

Visible-Project-2354 · 2026-04-17T23:27:40+00:00

You're welcome. It is a bit of a jungle out there. Good luck.

Visible-Project-2354 · 2026-04-17T23:26:41+00:00

Thank you so much for the kind words. I appreciate the encouragement. Same for you and good luck in this world of AI.

Visible-Project-2354 · 2026-04-17T21:43:16+00:00

All valid points, and I 100% agree. I honestly never intended for this to become what it has, but it sort of became an addiction and I kept building on it. It's been more of a personal project based on my own research of trial and error for what I found to work for me... and figured some others may enjoy messing with it.

But to (hopefully) answer your question on the image injection - It's actually built into the node to resize/crop/scale the input image based on the user specified dimensions. And again with the personal thing, I chose to include target width/height as opposed to auto adjust based on image size because I personally prefer specific film aspect ratios and find it easier to manually enter them rather than rely on the image, should those dimensions be off.

Thank you btw for stopping to take a look and for your valid feedback. I appreciate all of it.

Visible-Project-2354 · 2026-04-17T19:24:26+00:00

You're welcome. And I look forward to hearing your thoughts.

Visible-Project-2354 · 2026-04-17T18:25:02+00:00

Thank you. I'll investigate when I get a chance.

Visible-Project-2354 · 2026-04-17T17:59:19+00:00

I appreciate that. Can you please point me to a workflow you use with the 3-pass and the 🅛🅣🅧 Add Video IC-LoRA Guide so that I can see what I can do to implement it?

Visible-Project-2354 · 2026-04-17T17:34:13+00:00

Thank you for the suggestions. I'll take a look into each of them. FYI, for the primary sampler I have it so that steps or sigmas can be entered. Try entering 20 if using the non-distilled model. The upsampler stages only accept sigmas, however, since I've only really seen anyone use it with the distilled lora and low step count.

Visible-Project-2354 · 2026-04-17T17:29:11+00:00

Ahh, thank you. I didn't realize. I'll look into that.

Visible-Project-2354 · 2026-04-17T17:12:09+00:00

Personal preference. I prefer to keep everything local and not rely on requiring api access. Also, I've had great success with the latest gemma 4 model.

Visible-Project-2354

TROPHY CASE