![]() |
|
TTS that sounds less fake - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Generative AI (https://www.datasculpting.ai/inference/forumdisplay.php?fid=17) +--- Forum: Image (https://www.datasculpting.ai/inference/forumdisplay.php?fid=69) +--- Thread: TTS that sounds less fake (/showthread.php?tid=538) Pages:
1
2
|
Re: TTS that sounds less fake - visionforge - 10-02-2026 Interesting, I hadn't tried that. The pattern around embeddings has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer. Re: TTS that sounds less fake - cobaltworks25 - 10-03-2026 What worked for me was pretty simple. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece. If you post your exact settings, people here can probably narrow it down pretty fast. Re: TTS that sounds less fake - cobaltspark - 10-03-2026 subscribed, curious where this lands. There are a few different conversations hiding inside this thread, so being explicit about the goal helps. Re: TTS that sounds less fake - thetaplane - 10-03-2026 Quote:subscribed, curious where this lands. A couple things I'd check first. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time. Re: TTS that sounds less fake - llmtrack - 10-03-2026 Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality. Re: TTS that sounds less fake - deltagrid - 10-03-2026 What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. |