I'm curious why the Reallocate tweak seems to work the opposite of how I would expect. My mental model would be "If I have the voices set to reallocate, then I would expect a new voice to be allocated each time I press the same note." But in practice, having Reallocate = ON *keeps* the same voice (to my thinking, that means it didn't reallocate!).
This might be just a question of semantics. If one thinks of reallocating as "allocating again" then you could either mean you want to change the allocation (my mental model) or "allocate the same voice again" (apparently how it's designed).
Anyone else feel like it's backwards?
Why does "Reallocate = ON" do the opposite of what I expect in Repro-5? :)
-
- KVRer
- 28 posts since 11 Mar, 2025 from Seattle
Recording Setup: Mac Mini/12C CPU/16C GPU/24GB/512GB (2024), MOTU M2 Interface, Logic Pro 11.1, u-he Diva, u-he Repro, Cherry Audio Mercury-4, Cherry Audio Memorymode, Cherry Audio DCO-106, Yamaha HS 8, Sennheiser HD 650
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
But "to reallocate the same voice" is exactly the opposite as "to allocate a new voice". Hence, the "re" in "reallocate" means it allocates the same voice, as opposed to a new voice.
-
- KVRer
- Topic Starter
- 28 posts since 11 Mar, 2025 from Seattle
Thanks, Urs 
I think it's one of those things like flammable / inflammable or regardless / irregardless.
In any case, a great feature.
I think it's one of those things like flammable / inflammable or regardless / irregardless.
In any case, a great feature.
Recording Setup: Mac Mini/12C CPU/16C GPU/24GB/512GB (2024), MOTU M2 Interface, Logic Pro 11.1, u-he Diva, u-he Repro, Cherry Audio Mercury-4, Cherry Audio Memorymode, Cherry Audio DCO-106, Yamaha HS 8, Sennheiser HD 650
