@Sapkiller said:

so I'm the only one having problems with this?? [*-)]

I am experiencing this issue as well.

I have the library spread across 5 hard drives. All SATA.

Sometimes I get a click sometimes I don't,
Does not matter if used as plugin or stand-alone.

Hi paul
Well - it seems that this is only a problem when the VI Gui is opened - if I
close the VI window in my host the popping stops.
Minimizing it does'nt eliminate the problem but seems to lower the frequency at which poppin' occurs.

so its a VI graphical update issue interferring with the audiostream?

Just to chime in - I'm experiencing the same thing. And, I've noticed that closing the instrument window helps. I can't tell you if it happens in standalone as VI doesn't recognize my Midiman USB Midisport 8x8/s

My system = Intel dual 2.4 Xeon processors, Windows XP SP 2, 4GB RAM, Sonar Producer 5.2, M-Audio Delta 44 audio card (latest drivers).

For what it's worth, I'm also using an nvidia GeForce3 with driver versions 4.3.4.5 (3/20/3002). I'm downloading new video drivers right now to see if that improves things.

Edit: I missed the fact that there appears to be a VI update. It's not immediately obvious to me how to check what version you have. Anyone know? I'm downloading regardless, and will try updating to see if it helps.

@Another User said:

It's not immediately obvious to me how to check what version you have.

Hi James,

you can check the VI version number when you're in Preset Select mode, it shows on top of the list in the left-hand window.

Regards,
David
VSL manuals

Just to follow up... My install disks say v1.05, so I presume that's what I had before I upgraded to 1.06. Updating VI and my video drivers made no difference - I'm still hearing the crackling in Universal mode when playing a sustained note and moving the mod wheel, but only when the VI window is open.

Do you have a two-screen setup? I use a Matrox G500 with two screens, and quite often get crackling when something on the secondary screen changes or when I move windows between the screens. Could it be something like that?

Cheers,
David

No, I only use a single monitor, so I'm afraid that's not it. I tried disabling hardware acceleration, lowering resolution and bit depth, to no avail. Short of buying a new video card (which I'm not going to do until I'm sure it would solve the issue), I'm not sure what else I can do on my end. Fortunately, it's not a showstopping problem, as I don't typically leave the VI windows open for long (with my limited screen real estate). Still, I'll provide what info I can think of to help the devs solve the problem.

I don't think I'm experiencing the same thing you are David. It's more like Sapkiller described. Easiest way to reproduce this: Play a note with Orchestra Violins Universal Matrix with mod wheel all the way down. If I fiddle with the mod wheel while the VI window is up, then I get breakups of the audio stream when I cross control boundaries. If the VI window is closed, then no such distortion occurs. Based on what sk said, I also tried different crossing speeds, and can confirm that it only clicks when you move the mod wheel somewhat quickly across boundaries. Moving very slowly seems to eliminate the pops.

Txh james - nice to know one's not alone with this matter.

It maybe a Sonar issue with VST plugins ( would'nt be the first time )
Maybe we can get our logic and cubase friends to try out the procedure?
And also other Sonar folks?

This way we may get a clearer picture.

Sapkiller,

I had similar issues on one of my slaves and I went into BIOS and 'disabled' hyperthreading on that PC. Someone told me that VSTACK does not support it (HT).

Turned it off and no pops/clicks. Helped here.


Rob

@Sapkiller said:

Txh james - nice to know one's not alone with this matter.

It maybe a Sonar issue with VST plugins ( would'nt be the first time )
Maybe we can get our logic and cubase friends to try out the procedure?
And also other Sonar folks?

This way we may get a clearer picture.

Actually, it would be the first time for me. I have a couple other commercial VST plugins, and this is the first time I've seen any sort of compatibility problem.

It definitely looks like some sort of Sonar compatibility issue, because I can't reproduce this in standalone mode, and we have fairly different hardware configurations (I have dual Intel Xeons). I'll make some work of reporting this over on the Sonar forums.

On a somewhat related topic, I actually have Sonar 6 Producer ordered and on the way, which has native VST support instead of a DXi wrapper. That gives me some hope that this issue might go away.

@Rob Elliott said:

Sapkiller,
I had similar issues on one of my slaves and I went into BIOS and 'disabled' hyperthreading on that PC. Someone told me that VSTACK does not support it (HT).
Turned it off and no pops/clicks. Helped here.
Rob

Don't think that is a problem with Sonar - it supports both multithreaded and multiprocessor operations.
But thx anyway

well, I've had problems with DFR Superior (graphics and pops, which is partly a well known issue) in Sonar, so its not the first time for me.
Hope you're right about Sonar 6 though - although I was under the, apparently wrong, impression that VST is native in the Sonar 5.

And you're right: pops are not an issue in standalone mode.

@Sapkiller said:

well, I've had problems with DFR Superior (graphics and pops, which is partly a well known issue) in Sonar, so its not the first time for me.
Hope you're right about Sonar 6 though - although I was under the, apparently wrong, impression that VST is native in the Sonar 5.

And you're right: pops are not an issue in standalone mode.

Well, I just got Sonar 6 installed tonight, and it made no difference. I'm still hearing the exact same problem.

I don't suppose anyone at VSL can let me know if they can reproduce this issue?

Hmmm, there is definitively a problem with the VI GUI [:(]

I've posted a thread a few months ago about this :
http://community.vsl.co.at/viewtopic.php?t=8928">http://community.vsl.co.at/viewtopic.php?t=8928

Vsl, please give us an official answer