Closed alessandroperilli closed 11 months ago
Ah, I see. First of all, thank you very much for your tests! I was hopeful that moving the models to the available device in one place would be sufficient. I'll take a look at it as soon as possible and make the necessary corrections.
I've made some more changes. Now, all models should be initially loaded on the CPU and moved to the corresponding Torch device if one is available. A new test would be highly appreciated.
This is working now. Thank you.
Attempting to use the
SAM Model Loader
node on an Apple M2 generates the following error:This is an old problem that I never reported because I normally use the
SAMLoader
node fromImpact Pack
, which allows you to chooseCPU
asdevice_mode
. But given that this is a new repo and this node exists...Update:
Reading the documentation of your new suite, I discovered that you only utilize the SAM_HQ models. So I tried to use sam_hq_vit_h.pth with the
SAMLoader
node fromImpact Pack
, in the attempt to debug #6.SAMLoader refuses to load that model and return the same error above:
So I'm assuming the problem is not specifically about the
SAM Model Loader
node, but the model family that by default the node tries to load.