-
Notifications
You must be signed in to change notification settings - Fork 25
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
Q: Speech as Vec<u8> or &[u8] #12
Comments
Sorry, no support for that yet. I'd love to have it, though, and would
accept a PR. Most backends support it, and I think UWP even creates the
bytes before sending them to a media player, so `speak` can probably use
that functionality and just pass along its output.
If anyone wants to implement it, I'd probably call the method and
feature `synthesize`.
|
I'm quite interested in having the ability to get the generated raw audio samples, specifically for the WinRT and AVFoundation backends. I think for some backends, its a little bit nontrivial- some will want to progressively stream out samples as they are generated, and the generated audio formats (and sample rates) may vary between backends. I don't know if this would help it get done more quickly, but I'd be happy to offer a bounty to anybody who implements this feature in a manner acceptable to @ndarilek, creates a PR, and gets it merged to this repository. $40 PayPal each for the WinRT and AVFoundation backends, or $80 together. |
I am currently to use Because on Windows, opening a note: For those who have encountered the same problem as I did and arrived at this Issue. While it is not always advisable to use a branch in development for a product, a product in demand must be released. [dependencies]
# tts = "0.25.6"
[target.'cfg(windows)'.dependencies]
# tts Issue-#12, PR-#30 synthesize branch
tts = { git = "https://github.com/Bear-03/tts-rs", branch = "synthesize" } |
Hi there,
Silly question, maybe, but is it possible to get the produced speech as a Vec or a &[u8]? I have not been able to find a way to get it.
Thanks!
The text was updated successfully, but these errors were encountered: