-
Notifications
You must be signed in to change notification settings - Fork 525
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
M1 Mac piper-phonemize issues + arm64 binary fails to run #395
Comments
I can confirm issue number 1 which led me building from source which worked well with the Cmakelist pull request currently open. |
Having same issues |
Also experiencing this, but unfortunately don't have the python / C knowledge to help resolve it :/ |
Here is the mentioned pull request, it's still open: Fixed build issues on MacOS caused by unset rpath by TheLouisHong · Pull Request #412 · rhasspy/piper. This issue makes it harder for the M1/2 mac users to install the library. |
@bephrem1 Try install pip install piper-phonemize-cross command |
I tried it, then ran
Didn't work for me. Mac with M2. |
can you provide some logs? |
Sure, but the message is not new. pip install piper-phonemize-cross Collecting piper-phonemize-cross
Downloading piper_phonemize_cross-1.2.1-cp312-cp312-macosx_11_0_arm64.whl.metadata (325 bytes)
Downloading piper_phonemize_cross-1.2.1-cp312-cp312-macosx_11_0_arm64.whl (15.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 15.1/15.1 MB 7.3 MB/s eta 0:00:00
Installing collected packages: piper-phonemize-cross
Successfully installed piper-phonemize-cross-1.2.1 pip install piper-tts Collecting piper-tts
Using cached piper_tts-1.2.0-py3-none-any.whl.metadata (776 bytes)
INFO: pip is looking at multiple versions of piper-tts to determine which version is compatible with other requirements. This could take a while.
Using cached piper_tts-1.1.0-py3-none-any.whl.metadata (776 bytes)
ERROR: Cannot install piper-tts==1.1.0 and piper-tts==1.2.0 because these package versions have conflicting dependencies.
The conflict is caused by:
piper-tts 1.2.0 depends on piper-phonemize~=1.1.0
piper-tts 1.1.0 depends on piper-phonemize~=1.0.0
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts |
@BirgitPohl try install with this option pip install piper-tts --no-deps |
This worked for me. Thanks! |
This works for me! |
Creating this issue to pull together the issues that Mac users are facing getting things up & running locally. I am on an
M1
Macbook,2020
, runningSonoma 14.0
(8GB RAM
).1)
piper-phenomize
dependency issueRunning
pip install piper-tts
yields the following error:following up with specific package versions with
pip install piper-phonemize==1.1.0 piper-tts==1.2.0
yieldsrunning
pip install piper-phonemize
yields the same error as above.This is odd because the package shows up on PyPi (piper-phonemize on PyPi). (not sure why it says
(from versions: none)
, wondering where that data is pulled from.This leads to the
piper-tts
being (currently) uninstallable for Mac users.2)
arm64
binary fails to runRunning the
arm64
binary (downloaded from repo homepage) result in the error:running
file {piper_executable_path}
yieldsSo currently it seems that there is no straight-forward way to run the library on a Macbook (w/o use of Docker, etc, which I might explore next).
Related Issues:
piper
#27 (issue running
arm64
binary)#156 (
piper-phonemize
dependency issue)#193 (
piper-phonemize
dependency issue)#217 (
piper-phonemize
dependency issue)#357 (issue running
arm64
binary)#384 (
piper-phonemize
dependency issue)#404 (~ other ~)
piper-phenomize
rhasspy/piper-phonemize#14 (
piper-phenomize
pip package missing)Related PRs:
rhasspy/piper-phonemize#11
rhasspy/piper-phonemize#13
Related Videos:
▶︎▶︎ Context on Piper TTS Python Package: https://youtu.be/MT9wJ1k3xBw?si=kC51MB4yVZuYy2cO&t=1206 (timestamped)
The text was updated successfully, but these errors were encountered: