Words pronounced wrong.

Probably something on your speech replacement list (under menu - Settings - Edit speech) causes this. I suggest that you review the whole replacement list and delete all suspect entries, then try again. The common misconception is that people think that they replace a word, but it's a short word, and write the replacement incorrectly, so that it also matches _parts_ of other words. The newer versions of @Voice app now have an option to "match whole word only" if you select "case sensitive" or "case insensitive" replacement. For RegEx replacements, which are very complex, it assumes the user knows what they are doing and does not do extra checks.
 
If your review of replacements does not help, either delete all of them, or if you want - export them from the menu on the list of replacements screen, then send me all the replace-???.txt files as email attachments, by email. I can review them and correct if you want.

"Live" - both pronunciations are correct and you need human understanding of context to know which should be used. TTS software is not as smart as a human. And I really hope it will never get there. For Roman numerals maybe one could write a set of complex rules to get right the first 100, but is it really worth the effort? In English, again without human intelligence, you would not know if I stands for "me" or "one". The other numbers should be easier to distinguish, but one would probably need a Ph.D. in language parsing and processing to pursue that...

No, I did not do anything. Maybe you changed the TTS voice that reads differently roman numerals etc., or maybe the same voice you were using so far was updated by it's maker with extra "smarts"... Or if you are using a Google TTS voice, it may sound different and act differently, depending on the network connection. When there is no fast network connected, it may use a dull sounding and "stupider" local TTS voice, and when the network is good, it may use a "smarter" voice generator on Google server and send back speech data.