Package Details: piper-tts 1.4.2-1

Git Clone URL: https://aur.archlinux.org/piper-tts.git (read-only, click to copy)
Package Base: piper-tts
Description: Fast and local neural text-to-speech engine
Upstream URL: https://github.com/OHF-Voice/piper1-gpl
Licenses: GPL-3.0-or-later
Conflicts: piper, piper-tts
Provides: piper-tts
Submitter: AUR-user
Maintainer: AUR-user
Last Packager: AUR-user
Votes: 11
Popularity: 1.06
First Submitted: 2025-08-01 21:17 (UTC)
Last Updated: 2026-04-05 07:33 (UTC)

Pinned Comments

AUR-user commented on 2026-01-17 17:05 (UTC)

Both packages (piper and piper-tts) provide /usr/lib/python3.14/site-packages/piper/

I don't see a way to change the module name without breaking dependencies.

It might be best to contact upstream (https://github.com/OHF-voice/piper1-gpl) to solve the name conflict.

Latest Comments

1 2 Next › Last »

AUR-user commented on 2026-05-17 18:47 (UTC)

@CapSel see https://aur.archlinux.org/packages/piper-tts#comment-1055766

CapSel commented on 2026-05-08 09:05 (UTC)

this package conflicts with extra/piper - a mouse configuration tool. can this be solved somehow?

acerix commented on 2026-04-18 20:40 (UTC)

The build error with the vowel asset happens if the full path of the asset file is too long, so it fails when building in a directory with a long path. As Schlaefer mentioned, there's an upstream bug report for this: https://github.com/OHF-Voice/piper1-gpl/issues/126

The build fails using an AUR builder like paru which builds packages under a path like ~/.cache/paru/clone/piper-tts/piper1-gpl/ sice that makes the file paths too long. The package builds if it's built in to a shorter path like ~/piper-tts/.

AUR-user commented on 2026-04-07 18:22 (UTC)

@kagetora13, try to build in a clean environment (extra-x86_64-build) without AUR helper.

To install dependencies not in the repository, you can use -I, e.g. extra-x86_64-build -- -I ../python-pathvalidate/python-pathvalidate-3.3.1-1-any.pkg.tar.zst.

Taithrah commented on 2026-04-07 12:00 (UTC)

From what I can tell, this is an upstream eSpeak-NG issue. The issue happens when compiling phonemes, specifically the NYC vowel asset.

The following addition to prepare() resolved my issue.

prepare() {
    cd "${_pkgname}"
    sed -i 's/"cmake", "ninja"//' pyproject.toml

    local _espeak_patch='PATCH_COMMAND ${CMAKE_COMMAND} -E copy_if_different <SOURCE_DIR>/phsource/vwl_en_us_nyc/a_raised <SOURCE_DIR>/phsource/vwl_en_us_nyc/a_raise'
    local _cmake_file
    for _cmake_file in CMakeLists.txt libpiper/CMakeLists.txt; do
        if ! grep -Fq 'vwl_en_us_nyc/a_raise' "${_cmake_file}"; then
            sed -i "/BUILD_BYPRODUCTS/i\\    ${_espeak_patch}" "${_cmake_file}"
        fi
    done
}

kagetora13 commented on 2026-03-31 16:09 (UTC)

I'm still getting the below error when trying to build this package.

Refs 4914,  Reused 3937
Compiled phonemes: 2 errors.
[44/167] Building CXX object src/speechPlayer/CMakeFiles/speechPlayer.dir/src/frame.cpp.o
ninja: build stopped: subcommand failed.
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "/usr/lib/python3.14/site-packages/skbuild/setuptools_wrap.py", line 668, in setup
    cmkr.make(make_args, install_target=cmake_install_target, env=env)
    ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/skbuild/cmaker.py", line 696, in make
    self.make_impl(clargs=clargs, config=config, source_dir=source_dir, install_target=install_target, env=env)
    ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/skbuild/cmaker.py", line 741, in make_impl
    raise SKBuildError(msg)

An error occurred while building with CMake.
  Command:
    /usr/bin/cmake --build . --target install --config Release --
  Install target:
    install
  Source directory:
    /home/rsruser/.cache/paru/clone/piper-tts/src/piper1-gpl
  Working directory:
    /home/rsruser/.cache/paru/clone/piper-tts/src/piper1-gpl/_skbuild/linux-x86_64-3.14/cmake-build
Please check the install target is valid and see CMake's output for more information.


ERROR Backend subprocess exited when trying to invoke build_wheel
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'piper-tts-1.4.1-2':
error: packages failed to build: piper-tts-1.4.1-2

DeX77 commented on 2026-03-03 10:41 (UTC)

@Clover_Yan: I tried to package g2pw but check() using pytest fails with

AttributeError: 'G2PW' object has no attribute 'all_tied_weights_keys'

guess its due to python-transformers being to new.

Clover_Yan commented on 2026-02-12 12:01 (UTC)

Piper introduced g2pW in v1.4.0 recently. This makes the library g2pW necessary. I hope someone can help packaging python-g2pw and add it into (opt)deps. Thanks in advance

FGYada commented on 2026-02-09 20:21 (UTC) (edited on 2026-02-09 20:27 (UTC) by FGYada)

I encountered the "Bad vowel file" error during the espeak-ng compilation phase. It seems to be a race condition when building with multiple cores. Here is how I fixed it:

Edit the PKGBUILD and add export CMAKE_BUILD_PARALLEL_LEVEL=1 inside the build() function.

Example:

build() { cd "$_pkgname" export CMAKE_BUILD_PARALLEL_LEVEL=1 python -m build --wheel --no-isolation }

Schlaefer commented on 2026-02-05 09:39 (UTC)

1.4.1-1 needs a checksum update and aur/python-pathvalidate as new dependency.

1 2 Next › Last »