Actually...is the SDK not making OpenGL calls? 

I have been through about every performance setting on my Nvidia control panel. I can improve the situation by dropping windows to 16bit color. But, who wants to do that? It doesn't completely go away...but, it does indicate that the graphics card, graphic OS subsystem/drivers interplay are what's causing lag and high CPU usage on certain systems. 

I don't remember, did I run the above test for you? I know I ran a utility that spelled out every API call the card would accelerate...but, I don't know if I made the broader system config file...

It is...but, the system specs should help the team working on it. Thx. 

If we get into a vote, I've had ZERO synchro soft issues...yet, have had iLok issues with both the iLok 1 and now 2. I had to break out diag tools to diagnose and fix my own ilok2 issue...which it turns out affects every install of Win7 that is not actively on a network. 2 months after I reported in detail the problem and fix, I got a note today that they're writing up a knowledge base article. 

Anyway...i bought an iLok 1 for a single app--caused config issues in XP years ago...bought a 2 for a second app and while I ultimately fixed it for them, it caused the software I bought to not actually work for the first week or so of ownership. Time that should've been spent mixing was spent diagnosing and resolving the issue. Not to mention the time it takes Waves vintage series to open. Yank the iLok while you wait--it'll barf...that's what its waiting on. 

Two strikes. Ask me if I'm ever going to buy anything else that goes on an iLok. I vote hells no. 

Bump to put this original thread right next to two newer, GUI related threads...making it easier to cross reference for common threads. 

Maybe you could post you system specs? In this (Rdc) both video card on the Mac and video card/CPU on the PC will factor in. 

Should really consolidate these into a single thread. Get all the affected systems in one place. 

I think everyone on the Windows side assumes you're building it yourself. But, a hex core, pretty sure that's the cost of the CHIP...there's a single 6 core intel that's about $500usd...the rest are closer to $1k....just chip costs. 

Are you 100% sure it's ONLY on Rdc? I mean, if you plug up a local monitor/mouse does it not drag? Ive been working with Martin to optimize the GUI's CPU usesge on Windows. It's the only VI I own that Shows any increase in CPU usesge just displaying on screen--minimize it, the CPU usesge goes away. 

RDC is using a special terminal services video driver...thus, I would think its related. If the GUI hits the host CPU hard, having a terminal session convert it to that transport is going to be even harder on the system. 

I really wish they would gut the GUI and start fresh with an API call based, reSizable win32 GUI. The Instrument itself is magical, and SUPER CPU efficient. The GUI is a resource hog--albeit a bit less of one with the latest beta build. Still, why it uses so much CPU where bfd2, Kontakt, B4, Atmosphere, and any other doesn't use any noticeable CPU time, is a significant issue. When your GUI takes more than the sample/synth/filter/reverb/pitch dsp, that's an issue. 

Does it change if you reduce the color depth of the Rdc session?

Sorry...you're just looking for ways to control vsl. I've yet to sit down and really contemplate the ways I can control it with the Kronos's couple joysticks, ribbon, buttons, faders, knobs...I would think the humanize slider would be a no brainer...maybe the lpf....I don't have any vsl wind samples...

Yes...supports CoreMIDI over USB or dock connectors...but, how is it a replacement for a controller you BLOW into?

What are you using now?

I think he means without instruments (ie Kontakt)...otherwise, with VE loaded, not doing anything. 

Im still weirded out by the idle CPU usesge of sample players. Omnisphere is a different beast...but, none of this talk makes me want to take my Macs down to the studio. 

LASS is a hog on K4...relative to VSL or QLSO/PLAy3...BUT, what strikes me as odd is that you see CPU use go up in a sampler without anything playing? It should not touch the CPU until its playing back samples and running its auto arranger scripts and calculating glissando time stretches in RAM, etc. I find it suspect that you open an instance and it eats 20% of your (albeit older) Xeon. Are you sure you've let it fully load before reading CPU usage? Kontakt and vsl both do that thing that everyone but me likes--loading in the background. Kontakt will call itself loaded at like 10sec...and then proceed to continue loading for another 45sec in the background--if a machine is actively loading huge samples to ram, it will register elevated CPU time during the load unless you have some really pricey SCSI drives/controllers. 

