[Bug]: Can't add point prompts or pick a box threshold

[copybaras]

Is there an existing issue for this?

• I have searched the existing issues and checked the recent builds/commits of both this extension and the webui

Have you updated WebUI and this extension to the newest version?

• I have updated WebUI and this extension to the most up-to-date version

Do you understand that you should go to https://github.com/IDEA-Research/Grounded-Segment-Anything/issues if you cannot install GroundingDINO?

• My problem is not about installing GroundingDINO

What happened?

After dropping image to Segment Anyting tab I can't add point prompts or pick a box threshold after checking Enable GroundingDINO.

Steps to reproduce the problem

1. Go to img2img
2. Open Segment Anyting tab
3. Select a sam model
4. Drop image under selecting model tab
5. Try to click on the image with right and left mouse buttons
6. Check Enable GroundingDINO.
7. ???
8. Profit
   

What should have happened?

Dots should appear on the image after clicking at it.

Commit where the problem happens

webui: latest A11111 as for 14.04.23
extension: sd-webui-segment-anything 16.04.23

What browsers do you use to access the UI ?

No response

Command Line Arguments

@echo off

set PYTHON=
set GIT=
set VENV_DIR=
set COMMANDLINE_ARGS= --xformers --no-half-vae
set ATTN_PRECISION=fp16
call webui.bat

Console logs

No errors when clicking on dropped image

This error after entering text in GroundingDINO Detection Prompt:

127.0.0.1/:1 Uncaught (in promise) API Error
Promise.then (async)
(anonymous) @ index.4395ab38.js:76
(anonymous) @ index.4395ab38.js:4
le @ index.4395ab38.js:4
x @ index.4395ab38.js:79
(anonymous) @ index.4395ab38.js:4
(anonymous) @ index.4395ab38.js:4
u @ index.4395ab38.js:78
t.$$.update @ index.4395ab38.js:78
ql @ index.4395ab38.js:4
bt @ index.4395ab38.js:4
Promise.then (async)
yo @ index.4395ab38.js:4
Yl @ index.4395ab38.js:4
(anonymous) @ index.4395ab38.js:4
g @ index.4395ab38.js:34
i @ index.4395ab38.js:34
(anonymous) @ index.4395ab38.js:4
S @ index.4395ab38.js:79
i @ index.4395ab38.js:79
(anonymous) @ index.4395ab38.js:4
k @ index.4395ab38.js:78

Additional information

No response

[continue-revolution]

Your terminal must have thrown some exceptions. Check your terminal and let me know the error.

[Rootybooty]

Having the same issue. No exceptions here. Updated to the latest version of everything. The image just isn't interactable after uploading it. Left clicking does nothing. Right clicking shows the usual browser right click menu as shown here:
https://i.imgur.com/XHVUpdI.png

[continue-revolution]

#10

The reason is probably due to some other extensions. Could you share with me all extensions you have installed?

[Rootybooty]

Sure thing.

Edit: I went and disabled all the extensions above besides this one but still doesn't seem to work.

[Someonetoldme584]

Same issuie

[continue-revolution]

I really have no idea why. Someone has two PCs with similar environment, one can, one cannot, unable to really find a reason. A reason I guess might be that your browser somehow blocked my JavaScript, but I’m not sure. I can really not find a way to reproduce. My best advice is to pick another environment/different browser to re-try.

[B-rowser]

I have the same issue. Tried it with Chrome and Firefox. I should be getting terminal messages when I load new SAM models in right? Because I don't get those. So I suspect something is wrong.

[continue-revolution]

I have the same issue. Tried it with Chrome and Firefox. I should be getting terminal messages when I load new SAM models in right? Because I don't get those. So I suspect something is wrong.

Yes. If there is no change on both your terminal and your UI, then your server somehow disconnected to the browser. If you have updated your extension to the newest, you should get a message on your UI even if you simply click ‘preview segmentation’ without uploading an image.

[continue-revolution]

In the update when I post this message, when you simply upload an image without adding whatever point prompt or groundingdino and you have clicked Preview prompts, you should see these on your terminal

Start SAM Processing
Initializing SAM
Running SAM Inference (1520, 1152, 3)

and this on your browser

[continue-revolution]

if anyone here have time please update the extension and give it a try. I'm not sure where the problem is. I can only try narrowing down the problem. After checking this, you can try using GroundingDINO without point to see if it is working. If GroudingDINO is working, you can disable GroundingDINO and try adding point prompts.

[B-rowser]

To be clear the WebUI is still running I can load SD models and everything else seems to work just fine, interacting with the extension does not yield even an error message until I enable GroundingDINO which won't install properly and then returns an error, breaking the extension. No idea if copybaras has the same issue

[continue-revolution]

To be clear the WebUI is still running I can load SD models and everything else seems to work just fine, interacting with the extension does not yield even an error message until I enable GroundingDINO which won't install properly and then returns an error, breaking the extension. No idea if copybaras has the same issue

If your problem is about '_C', please follow the step:

1. go to nvidia website to download appropriate version of CUDA (you should be able to see the cuda version which match your torch version on the botton of the webui page)
2. Initiate your local terminal, switch to your virtual environment and run

from torch.utils.cpp_extension import CUDA_HOME
print(CUDA_HOME)

If it's printing some path, then you are good to go.
3. Uninstall groundingdino via either pip uninstall groundingdino or you manually remove groundingdino directory inside your virtual environment, it is most likely something named venv (your virtual environment, assume you are using some bat on windows) then Lib then site-packages
4. re-initiate webui

Please do not skip any step.

[continue-revolution]

This _C problem has been asked multiple time but is very hard to resolve. #31 is about this.

I would assume @copybaras @Rootybooty @Someonetoldme584 have another very mysterious environment problem.

[Rootybooty]

I noticed that in one of your demos, you're running python 3.8.10. It might not be the issue but just wanted to confirm, this extension should work with python 3.10.6 release right?

[continue-revolution]

Python version should not be a problem. Higher version normally supports everything lower version supports