This object is in archive! 
TTS alerts - not supported language
Solved
If you try to start countdown before starting the tracklog AND you don't have installed proper TTS language, then you got error message with option of TTS engine change. But if you don't have any TTS engine with proper language, then you just confirm. But the error message (and option to select TTS) is back in a half second. And again.
Would it be possible to throw the msg just once (and in case without TTS language replace coundown with beeps)?
Settings was: Czech in Locus and Pico/Google TTS (both doesn't support Czech).
Good day Hrabosh,
good point, thank you. Improved so next time, just one notification in case of any TTS problem will be thrown.
Good day Hrabosh,
good point, thank you. Improved so next time, just one notification in case of any TTS problem will be thrown.
You're faster than death :-)
One more point linked to countdown topic (I hope someone to read this so I wouldn't report new bug). If you set longer time-limit lasting for more than one second, then TTS becomes halting. Nothing super-important but it sounds strange. In general I think that countdown ... 240 - 180 - 120 - 60 - 30 - 20 - 10 - 9 - 8... would be sufficient instead of "every second notification". Sometimes I use longer time-limit - I start it, then phone goes to soft bag, then to zipper bag, then to pocket, lock house, keys goes to pocket, close pocket, gloves on... It usually takes 90-120 seconds.
You're faster than death :-)
One more point linked to countdown topic (I hope someone to read this so I wouldn't report new bug). If you set longer time-limit lasting for more than one second, then TTS becomes halting. Nothing super-important but it sounds strange. In general I think that countdown ... 240 - 180 - 120 - 60 - 30 - 20 - 10 - 9 - 8... would be sufficient instead of "every second notification". Sometimes I use longer time-limit - I start it, then phone goes to soft bag, then to zipper bag, then to pocket, lock house, keys goes to pocket, close pocket, gloves on... It usually takes 90-120 seconds.
Not as fast :).
Thanks for a suggestion ... consider it done. There were also a problem with rotate of screen during counting and also closing a side panel during counting. So both fixed now. Thanks for a "kick".
Not as fast :).
Thanks for a suggestion ... consider it done. There were also a problem with rotate of screen during counting and also closing a side panel during counting. So both fixed now. Thanks for a "kick".
Replies have been locked on this page!