Ah, figured it out finally. vsti is new to me ( old midi hardware kind of guy). Hiding in the unfamiliar place.

Cheers

Just curious. How did you work it out?

Hi Hue,

Good question. The E-mu x3 is a royal pain for first time users and/or installing it for the first time into a DAW. You need to locate the VST folders ( which makes sense) and then even though you update the library and as a stand alone , it has to be added and updated again when you use it with the DAW vsti. Like anyone would know this. So, I spent months updating the library, and re installing it over and over. Now that I am becoming more familiar with my two DAW's, I flooked out. And it is making sense.

Its most likely my mind being bias to how Pro Tools works then thinking things are not working if it doesn't automatically install like digi things do. I often hate even posting my issues because most of all these issues are the lack of reading manuals, over looking things, or in my case, how things work with one DAW can really mess you up when "assuming" it will work like that with another.

Plus, I really loved my old midi setup with a MPC , real keyboards and a tape machine. I could compose songs one after another , day after day. All this CP stuff is one mass latency nightmare that I'm really disliking. The X3 is a royal pig that leaves something to be disired. And I have a 968 i7 that rocks but not so well with x3.

Latency. The worst thing about computer audio. Unfortunately it will never go away and gets worse the more plugins you use. Unless of course you are using a the $20000 dsp powered thing. I don't have to deal with latencies being too noticeable but it would be nice if it wasn't there at all.

hmm, I hear ya.

Well, I'm back up again after a long process of configuring. I've managed to do some serious editing tonight with near zero latency. I'm getting this X3 happening. I put the entire library on the sample drive in my i7 and it tightened right up! That's what I was having so much trouble over in the first place. I had to copy it all over from my C drive. For some reason I couldn't simply install it on the sample drive. Again, its most likely me "green" with PC's. ( was Mac before)

I have three drives. One for the OS, one for Samples (X3, BFD 2 )and one for audio which I think I'll double up on. Still to young at this new vsti system to be sure but I think the sample drive made the difference.

X3 requires a fast and defragged hard drive to stream the samples and an optimized PC no matter how fast or how many cores it has. Be aware that some of the optional smaller X3 banks can not just be moved or copied and have to unistalled and reinstalled to a new location. Also in the Prefs for X3 is a check box and drop down for multicore PC's. Then bump up the CPU cap to 80%.

It is also more productive to not use more than one or two instances of X3 as VSTi and route MIDI tracks to X3 than it is like many other soft synths that use one instance per sound/sample

The preference and how I installed it could be part of my problem. AG, what drive are you installing it on?

I have the program files in the C drive and the samples on the Sample/ G drive

AudioGaff, post: 350645 wrote: X3 requires a fast and defragged hard drive to stream the samples and an optimized PC no matter how fast or how many cores it has. Be aware that some of the optional smaller X3 banks can not just be moved or copied and have to unistalled and reinstalled to a new location. Also in the Prefs for X3 is a check box and drop down for multicore PC's. Then bump up the CPU cap to 80%.

It is also more productive to not use more than one or two instances of X3 as VSTi and route MIDI tracks to X3 than it is like many other soft synths that use one instance per sound/sample

Got it fixed up last night AG, that was it all. Thanks.