Independant Checkpoint for hires.fix Plus Other Absent Features

[gohan2091]

I'm using SD.Next and my online friend is using A1111. He is able to use a different model checkpoint for his hires.fix than from the first generation. So for example he can use RevAnimated then hires.fix with Realistic Vision all as one process. He showed me a setting to enable this. It appears (unless I've missed it) that this option is absent from SD.Next. Is that correct? Can this feature be added in please?

There were other things he had in his A1111 that were absent. He has a sampler called "Restart". With SD XL checkpoints he was able to use a lot more samplers for example DPM ++ 3M SDE. His A1111 didn't require a restart of the server and backend change when switching between 1.5 and XL checkpoints. Also he had controlnet functioning for XL.

Im quite happy to continue using SD.Next and I understand XL and controlnet XL are being worked on for better integration. I also heard the way A1111 got XL working is a messy crude way. Would love to try out the Restart sampler and be able to use a different model when I hires.fix though.

[vladmandic]

SDNext is not A1111 and settings are not the same.
But yes, you CAN you different model for second pass - and you can even mix and match different model types for base and second pass.
And you definitely don't need to restart server to switch between SD15 and SDXL models. You need to restart server to switch between backends - which is not even close to same. Diffuser backend supports both and many other model types that can be loaded on the fly.

[gohan2091]

Well you're writing the absolute bare minimum of replies and It's not really helping me to be honest. I am still stuck and haven't been able to switch between 1.5 and XL models on the fly. Are you saying to leave the backend on diffusers for good so I can use all types of models? if so, Controlnet then doesn't work, it gets disabled as well as several other plugins. So I may have XL working but then the 1.5 models have no ControlNet. I am really confused. If a member here could help me, I would be most appreciated.

@eadnams22 yes understood, I understood that part from Vladmandic but not the other part :(

[eadnams22]

Correct, no controlnet with diffusers.

[gohan2091]

Ok so then it seems to get XL working, I need the backend to be set to diffusers but by doing this I then lose access to controlnet even with 1.5 models. So basically if I've understood correctly, SD.Next is just not a good solution for XL use at the moment because I also want access to 1.5 things. Yet my friend who uses A1111 keeps asking me why I won't use A1111 as he has those features working himself. The ability to access 1.5 and XL on the fly and use controlnet.

[vladmandic]

each one has pro and cons and i'm not going to get into full list here.
post like "Yet my friend who uses A1111 keeps asking me why I won't use A1111" doesn't help. nobody is stopping you.

[eadnams22]

I don’t know why you would be losing any 1.5 model use with diffusers, I use 1.5 models all the time in diffusers.

[gohan2091]

each one has pro and cons and i'm not going to get into full list here. post like "Yet my friend who uses A1111 keeps asking me why I won't use A1111" doesn't help. nobody is stopping you.

If I wanted to use A1111, I wouldn't be here. I am here because I like and support SD.Next.

I don’t know why you would be losing any 1.5 model use with diffusers, I use 1.5 models all the time in diffusers.

No, that's not what I meant. I can use 1.5 models and XL models but by using diffusers backend, I lose the ability to have extensions like ControlNet so my 1.5 models don't have controlnet function unless I switch back to original backend but then I lose the XL models... that's what I am saying.

[vladmandic]

native controlnet for sdnext is coming soon.

[gohan2091]

Now with the new update, I was hoping my problem would be solved but nothing for me has changed. I am not sure if I am misunderstanding. To explain again... I want to use ControlNet with 1.5 models (and possibly XL models). I want both 1.5 and XL models to work on the fly without having to restart the server. If I go into diffusers backend, I can do this. If I go into standard backend, the 1.5 models work but the XL models do not (I get Error: model not loaded). When using diffuser backend, important extensions that I use all the time such as controlnet and multidiffusion gets disabled automatically.

Can someone please POLITELY help and explain?

[vladmandic]

diffusers backend now has controlnet support.
multidiffusion is a no in that case, but i don't see what would that be a critical one. your choice.