Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is simply because Google Duplex's TTS engine is using Tacotron and WaveNet which are not ready for general use yet.


WaveNet is already used in the Assistant and Google Translate at least. The new voices they announced are powered by WaveNet.


I think all WaveNet speech is still being generated server side instead of on the client hw? So there is a cost to associated to it.

If Google Duplex is a paid product, maybe it just enables running WaveNet on Google Cloud with larger models and higher quality settings .

Speech produced for Assistant doesn't make any money so the server side cost has to be minimised.

One day we'll have all this client side, on specialised ML chips on devices.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: