@TheQuinbox Oh actual shit. Let's o
@TheQuinbox aw, not anywhere I can grabby yet. Sad faysh
@mew You said this as I was drafting my post about the source code :D
@TheQuinbox you won me over with your little demonstration of explore by touching really damn fast.
@TheQuinbox It's weird, right, I feel like a lot of TTS engines on Android get this wrong, and I can't really figure out why
@TheQuinbox claude: Build succeeded in 5m 50s.
@TheQuinbox God damn that's snappy!
@mew Riiight? I think there's still a bit of room for improvement in a few hyperspecific areas, but maaaan
@TheQuinbox It amazes me how incompetent commercial TTS vendors are at writing proper drivers for their own software. I honestly think it is just failure to consider the user experience. Very few people who aren't screen reader users themselves put sufficient thought into how a few ms makes a massive difference, even as they bemoan the lack of 60fps rendering on whatever graphics thing is bothering them. @mew
@jcsteh @TheQuinbox @mew My ebook reader has pauses in between paragraphs from rendering the next bit of speech that drive me bonkers. Currently figuring how to stream some text in this neural net based TTS so it can be actually passable. 😭
