I know that there are special patches of noises and effects for the Dimension Violins, but I'm hearing constant thumps and noises when using sustain patches eg the basic sus-Vib.
Is there any way to regulate these noises or turn them off completely?
-
Dimension violin noises
-
I've experienced similar issues - it's not necessarily system overload as I'm running off SSDs and passages of a given intensity of instruments / notes appear fine while others sound like someone's whacked the wall - and the disk / CPU / memory usage off the monitor don't appear to particularly jump at these points, I'm using 8 individual DS staff lines and the problem seems to occur irrespective of whether velocity cross-fade is switched on which I appreciate adds to the load.
-
To put some context on the earlier comment, I use Sibelius to drive Mir Pro using Andi's standard presets, the latest Strings soundset, the updated house style and latest versions of all software including the recent VIP Pro update and the noises occur even when not switching between cells and are not limited to the sustain patches. The staves were created using the Dimension Strings entry and all routing between Sibelius / Mir Pro / VIP Pro / expected matrices / cells appears to be working as expected.
I copied a staff showing the problem to an empty manuscript and the problem appeared to largely go away - then added further individual DS violin lines and the problem seemed to re-occur getting worse as the number of DS violin lines increased. While this seems to suggest a performance limitation as stated earlier I'm already running all samples on SSDs (2 x 480Gb) and it seems unlikely to me that a few DS violins would max out when I've happily run fairly large numbers of instruments off this configuration. The only change I've made to the default presets was to set velocity cross-fade on but this doesn't stop / increase the problem.
Any ideas?
-
Andi
This is performance related. I increased the pre-load buffer size in Directory Manager from 1536 to 2048 for the Dimension Strings and later the other strings using the same SSD and it improved significantly. As it's a performance limit, I've switched off velocity cross-fade as well.
The moral of the tale would appear to be that Dimension Strings is very demanding of the system - looks like a 3rd SSD and/or increase in memory will have to be on the cards at some point especially when you release the rest of Dimension Strings!
Dave
-
Everything works flawless for me, and I don't use SSD drives at all (just WD Cavier Black HD's),
just increase the pre-load buffer size until your problems go away, being able to use velocity cross-fades etc is far more important than saving a couple of seconds in load times because your buffer size is too small.
I think SSD performance is over rated, they are not the answer to a gitch free system.
-
Andy, thanks for the feedback. I'll play around with the settings to reach a compromise that works best for my setup. In my case your 'few seconds' was the difference between waiting an unacceptable 20 minutes to load a fairly large template at the start of a session and a more reasonable 5 minutes when I started using SSDs. In hindsight using the most aggressive pre-load buffer settings is clearly not the best route - a path I'd taken to maximise the number of instruments sample variations I could safely run given my current memory configuration.
-
Martin
Two Intel 480Gb Series 520 SSDs - working off a 4 port SATA III PCIe card (motherboard didn't support SATA III and had run out of interfaces).
The VSL samples are spread over the two SSDs - brass and strings sharing one and the rest on the second.
At present the OS / applications are on conventional drives.
Dave
