# Cantai and performance problems

**URL:** <https://forums.steinberg.net/t/cantai-and-performance-problems/1031867>\
**Category:** Dorico\
**Created:** [May 7, 2026, 9:19am UTC](https://forums.steinberg.net/t/cantai-and-performance-problems/1031867 "2026-05-07T09:19:17Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![kasky1](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/kasky1/32/278743_2.png) [@kasky1](https://forums.steinberg.net/u/kasky1)\
**Post date:** [May 7, 2026, 5:43pm UTC](https://forums.steinberg.net/t/cantai-and-performance-problems/1031867/8 "2026-05-07T17:43:15Z")

</div>

According to Richard De Costa on Feb 6, Cantai uses

1. **Local GPU:** Utilizes your graphics card for near-instantaneous synthesis.

2. **Local CPU:** For machines without a dedicated GPU, the system runs entirely on your processor.

3. **Cloud Failover:** We maintain an AWS path only as an emergency backup for legacy hardware.

Thus, I would imagine that one’s specific computing resources would dictate how Cantai operates on individual machines. Just FYI.

> [@Dev Diary: Cantai 100% Local Rendering & Ethical AI for Dorico (April 30 Launch)](https://forums.steinberg.net/t/dev-diary-cantai-100-local-rendering-ethical-ai-for-dorico-april-30-launch/1023183):
>
> Hi everyone, As we approach the April 30 launch for Cantai for Dorico, we wanted to share a major technical update regarding Cantai. Moving to 100% Local Rendering To provide the most robust and private workflow possible, we have moved all of Cantai—including the phonemization—to your local hardware. Everything is local. Your scores, lyrics, and audio data never leave your machine. To ensure the best performance regardless of your setup, we’ve implemented a hybrid hardware hierarchy: Local…

---

_[View the full topic](https://forums.steinberg.net/t/cantai-and-performance-problems/1031867)._