- Have you checked the voices in VI Pro to see if it is going red (overload)?
- What is your preload buffer set at?
- Are you using humanization?
- What is the maximum number of voices set to?
DG
199,344 users have contributed to 43,161 threads and 258,943 posts.
In the past 24 hours, we have 0 new thread(s), 3 new post(s) and 60 new user(s).
I also have a beefy system and have voice limit problems with Dimension Strings. The weird thing is that if I play the sequence a few times, the SSD kind of "wakes up" and will play it correctly. I'd love to know what is going on!
Same on my system. I play only one note and the voices run out ( red) and the sound break.
It seemed the drive (SSD) wakes up some time. But switching on release samples and velocity x fade it gets unusable.
For what a machine is this library made? Future rockets? You need 4 machines for violins,viola,celli and KB. And it still crackle.
I run 7 pc spread out all my librarys , but dimension still overload the voices.
Study the manual twice, just tryed the latest updates - no change
Rainer
Windows 7 Intel Core 3.07 Ghz - 24 GB RAM 1GBSSD Drive
Instruments pro
Ensemble Pro 5 Server
Hi Danny,
I´ve been trying to get my hands on a similar machine as you have, but without success so far.
The "ALL" patches contain 8 players, and if you are using Velocity Xfade and Release Samples, that quickly adds up to quite a high voice count.
I´ll see that I can check soon.
Best,
Paul
Anyone? Please? (Click click pop)
If you render offline, and your DAW informs VI that it's offline, and VI interprets that info right, CPU limitations should not cause audio problems; so it might be interesting for you to render offline and compare results.
In my case, 2 x Samsung 840evo 700gb. Preallocated voices: 8192. Max Voices 8192, Instance Voices: Max. Streaming Threads: 4. ASIO Buffer 512. Directory Manager: Dimension Strings, 8192; other libs: 2048
Thanks
MOH
Is there any update on why this might be happening? I need to play my sequence back at least 3 times before the dirve kind of "wakes up" and plays smoothly before I get voice count errors. Even at low voice counts of 200-300, depending on whether or not I've played through that part of my sequence.
Drives configured as single NTFS partitions on SATA III ports. Basic.
EDIT: After further checking, I see now that when I first load my template my RAM usage is at 35 GB. Then when I play my sequenceslowly starts to crawl upwards to 37GB. So it's like some cells are disabled even though I have ensured that they all are enabled.
@mohurwitzmusic said:
Is there any update on why this might be happening? I need to play my sequence back at least 3 times before the dirve kind of "wakes up" and plays smoothly before I get voice count errors. Even at low voice counts of 200-300, depending on whether or not I've played through that part of my sequence.
Drives configured as single NTFS partitions on SATA III ports. Basic.
EDIT: After further checking, I see now that when I first load my template my RAM usage is at 35 GB. Then when I play my sequenceslowly starts to crawl upwards to 37GB. So it's like some cells are disabled even though I have ensured that they all are enabled.
I cannot explain why your system behaves this way. Your machine should be fast enough to handle this kind of workload. It sounds like there is a bottleneck somewhere in the storage subsystem. Perhaps some drivers or BIOS needs updating?
Regarding RAM usage: I suppose this is the Windows RAM usage you are referring to? The VEP process usage should not increase during playback - unless you are running out of reserved voices inside of VI/VIPro. The Windows RAM usage may increase due to Windows disk caching.
Update: I redownloaded and reinstalled Dimension Strings and the problem went away. Not sure what happened. Thanks for your kind attention.
MOH