And 1024? Yikes...I didn't use over 256 on occasion with a 10 year old single core P4. Let alone on the c2duo iMac, that never went above 128...I think you have something wrong. 

I would buy a bc3 in a heartbeat for my Brass2 and MojoHorns, along with the Kronos horn samples. I find it odd in this day and age that no one makes a breath controller. The Akai is more--it s amid I brass controller that you are intended to hold and play. It's odd to be that there is no headset format bc like the old Yamaha. 

Bad news...have the latest echo drivers. Not been updated since 2/2010. However, it did get me to read the "read me" on the driver set...it says under known issues "if you experiences glitches or distortion while recording, disable unused inputs/outputs in your DAW software". So, I have disabled the ADAT IO, which is only occasionally used. Can't rerun my test though, as it uses the extended libraries, which apparently just ran out. doh! Since my real world projects are not glitching since the update (only the stress test project I made)...I've got no way to see if that helped. 

I also found a setting in Cubase to boost the audio priority. I've set that to boost. 

Also on the graphics card...didn't mention--the drivers for the Quadro cards are meant for more window and openGL acceleration (intended for CAD use) versus the GeForce line. I know the CAD engineers at work require Quadro and FireGL cards even though the "consumer" lines are technically "faster". avid only certifies Quadros for use in HD rigs, too. 

What CPU are you running with the 9800gt? Do you see the CPU jump significantly with the GUI open? I'm running a fanless 9500gt/1gb with a core2quad 2.5ghz.  Martin's testing with a i7/Quadro. I do also believe its using the CPU rather than hardware acceleration. However, the problem gets far WORSE with aero (thus graphic acceleration) disabled. 

Im going to continue to use it with the newly disabled IO. Seems like a weird thing that disabling IO that aren't being used would change performance, but it does say that in the driver read me, so...We'll see...once I actually get the money together to buy the extensions, I can rerun the test project. 

EFI is the Mac equivalent to a BIOS on a PC. Does that help? If Bootcamp made it, it's likely a boot loader partition that is 100% needed, as it is the active partition that the EFI chips boot to--it contains config files and a boot loader app that allows you to choose which OS to boot. It may also contain a software emulated BIOS for Windows install to use to communicate with the EFI chips on the mobo. 

My only other audio interface has no 64bit drivers. Old Maudio 2496 card that had the best GSIF drivers of anything I used back in the day--and I went through a billion. This is the only thing that has made this system even hiccup. And it's just the GUI for it--leave it PLAYING, open any other GUI all day--no glitch at all. 

Technically speaking, I actually don't think my video is as feature rich as the Quadro, which is native DX11 accelerated and has a faster memory bandwidth, and if memory serves, more "cuda core" pipelines. 

My local buddies all have FW, which I guess I could borrow, but does put another layer of driver/controller compatibility into the mix. 

I have the iMac, but them there's nothing similar. I'll see if Echo has updated their drivers since build. Since I've now updated everything ELSE as part of this. 

Also note at 256 samples...zippo glitches. Still very playable(live), as the nature of strings and the "no hidden buffer" feeling of the VI engine does not add up to anything to be concerned about. And I'm bugged by latent software instruments. 

Thank you so much Martin. 

I just sent him my test results. While still more CPU usesge than any of my other VIs (none of which show significant difference between GUI opened or closed)...it's WAY down from what it was. And in my "real world test" (as opposed the shared test project we've been using) its working fine at 128samples on full arrangements with only occasional minor audio glitches. 

