i'm glad it's not just me then. :) Before, I could load my entire string section going through MIR without any trouble like this before.... even using Velocity crossfading. Now even just sustaining a single note can produce the CPU fuzz described. I am looking at SSD options. Angel crest rep emailed me about some new external SSD drives that will use eSATA/USB3, however I DO have the required AND recommended setup for DS and wish it worked so.
-
I've also had VI Pro crash on me while loading DS a couple of times. Loading from an SSD-drive, 24 GB RAM. i7 960.
-
Just updated to the Oct 4 build and I'm still getting the same weird noises/artifacts/cpu jumps even when doing things NOT complicated. Thanks for your help!
-
-
Hi everybody,
I'm experiencing the same issues loading VDStrings, except for the CPU problems. With the previous VIPro version I've never had clicks or pops at all...Besides that, whatever I load in VIPro (VDBrass or any single instruments) everything works perfectly.
I've also tried to raise the latency, up to 1024, with no result.
I thought 24 GB of ram would have prevented such pop and clicks (and sudden stuttering) issues. In addition to this, my computer is "empty", in the sense that does not contain any Windows programs or else. It has been optimized for music production and audio.
Please, give us a hand.
Thanks for your support.
CPU model:
i7 950
CPU speed: 3.05 GHz x 8 core RAM:
24GB Soundcard: RME HDSPe RayDAT Operating system: Windows 7PRO
-
@MS said:
Miki,- Are you using SSD drives?
- What is your voice count when clicks and pops occur?
Hi Martin.
no, I own SATA drives and I can't tell you about voice count because clicks and pops seem not to occur anymore. It is a bit weird, but now it works. The "strange" thing to me is that I have to load each single preset manually, double-clicking on every single cell...
Before last updating, I could just load everything just clicking on (down right hand side) "load". Now, it does not work that way anymore...
Thanks.
-
If you want to always load all cells of a matrix/preset, without having cells enabled on midi activity or by doubleclicking cells, you can activate "Force Enable Cells" in the VI Pro Settings. RAM usage is pretty high with DS however, especially if you run spinning-junk drives. Since DS requires a high voice burst performance, instantly activating up to 32 voices with every pressed key, SSD is definitely recommended.
-
No not SSD, 7200 RPM eSATA, it's occuring with higher voices (256-512) and even with very low voice counts just switching cells. Even holding 1 note. Or the 1st note make a 'AAANNNK'. I am about to purchase a brand new line (not yet out) from http://www.angelbird.com/ called the SSD2Go (portable 480G SSD eSATA/USB3 keep a look out). YAAY!! But, again I have the required and recommended setup. It's never performed this way before. I know you'll figure it out. :) Much faith in your team.
-
You are using the latest version of VIPro, v2.3.11630?
Please be aware that burst performance with regular 7200rpm drives is not very good, they can only handle some 30 voices of simultaneously triggered samples at 16384 samples buffer. Running the DS 8-violin patches with Vel-XF enabled can trigger 32 voices on each keypress.
-
Perhaps the Requirements/Recommendations on the Dimension Strings Area should be changed to Requiring SSD drives. Still seems weird for it occur at low voice counts or starting note. Not to mention I usually have the ENTIRE string section running at once ALL using Velocity crossfading/cell crossfading, So it's seems weird to not be able to play even JUST the Violins of Dimension. I am ordering an SSD drive from Angelbird. (SSD2GO) Maybe you should sell the stings bundled on one of their NEW portabe SSD drives. :)