Open keturn opened 12 months ago
This must be a regression, since I'm sure we had a working zoe depth processor at some point.
Other UIs are reporting the same error:
The A111 issue references torch 2.1 as a possible cause 😬
Yeah, it's a torch 2.1 issue, introduced in this PR: https://github.com/pytorch/pytorch/pull/99243#issuecomment-1646736129
I was about to create a PR to fix it, but I see it was actually already done: https://github.com/pytorch/pytorch/pull/110778
So I think we will just need to wait for the next release of torch.
A quicker fix might be to update controlnet-aux
to use plain integers. It's a good handful of spots where this would be needed: https://github.com/search?q=repo%3Apatrickvonplaten%2Fcontrolnet_aux+interpolate%28&type=code
torch 2.1.1 was released yesterday - it does not include the fix. Here's the 2.1.1 tag with that code: https://github.com/pytorch/pytorch/blob/v2.1.1/torch/nn/functional.py#L3777-L3783
Look like it going to be fixed in 2.2, the merge has been pulled to the 2.2 release branch..
This is fixed in the just-released torch 2.2.
Is there an existing issue for this?
OS
Linux
GPU
cuda
VRAM
12GB
What version did you experience this issue on?
1c7ea57492802eaf19f81ada9ed545a2e618add8
What happened?
Traceback:
though this traceback says it is in
resizer
, it does not change when I set Resize Mode to Crop or Fill instead of Resize.The Midas depth processor works without error.