Local Rendering
Introducing ACE Studio's Local Rendering technique.
Turbo Mode
Turbo Mode offloads the heavy synthesis steps of Verse25 to your local CPU/GPU, reducing cloud latency and accelerating the overall render time.
Testing Your Device
Local rendering consumes a significant amount of local computing power, so it requires a certain level of computer configuration.
During the onboarding setup, ACE Studio will automatically test your device's performance. Turbo Mode will be enabled if your device is supported. You can also manage it in the [Rendering] tab of preferences window. To enable Turbo Mode manually, you must pass a performance test.
Run the test
In the [Rendering] preference window, click the Run Test button to start the test.
Close other large programs to avoid misjudgment caused by performance consumption from other software.
Monitoring During Rendering
If local rendering tasks exceed acceptable time limits, users will be prompted to switch back to cloud rendering.
For Windows Users with Multiple GPUs
To ensure Turbo Mode runs with maximum performance, we strongly recommend assigning your dedicated (High-performance) GPU to ACE Studio in Windows settings. This is especially important for laptops.
Navigate to Windows Settings > System > Display > Graphics.
Find ACE Studio in the application list. If it's not there, add it manually.
Click on ACE Studio, select Options, and set the GPU preference to High performance.
Rendering Timing
By Default
Local rendering starts when playback is triggered.
Pre-rendering
When pre-rendering is enabled, local rendering operates in real-time (after changes).
Rendering State
Un-rendered pieces are marked with a gray brace inside the time ruler.
Rendering Scope
The model dynamically detects the rendering range. When a small area is modified, only the modified area will be re-rendered.
Last updated