We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In a Debian system, this simple script:
ss = Create SpeechSynthesizer: "English (Great Britain)", "Male1" text$ = "text" phonemes$ = Get phonemes from text: text$ appendInfoLine: "phonemes = ", phonemes$
worked fine with Praat 6.3.14:
$ praat_nogui /var/tmp/test.praat phonemes = tɛkst
However, with version 6.3.15 of Praat, it yields random Chinese characters instead of a string of IPA characters:
$ for i in {1..5} ; do ./praat_nogui /var/tmp/test.praat ; done phonemes = 陖 phonemes = 鼲 phonemes = 隝 phonemes = 黑 phonemes = 蹑
The text was updated successfully, but these errors were encountered:
The patch below fixes the problem for me. I am not sure about the possible colateral effects of bypassing the call to Melder_dup.
Melder_dup
--- a/dwtools/SpeechSynthesizer.cpp +++ b/dwtools/SpeechSynthesizer.cpp @@ -701,7 +701,7 @@ conststring32 SpeechSynthesizer_getPhonemesFromText (SpeechSynthesizer me, const } else MelderString_append (& phonemes, phonemeLabel, (iint < numberOfIntervals ? phonemeSeparator : U"") ); } - return Melder_dup (phonemes.string).get(); // TODO: implement MelderString_move() + return phonemes.string; } catch (MelderError) { Melder_throw (U"Phonemes not generated."); }
Sorry, something went wrong.
Just for the record, this issue causes the unit test dwtest/test_SpeechSynthesizer.praat to fail in version 6.3.15.
dwtest/test_SpeechSynthesizer.praat
No branches or pull requests
In a Debian system, this simple script:
worked fine with Praat 6.3.14:
However, with version 6.3.15 of Praat, it yields random Chinese characters instead of a string of IPA characters:
The text was updated successfully, but these errors were encountered: