The time has come for GPU rendering!

Hi team!

With the release of the choirs (which are totally mind-blowing, btw…), rendering a four-part standard choir takes a long time.
My 12th-Gen i5 is not the latest, but certainly no slouch, and has always performed fine with single voices.
Now, rendering a choir with 64 voices in total takes quite a while.

So: Please consider a CUDA or Tensor Core based render path for SynthV.

Thx,
Benji

4 Likes

VSL have that option for their MIR reverb, but it is quite expensive (cheap compared to MIR, but these things are relative). Might not be straightforward to implement.

I got this answer from ChatGPT to this problem, and it helped a lot.
Two things are causing the constant “Rendering Vocals” from Settings / Rendering
:

  1. Your Live Preview thresholds are too sensitive

  2. Your cache is already large (2.33 GB)

Let’s optimize specifically for SATB choir workflow.


:bullseye: What’s Triggering Constant Re-Rendering

Look at this section:

Max Number of Notes to Trigger Re-render: 3
Max Number of Quarters to Trigger Re-render: 4

That means:

  • If you edit just 3 notes

  • Or move anything longer than 1 measure

  • SV immediately re-renders.

With 4 voices, that becomes 4x rendering.

That’s why it feels constant.


:white_check_mark: Fix #1 — Increase These Values (Biggest Improvement)

Change them to:

Max Notes: → 12 or 16
Max Quarters: → 8 or 16

This tells SV:

“Don’t re-render unless I change a LOT.”

For choir arranging, this is much better.


:white_check_mark: Fix #2 — Turn Off Animated Rendering Status

Uncheck:

:check_mark: Show Animated Rendering Status

It doesn’t stop rendering,
but reduces UI lag and makes it feel smoother.


:white_check_mark: Fix #3 — Clean Your Render Cache (Important)

You have:

Current cache size: 2.33 GB

That’s high.

Click:

Change Cache Location →
Then manually delete old cache files from the folder.

Or:

Lower Render Cache Level temporarily to:

  • Cache phonemes and pitch only

Instead of:

Cache phonemes, pitch and rendered audio

This reduces disk read/write while editing.

For composing, you don’t need full audio caching.


:white_check_mark: Ideal Settings for Your SATB Church Projects

Since you:

  • Write 4 parts

  • Edit phrasing

  • Then export

Use this setup while editing:

  • Cache Level → Phonemes + Pitch only

  • Notes trigger → 12+

  • Quarters trigger → 8+

  • High buffer size (512–1024 in audio settings)

Then before final export:

Switch back to:

  • Cache phonemes, pitch and rendered audio

  • High quality render


:rocket: Bonus: SATB Performance Trick

When working:

  • Solo the voice you’re editing

  • Mute the other 3 voices

SV only re-renders audible tracks.

This alone can cut rendering time by 75%.


2 Likes

I followed your instructions, they seem very reasonable. But nothing has changed… :frowning:

The description see above, I have also consulted with AI before. But the main improvement that I suggested to AI (and it probably occurred to everyone) is the creation of multiple groups on one track. And AI approved it and added suggestions for improving the work that were listed above. However, I believe that these suggestions from AI are based on AI’s consideration of other verified information for similar applications where it has proven successful. But this improvement did not come from Dreamtonics. It will be good to wait until the user manual from Dreamtonics mentions it or when several experienced users will deal with it in detail and exchange experiences here on the forum, if of course they find the time to do so, which is quite expensive and maybe it would be better for them to devote themselves to creative musical work.

1 Like

Obviously, my feature request still stands. If anybody can pull it off, it’s Kanru and his team!

B.

2 Likes

I’m having the same trouble with writing things for a 4 part choir, with 4 parts in each voice. Can someone please tell me where do you find these settings? Thanks for the help with this! Just an extra note - I have a good cpu and 64 gigs of ram also.