This object is in archive!
Speach error for pace (in french)
Solved
Audio description in french for pace "allure" ib wrong
Expected : x minutes y secondes par kilomètre
Actual result : x heures y minutes kilomètre.
Missing PAR (by) and number is minutes second, no hours minutes
Files:
Screenshot_2023...
The same problem 
Hi Florian,
we are sorry for this inconvenience. It seems that French TTS wrongly reads the line "x.x min/km". This can be fixed by a custom TTS file. Unfortunately, this may take some time...
Hi Florian,
we are sorry for this inconvenience. It seems that French TTS wrongly reads the line "x.x min/km". This can be fixed by a custom TTS file. Unfortunately, this may take some time...
The system says x.y, like days hours. insteed of "minutes seconde". It is not the same in English?
Best regards
The system says x.y, like days hours. insteed of "minutes seconde". It is not the same in English?
Best regards
Hi Florian,
no, English and other languages are OK.
Hi Florian,
no, English and other languages are OK.
The "test" (view print screen) in language selection is working fine..
The "test" (view print screen) in language selection is working fine..
I test in English. Speed (x km/h) and pace (y min/km) are logical (I.E. 12 km/h and 6 min/km). But in french the parce number is completly wrong. I Pretty sure that the French text is wrong at the "root".
Best regards
I test in English. Speed (x km/h) and pace (y min/km) are logical (I.E. 12 km/h and 6 min/km). But in french the parce number is completly wrong. I Pretty sure that the French text is wrong at the "root".
Best regards
Hi Florian,
we had a look in the "root" and the system generates "Allure 02:52min/km" for the French TTS when announcing the pace in the audio coach. Nothing about "heures".
Hi Florian,
we had a look in the "root" and the system generates "Allure 02:52min/km" for the French TTS when announcing the pace in the audio coach. Nothing about "heures".
Hello. I found the problem.
It's a TTS bug + wrong separator . More visible in french but present in other tested language (German and English) . If the second number start with a "zero", "min/km", "sec/km" or "km/h" ,is misinterpreted...
Try (in englisch)
05 sec/km vs 15 sec/km
On top of that, the X:Y interpretation is hours:minutes (but not always says)
I try in german
5:05 min/km vs 5:15 min/km
5,05 min/km vs 5,15 min/km
First line is always wrong (says mimimal) .
Second one is good
Hello. I found the problem.
It's a TTS bug + wrong separator . More visible in french but present in other tested language (German and English) . If the second number start with a "zero", "min/km", "sec/km" or "km/h" ,is misinterpreted...
Try (in englisch)
05 sec/km vs 15 sec/km
On top of that, the X:Y interpretation is hours:minutes (but not always says)
I try in german
5:05 min/km vs 5:15 min/km
5,05 min/km vs 5,15 min/km
First line is always wrong (says mimimal) .
Second one is good
In french and German the following add "hours"
13:05 min/km vs 13:15 min/km
In french and German the following add "hours"
13:05 min/km vs 13:15 min/km
We made a few more tests and we found out that there is really a bug in the TTS not able to read properly "x:xx min/km" string. The only solution is the custom TTS we have to prepare.
We made a few more tests and we found out that there is really a bug in the TTS not able to read properly "x:xx min/km" string. The only solution is the custom TTS we have to prepare.
Thanks for the time spend (but i can live a moment with this bug 😂).
Thanks for the time spend (but i can live a moment with this bug 😂).
Hi Florian,
the custom TTS has been added to the app so you can test it when the new version comes out.
Hi Florian,
the custom TTS has been added to the app so you can test it when the new version comes out.
Replies have been locked on this page!