While I CERTAINLY welcome further improvement, I want to thank Martin for working on this so diligently. I did go ahead and buy my permanent vip2 license. Being in IT, I'm glad to help and also understand the development cost calculations that can equal a company having the attitude that it's not worth the development time to make code more efficient. I want to publicly thank VSL for perusing GUI optimization despite it running great on i7/Quadro powered machines. I know I, for one, would rather spend money on more VSL samples for vip2 than on building a new box that wouldn't matter if the GUI were optimized or not. 

Thanks you. I look forward to the official release as well as any further testing I can do for the team at VSL. There are not a lot of software products I honestly LOVE(I am a hardware guy at heart)....these samples played with the vip2 engine...I do. The sound of strings I've always heard in my head are now under my fingers. 

There's nothing to tweak for ram usesge on a 64bit OS. Fwiw. I have 8gb and have never been able to max it out. Bfd2 huge drum kit...Scarbee pianos and mojo horns in Kontakt...PLAY engine QLSO gold...individual VIP2...and also, fwiw, if you buy VIPro2 (and you should-world of diff)...and put the VSL samples on a solid state drive, you can reduce the amount buffered into ram significantly--meaning you need even less ram. And, well--it should load a lot faster. 

Anyway, you should do 9 or 12 if the machine is triple channel. My old c2q is 8gb max-dual channel. Ram is so cheap, it's no longer really a big deal to get more than you need. 

I'm sorry...I should have specified to look at the threads in TM of VEP and total that ram. Unless your machine has been configured with the /3gb switch, it will only allow user mode access up to 2gb...considering there can be some overhead for startup cpls and such, if the VEP is APPROACHING 2gb, you will run into trouble. You can google the 3gb switch for xp and up that to 3gb for user mode, which I had set for years...it meant I got about 2.7gb of cubase sample ram. That old machine had Gigastudio, which uses kernel mode ram, so I could load more on top of that, but using vsl and others insider cubase got unstable after about the 2.7 range. That still a bunch of articulations, though. I could load cello/viola/violin of my solo and chamber strings-perfect legato and the various articulation single note patches. I mean, I guess that's only "6 instruments"...but, that's fairly full articulation loads. Then I'd optimize via the VI GUI once the part was there...

It's simple...task manager...performance tab--shows ram usage. 

You don't really mention your OS specifics...4gb if 32bit may not even be being utilized. More accurately--it is NOT all being utilized--the only question is to what degree. The max I was able to squeeze out for a user mode app was about 2.8gb in 32bit Windows--and that was with customization to make that happen. 

You're not running out of CPU unless maybe you have the buffers set to 32samples or something. My full string arrangements with impulse verbs, etc, don't eat 25% of my c2quad at 128 sample buffer. I Ran the original VI for years on a single core P4/4gb machine. VSL OS not CPU intensive. Now, of you're opening play or Kontakt4 libs in VE, that changes. 

What you want to do it to be looking at task manager in real time while you have the arrangement playing back. Do you see CPU(s) spiking? If you're out of ram, that will certainly cause it...but, that's easier to determine than fix if 32bit OS. 

You want to change your title. You're asking about Hard Drive space requirements...not memory. 

I don't have the woodwinds to answer no much room is needed. I'm sure tech support could answer...but, if you're going to use VIPro2, with it's time stretched articulations, you need to add a big chunk to store the stretches. My chamber and solo strings that took like 80gb are now taking 102, and I can assure you I've not yet opened all the new stretch matrices. 124gb is the total the website claims for the two--so they may have updated them to include the preset stretch data of vipro2. 

5 or 6 channels? And you get clicking? Increasing ram only increases speed of what you're doing is running out. 8 gb? 5 VSL instruments? I've got 8 gb and can pretty well load the entire contents of the solo and chamber strings. I don't think you're running out. Are you trying to solve the clicking? Just increase the buffer on the PC. 

Actually, is the clicking in the vsl sound ONLY...or all of Logic glitching?