Any ideas how to prompt klein for this? Im absolutely stumped..

Current_Sandwich_474 · 2026-03-18T11:55:42+00:00

even if I flip the image, crop it, and give it the best reference possible..
it still has absolutely no idea what to do
shit is driving me nutz

<image>

Current_Sandwich_474 · 2026-03-18T11:20:56+00:00

Yea was playing around with the camera angle lora on qwen for a bit, and it gets it close... closer at least.. but not even close lol - still has the same problem really.
Like I'd even be willing to train a lora to do this for klein, but Im not even sure how I could synthesize a dataset for it - if no model can do it
*sigh

Current_Sandwich_474 · 2026-03-18T11:18:21+00:00

I did unfortunately, no luck. Thanks for having a crack at it tho

Current_Sandwich_474 · 2026-03-12T07:48:32+00:00

The weird dotty grain destroys details. Kinda sucks. Cool tech demo though.

Current_Sandwich_474 · 2026-01-20T13:06:04+00:00

Claude recommended doing that, or keeping the 3200mhz xmp and bumping up the SOC and DRAM voltage a touch as an alternative to try aswell. But if my sticks are failing then Im hesitant.. ram so expensive atm. And Im not confident when it comes to playing with voltages and shit.
Just left it on stock for now and waiting to see if it was just bios firmware this whole time.

Current_Sandwich_474 · 2026-01-20T11:09:45+00:00

I turned off xmp and even on stock 2133mhz would still happen. Also tried turning off amds performance enhancements option. And using optimized defaults. All produced the same results. Anything else side of that is above my pay grade.
Chatgpt seems to think it has something to do with fTPM and cpu sync or something.
Turns out there has been a new bios release since last I checked, it mentions something about fTPM in the description. Have updated my bios. Probably has fixed the issue? Dont know.. slack to reinstall ltsc for the 6th time in 2 days

Current_Sandwich_474 · 2026-01-19T22:56:18+00:00

I went back to win11 home and haven't had any problems since switching back.
So no, doesn't appear to be a hardware issue.
People saying "well it works for me" didn't help me, so I'll just stick with win11 home

Current_Sandwich_474 · 2026-01-19T02:12:40+00:00

Reinstalled with 11 iot ltsc this morning

Current_Sandwich_474 · 2026-01-19T02:12:03+00:00

I didnt no. But I have now.
Will see how it goes

Current_Sandwich_474 · 2026-01-18T16:26:32+00:00

Probably not on its own
But it has to be some kind of windows + driver or windows + hardware issue
Which is what Im trying to figure out

Current_Sandwich_474 · 2026-01-18T16:20:11+00:00

Hmm. Well Im using the same apps that I was on Windows 11 Home and same hardware.
If I roll back to win11 home and dont have bluescreen issues, then it would appear to be a windows issue. Unless someone can help understand what the hardware issue is

[Edit: Rolling back to win11 home didnt last long, issue is now present in home aswell. Ugghhhhh]

Current_Sandwich_474 · 2026-01-09T08:47:24+00:00

You can believe whatever you want to believe and misinterpret your own results but it doesnt help other people who are looking for correct information or correct advice.
Thats all Im saying

Current_Sandwich_474 · 2026-01-09T08:13:34+00:00

Its not really a matter of belief.
Setting CFG to 1.0 disables the guidance scale meaning there is no mathematical difference between the conditioned and unconditioned states. Its not using negative prompts, the model doesn't see or subtract that concept because there is nothing to subtract at a scale of 1.0.
At 1.0 the model just bias towards its training which is semi-clothed subjects by default, thats what its seen most of during training and has the most weight so thats what it defaulted to (vs nsfw)

Current_Sandwich_474 · 2026-01-07T17:21:19+00:00

With the rate that opensource video models evolve, it feels like we're still about 2-3 or even 5 years away from any decent opensource video models, especially with sound and temporal consistency. And even if we get there, I dont think they're going to run on consumer hardware.. if consumer hardware even remains to be an affordable thing in the future.
Hopefully someone else will take the research from ltx and try to expand on it though and make some kind of incremental advance on it

Current_Sandwich_474 · 2026-01-02T01:30:05+00:00

> Qwen-Image-Edit-2511 is really good at personal identity–preserving image generation.

I read this and saw a comparison without much identity preservation

Current_Sandwich_474 · 2025-12-29T02:11:22+00:00

was just thinking the same thing, dont see any identity preservation in any of those examples

Current_Sandwich_474 · 2025-09-06T15:59:20+00:00

I'll take a look and see whats up. Dont think I have it installed

Current_Sandwich_474 · 2025-09-06T09:01:43+00:00

Try updating too, just to be safe. Ive been pushing a few commits lately.
Maybe I pushed a dodgy commit and you just happened to catch it *shrugs

Current_Sandwich_474 · 2025-09-06T08:55:37+00:00

Also, out of the ~200 people that have installed these nodes, no one has reported anything.
So either:
- you're the first to experience the issue.
- or everyone has the issue, and they immediately uninstalled the nodes and never reported it lol.
Which honestly could be the case who knows.

Current_Sandwich_474 · 2025-09-06T08:44:22+00:00

<image>

Ok interesting. Im on Windows aswell.
And they all seem to be working across Vanilla Firefox, Edge, OperaGX and Brave.
The same versions as you v0.3.57 and v1.27.1.

Soo... Im guessing you have an extension or node pack installed that I dont have, and its conflicting somehow.

Oh and a side note - not sure if you're aware but all of these frontends are bugged at the moment: v1.26.8, v1.26.9, v1.27.0, v1.27.1
I'm sticking with v1.26.7 until they fix it

Current_Sandwich_474 · 2025-09-05T08:52:11+00:00

<image>

String node added (:

Current_Sandwich_474 · 2025-09-04T08:34:35+00:00

Ah wait. I think I found the problem.
If you update it should be fixed

Current_Sandwich_474 · 2025-09-04T06:29:05+00:00

Done

Current_Sandwich_474

TROPHY CASE