-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environment issue #246
Comments
@FrenkT Thanks for reporting this |
@FrenkT may I ask you how you manually installed pytorch to get Fastsd cpu to work ? |
@FrenkT Have you tried the latest release? |
@maburu-keki, here are the steps I followed, hope they work for you. First of all, it looks like pytorch 2.4.0 is not available on Intel Mac via pip, so I had to go through conda, so:
|
I get this :
While The "pytorch" channel does have up to the latest stable version (2.5.0) for windows, linux and arm64 osx, it is stuck at version 2.2.2 for mac os x64 (Intel) : Should I use another channel ? |
I had to install pytorch (2.4.1) from the "conda-forge" channel
...as official pytorch binaries for Intel Macs are stopped (from 2.3.0 onwards)
It got stuck at the command line : no gui window popping, nothing happening at all, for about a minute.
@rupeshs Your app doesn't work at all on Intel Macs running mac os Big Sur. |
@maburu-keki |
Most definitely. I wish I had the latest Mac Os but my mac being a few years (too) old, Apple won't let me upgrade beyond Big Sur. |
I have the same problem here on Monterey. could you please changed the title of the issue to 'PyTorch on Mac uint16 or similar, I only found this issue by accident. I'll try the conda route. |
Hi all, thank you for developing the project, it's really great.
When I run on Intel Mac (
./install-mac.sh
and then./start-webui.sh
or./start.sh
) I get the following error:The only other report I found on this is this one, where they suggest upgrading torch. In fact, I managed to get
FastSD CPU
running by manually installingpytorch=2.4.0
.I didn't have a chance to try this on another OS, so not sure if this is specific of my environment or some other dependency that needs to be pinned.
The text was updated successfully, but these errors were encountered: