<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FastSpeech 2: Fast and High-Quality End-to-End Text to Speech · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2006.04558/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2006.04558/feed.xml" rel="self" type="application/rss+xml" /><item><title>FastSpeech 2: Fast and High-Quality End-to-End Text to Speech — mentioned by nmfisher</title><link>https://news.ycombinator.com/item?id=34271860</link><guid isPermaLink="false">urn:hackerpapers:mention:2006.04558:34271860</guid><pubDate>Fri, 06 Jan 2023 07:16:05 GMT</pubDate><description>&lt;p&gt;My app [0] currently uses a mildly customized version of FastSpeech 2 [1] with LPCNet [2] vocoder, which I consider &amp;quot;good quality&amp;quot; @ 16kHz. Faster than realtime on mobile CPU (at least, on anything upwards of a mid-range 2017 device - I can stream practically instantly on my iPhone 11). Using a different vocoder with mobile GPU could probably get even faster (which I don&amp;#x27;t want to do, for various reasons), and desktop CPU is usually even faster. There are various other flavours that can deliver faster synthesis (NixTTS comes to mind), but IMO they sacrifice quality even further. &amp;quot;Good…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2006.04558/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>eess.AS</category></item></channel></rss>
