Re: Pleco for Android 2.4.0 Beta 5 Bug Report / Feedback Thr
stephanhodges said:
After installing and downloading things, I ran the reader, and tried the voices. There was no sound at all. I exited Pleco and tried other apps, but no sound from them either.
Well that at least suggests it wasn't something specific to our TTS, though it is a bit worrying...
stephanhodges said:
At "90%", the newer Hui voice is still jumpy, as if it speeds up and slows down. It also sounds like it's overlapping syllables sometimes. I am trying to get a 4 segment audio cable to be able to record it. The Lulu voice is smoother and a little "slower", without changing any settings. It seems to have a little bit of a background "hum" to it, however. I don't recall hearing that before.
I actually finally heard a little bit of that when I tried using Hui over a BT headset, so I see how it could be something speaker- or audio-subsystem-related... but Lulu is playing through the exact same audio code now (just generating samples differently) so I'm not sure whether that's somehow causing less background work or whether it's simply operating at a frequency or pitch level that's more resilient to audio system problems.
wibr said:
Small bug: When I set the speed for TTS it shows %% after each item...
This is actually a workaround for an Android bug: basically, Google changed the preferences screen in Android (3.0?) so that you could use codes prefixed by % to insert certain special values (like "current value of this preference," which oddly enough had not been supported before then), but one consequence of this was that a standalone % in a preference would cause the app to crash. Two %%s, the designated "this is not a special value" escape sequence, seems to avoid the crash but doesn't display as one % like it's supposed to. We might be able to rig up a way to get a single % to display by hacking around with the preferences code but it didn't seem like a big enough deal to make it a priority.
santiago said:
Thanks for the TTS advances, alternating voices really helps to grasp the pronuntiation. (If ever the play-all-along option is implemented it will be amazing)
It will be, though Lulu doesn't seem to support following along word-by-word with the cursor at the moment unfortunately.
HW60 said:
If in fill-in-the-blanks the brush in the top right should not react on (the totally unnecessary) tapping, when pinyin have to be entered (test reading) - look at the resulting screen.
So you'd rather it didn't do anything at all when you tapped on it?
HW60 said:
All known bugs seem to have disappeared, no more bugs detected for the time being. This is a great update!
Great, thanks!
wibr said:
Another small one: While doing flashcards, with the "switch dictionary bar" at the right side activated the undo stroke arrow is almost invisible...
Yeah, that needs a higher-contrast background - thanks.
Wan said:
Thanks for this update, no crashes so far. TTS works as well.
Great! Has the search speed situation gotten any better? (we did quite a bit of optimization on that, turns out that SE phones exhibit some rather odd file caching behavior which had to be worked around - make sure to update all of your add-on databases in Updates though)
Wan said:
Lulu sounds a little more tinny, and the tones are a little more accurate with Hui, but that may be in my head
Seems to be a little different on every phone here, actually - the frequency responses differ in various subtle ways.
Amusing discovery today was having both voices read 《
施氏食狮史》 - works, and seems pretty accurate, but it sounds (not unexpectedly) like 2 minutes of incomprehensible gibberish.