Commit ec9ee9b43fd6b4a8d990e9613dec4d9ae3bc3061 introduces support for protontts, a TTS library using Piper.
However, it seems to use a C wrapper around libpiper (it checks for piperInitialize in piper_c.h) that doesn't seem to be publicly released; at least it is neither part of libpiper nor part of proton, not part of anything any of the common search engines would find.
Commit ec9ee9b43fd6b4a8d990e9613dec4d9ae3bc3061 introduces support for protontts, a TTS library using Piper.
However, it seems to use a C wrapper around libpiper (it checks for piperInitialize in piper_c.h) that doesn't seem to be publicly released; at least it is neither part of libpiper nor part of proton, not part of anything any of the common search engines would find.
Current libpiper has a native C API (https://github.com/OHF-Voice/piper1-gpl/blob/main/libpiper/include/piper.h) - but it is different from the one expected by protontts.
The API actually used in protontts seems to resemble (but not fully match) the C++ API that was present in an old version of piper,
https://github.com/rhasspy/piper/blob/v1.2.0/src/cpp/piper.hpp
Where can this mysterious library that eludes Google and Yandex be found? Would it make sense to migrate to the current libpiper API?