Time Machine Pro limited to 4 voices in HQ-mode and w/o a voice button

In my Kontakt 6.5 version there is no voice button described in the manual and the number of voices is limited to 4 sounding voices. Although the HQ mode sounds really good at expanding the human voice beyond the range actually sung (because of the formants being held), it would not be useful for choral use due to the limited number of voices.
Why has the button that is still shown in the manual for 6.0.2 disappeared. Mistake or intent?

Image, shown in 6.0.2. Manual Screen shot of Kontakt 6.5

So that others don't have to look for a solution like me, here is a suggestion (maybe I just overlooked something):

The ingredients for solving the problem can be found in the KSP Reference Manual
14.8. set_voice_limit ().
The following script allows you to set the number of voices for both modes:

-----------------------------------------------------

on init

make_perfview
set_ui_height_px(50)
declare ui_value_edit $Voices (64,2,1) {max value 64, min value 2}
declare ui_value_edit $VoicesHQ (64,2,1)
make_persistent($Voices)
make_persistent($VoicesHQ)
declare $change_voices_id
declare $change_voicesHQ_id
$change_voices_id := set_voice_limit($NI_VL_TMPRO_STANDARD,$Voices)
$change_voicesHQ_id := set_voice_limit($NI_VL_TMPRO_HQ,$VoicesHQ)

{trying to understand what is going on. Remove the {}-brackets}
{message($change_voices_id & " " & get_voice_limit($NI_VL_TMPRO_STANDARD))
message($change_voicesHQ_id & " " & get_voice_limit($NI_VL_TMPRO_HQ))}​

end on

on ui_control ($Voices)

$change_voices_id := set_voice_limit($NI_VL_TMPRO_STANDARD,$Voices)​

end on

on ui_control ($VoicesHQ)

$change_voicesHQ_id := set_voice_limit($NI_VL_TMPRO_HQ,$VoicesHQ)​

end on

on async_complete

if ($NI_ASYNC_ID = $change_voices_id)

message("New TMPro Std Voice Limit: " & get_voice_limit($NI_VL_TMPRO_STANDARD))​

end if
if ($NI_ASYNC_ID = $change_voicesHQ_id)

message("New TMPro Std VoiceHD Limit: " & get_voice_limit($NI_VL_TMPRO_HQ)) ​

end if​

end on

--------------------------------------------------------------------------
I hope this editor didn't damage the listing.
When Creator Tools is open, you can see the changed values directly. You don't have to set anything in Creator Tools for this. Every change appears in KSP Log.

The moderator EvilDrageon wrote on February 19, 2019: “TMPro can be a CPU hog, yes. Especially HQ mode. "
I wanted to know how heavy the cattle really are. Two computers were available:
1) Intel i7-4770 (4 cores + 4 virtual), 16 GB RAM
2) AMD Ryzen 3950X (16 +16). 64 GB RAM, PCIe 4.0 memory connection (> 3 GB / s)
Contact 6.5, loaded with 2 instruments with a limit of 128 voices each in HQ mode.

Result
Regarding 1) Only when the number of votes exceeded 150 did the cracking start, because “CPU overload disabled”. With "relaxed" about 100 HQ votes were possible before the limitation set in.
Regarding 2) Over 250 HQ votes only resulted in a CPU load of 30%. Also feasible in Cubase 11 as a plug-in without any problems.

Even if a computer has something else to do besides playing Kontakt instruments, it's not quite as bad with HQ as I initially thought. In any case, the limit problem is solved for me. But I still want to have the question answered:

Why was the voices button removed in HQ mode ????

Best regards


Mike Kirm