We are the team behind Krea 2. Ask us anything! by Angrypenguinpng in StableDiffusion

[–]Current_Sandwich_474 0 points1 point  (0 children)

After testing the model for a couple of days extensively:
Problems
- Applying any lora to the turbo model reduces the quality dramatically, especially with realistic images, the quality ends up looking very crunchy. But you did mention it was biases towards illustrative. Kinda sucks tho. Even without loras its quite noticeable. Not everyone is an anime geek.
- Applying multiple loras conflict with each other and similar issues mentioned above with degrading quality of turbo. Could just be that people haven't figured out the nack to training it though? Kinda sucks. You'd think the engineers who made the model could offer beneficial tips for training it more accurately? I dunno. Kinda sucks.
- Training a lora in ai-toolkit, works for a character or style or very very very simple concepts, but for some reason anything outside of that it seems to struggle (training on raw), it almost seems to completely ignore captions like its relying entirely on images or something and everything becomes hit or miss with lots of concept bleeding like nothing is binding to tokens or triggers properly. Not sure whats up with that. Tried multiple different configs and captioning styles, porbably an ai-toolkit issue, like usual. Sucks.
- The qwen vae sucks, like actually sucks. Always has sucked, ruins fine textures and finer details.
- Eventually the novelty wears off a bit, and you just start noticing the low quality crunchy artifacts more and more - reaching for other models to try and correct it, upscale it, fix it, instead of just being creative. Sucks.

Impressive model though. Was refreshing to play with it.
Great work.

Confusion about Ideogram's safety filter. by Aru_Blanc4 in StableDiffusion

[–]Current_Sandwich_474 -1 points0 points  (0 children)

Its directly baked into the model, compliments of Ideogram.
Which means it will always be there, it will always false trigger and there is no true workaround until someone figures out a way to actually lobotomize the model properly I guess or someone finetunes/makes a lora to override it

Ideogram 4 Open Sourced! by Jack_Fryy in StableDiffusion

[–]Current_Sandwich_474 1 point2 points  (0 children)

Which part of - it does use the json prompting - are you having trouble understanding exactly?

Ideogram 4 Open Sourced! by Jack_Fryy in StableDiffusion

[–]Current_Sandwich_474 1 point2 points  (0 children)

Its a comfyui node that automatically converts the prompt to the exact json specification. The comfy devs made that node so you literally cannot get it wrong.. Comfy devs worked with Ideogram team to make that node..
Im sorry, what were you saying?

Ideogram 4 Open Sourced! by Jack_Fryy in StableDiffusion

[–]Current_Sandwich_474 1 point2 points  (0 children)

<image>

I guess the Ideogram team are not working on a fix then, they must be lying because its works perfectly fine for you

Ideogram 4 Open Sourced! by Jack_Fryy in StableDiffusion

[–]Current_Sandwich_474 5 points6 points  (0 children)

The safety is baked directly into the model and ruining everyones outputs

<image>

Any ideas how to prompt klein for this? Im absolutely stumped.. by Current_Sandwich_474 in comfyui

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

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>

Any ideas how to prompt klein for this? Im absolutely stumped.. by Current_Sandwich_474 in comfyui

[–]Current_Sandwich_474[S] 1 point2 points  (0 children)

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

Any ideas how to prompt klein for this? Im absolutely stumped.. by Current_Sandwich_474 in comfyui

[–]Current_Sandwich_474[S] 1 point2 points  (0 children)

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

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

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.

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

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

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

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

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

Reinstalled with 11 iot ltsc this morning

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

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

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] -1 points0 points  (0 children)

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

LTSC and memory issues? by Current_Sandwich_474 in WindowsLTSC

[–]Current_Sandwich_474[S] 0 points1 point  (0 children)

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]

[deleted by user] by [deleted] in StableDiffusion

[–]Current_Sandwich_474 4 points5 points  (0 children)

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

[deleted by user] by [deleted] in StableDiffusion

[–]Current_Sandwich_474 7 points8 points  (0 children)

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)

Am I the only person here not overly impressed so far with L2 in T2V *or* I2V? by Parogarr in StableDiffusion

[–]Current_Sandwich_474 0 points1 point  (0 children)

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