04-05-2020, 07:30 PM
(04-05-2020, 06:00 PM)jim_chapman Wrote: I see what you have in mind - but it does look like it might be quite difficult to do. From a quick look at the AWS and Polly documentation, I didn't find any easily digestible instructions for how a .NET (UWP and Xamarin) app should carry out authentication and construct the endpoint for invoking the Polly APIs. It is obviously possible, but the only proper sample code I code find was for Python and Java, and even that seemed to be missing some of the important steps. So making it work in .NET might be a bit of a research project. Implementing the Freda file-browsers for DropBox, GoogleDrive, and Synology were all research projects of similar complexity, and they all required some days or weeks of work. To that we add the work to deal with all the tricky asynchronous logic for launching, tracking and interrupting speech playback, and dealing with all the various edge cases and error cases.
I think you can tell that I'm not keen ;-)
But honestly it sounds like a fair amount of work to provide a feature that's not going to be useful to many of my users (until/unless a lot of people start setting up personal AWS accounts and subscribing to Polly voices for their personal use). So, given my current knowledge of what would be involved, I am not going to prioritise this feature.
Sorry not to be more helpful.
Just out of curiosity, how are you handling the 'read aloud' part now? Do you 'chunk it up' into discrete amounts, or just keep shoving text until it blocks?