piper icon indicating copy to clipboard operation
piper copied to clipboard

i am not getting any output nor error

Open Yahiyamuhammed opened this issue 1 year ago • 2 comments

i am running this command and not getting any output or error

D:\programming\ai\bark-ai\piper>echo "hi , hello " | .\piper.exe -m .\en_US-bryce-medium.onnx -f test1.wav

and i tried debug option and it produces these output

D:\programming\ai\bark-ai\piper>echo "hi , hello " | .\piper.exe -m .\en_US-bryce-medium.onnx -f test1.wav --debug [2024-09-06 15:45:42.400] [piper] [debug] Loading voice from .\en_US-bryce-medium.onnx (config=.\en_US-bryce-medium.onnx.json) [2024-09-06 15:45:42.401] [piper] [debug] Parsing voice config at .\en_US-bryce-medium.onnx.json [2024-09-06 15:45:42.403] [piper] [debug] Voice contains 1 speaker(s) [2024-09-06 15:45:42.403] [piper] [debug] Loading onnx model from .\en_US-bryce-medium.onnx

and also when i try to install with pip i am getting this error also PS D:\programming\ai\bark-ai> 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 to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts PS D:\programming\ai\bark-ai>

Yahiyamuhammed avatar Sep 06 '24 10:09 Yahiyamuhammed

Which version of python you are using? try with Python 3.10 or 3.11

Akash7677 avatar Sep 12 '24 06:09 Akash7677

Did you ever fix this?

EDIT: Tried this on a different machine and it worked fine - weird. didn't have anything on --debug nor procmon.exe that I could see to go over.

johnem-msft avatar Apr 19 '25 16:04 johnem-msft