Added deck picker widget to allow quickly pronouncing text based on your presets. Can be disabled in preferences.
Added a way to output debug logging on the command line
Fix on the fly sanitizer, which should allow substituting common characters such as [], ...
Comments
Am I understanding correctly that your main concern is that filenames shouldn't have spaces in them ? When I generate audio with AwesomeTTS, the files don't have spaces in them, could you share a screenshot of when that happens ?
2020-12-22 03:24:21 +0000 UTC
No worries, and sorry I didn't see your reply. I know it requires quite a bit of work.
Also, a much quicker one I think, when an mp3 is saved in human readable format, we may need a quick regexp to replace spaces with _ (works on all systems) - basically I don't think anything that isn't a letter needs to be there for the file name to be readable? It would solve a few basic problems that people will encounter with readable file names not working. That or the ability to change the service names, because I want to keep the name of the service and voice, and all of them have spaces in them and it breaks the usage of other plugins (that should be able to handle any filename, but don't, like edit audio in audacity) and it can easily be avoided on our side. It at least makes sense for the Service and Voice. Maybe there are already abbreviations for them anyway, I don't know. Readable doesn't necessarily mean litteral in users' mind, but just so you can trace back what the file is.
These are all suggestions/thoughts by the way, not demands.
I'm studying Korean, and use English for some fields. I'll soon be using Korean only in my fields.
2020-12-18 14:18:55 +0000 UTC
Some of this functionality might only come in the next generation of AwesomeTTS, as I explained in my latest post. So I need to ask you for a bit of patience but it will come. What languages are you studying ?
2020-12-05 03:31:12 +0000 UTC
Hi Anne! I understand your frustration. i think AwesomeTTS should become much smarter and should know 1. what languages are contained in each field (perhaps per-note type / per deck) 2. allow the user to quickly repeat the same type of operation. Essentially, a preset should know everything about what needs to be done, the source field, the target field, the service, the voice.
2020-12-05 03:30:34 +0000 UTC
First, thank you for working on AwesomeTTS!
I use 2 languages on my cards, for different fields, and need to go back and forth , and that means every time I change language/preset, I have to go through selecting the right fields for the cards. Could there be a way to associate each preset or group to the last set of fields used, if they happen to exist in the cards selected? Each specific preset always picks up from & save into the same fields.
Thanks
