I blew $60.00 on v3.3 just to have fxpansion go tickering around with it to create v4.0 - which doesn't allow any vst plugins to function in Sonar 2. Sure v3.3 works fine, but that's not the point.
Everybody wants upgrades, yet the upgrade to v4.0/1 causes a 'DirectShow error [0x8004022A]' box to pop up disallowing plugins to work. DirectiXer works great on every plugin, but i'm not gonna spend more blood, sweat, and tears (= money) on another adapter. This is a real screw up in that Sonar is so popular. I have searched and found no fix or work around for this. Others have experienced this too:

http://www.kvr-vst.com/forum/viewtopic.php?t=7001&highlight=directshow

Come on fxpansion, please remedy this asap! This is one that shouldn't have been overlooked when coding v4.0/1.

Thanx..

Tim S Harris
win98se
directx 8.1
Delta 1010
optimized DAW
tharris4@jam.rr.com

ArtDude quoth I blew $60.00 on v3.3 just to have fxpansion go tickering around with it to create v4.0

Which adds facilities that users requested that 3.3 doesnt have, such as multiple outs . But of course noone makes you upgrade.

which doesn't allow any vst plugins to function in Sonar 2.

Total nonsense. Ive been using VST-DX 4 since the beta, and whilst the earliest versions had some problems with some plugins, but all that happened is that they didnt output audio. The problem was cleared up very quickly.

Sure v3.3 works fine, but that's not the point

Ummm, yes it is. If you consider the extra features of 4 unnecessary, then you didnt need to upgrade. So why spend more money to do so.

Everybody wants upgrades, yet the upgrade to v4.0/1 causes a 'DirectShow error [0x8004022A]' box to pop up disallowing plugins to work.

Never seen it. Are you sure you know how to use it properly? Until the final version came out I swapped between 3.3 and 4 several times a week depending on what I was doing, and even that was almost totally problem free.

Maybe you could try submitting a sensible bug report including the specification of your machine and the actions you took instead of this hysterical claim that 'it doesnt allow any plugins to work'.

Have you even tried emailing Angus? His support of users is amongst the best in the industry.

This is a real screw up in that Sonar is so popular. It's one of the three major seq's in the world. I have searched and found no fix or work around for this.

That may indicate that the problem is ot even vaguely common, or is user-induced rather than a bug in the software.

Others have experienced this too:

Who? I havent seen a single mention if this on the Sonar newsgroup, nor here, nor the Computer Music forums. Doing a search on Google doesnt show seem to show a single website mentioning anything similar. And I would have thought that if it was a common problem, there would have been a lot of traffic, since VST-DX is such a vital adjunct to so many Sonar installations.

I think you should start of by removing VST-DX completely, reinstall it from scratch, whilst taking a note of what you do. Point it at a directory containing one plugin and run it. Note down how it behaves. Open Sonar see what happens. Note down everything, bundle it with a description of your setup (OS, service pack, DirectX version, Sonar version, et.c.) and report it here in a more sensible, less histrionic manner.

Hi Artdude,

Sorry you're not having luck with 4.0... do you have the final version or a beta, and did you run VSTCONFIG again after installing v4.0?

The link you've hilighted does NOT appear to relate to the problem you're experiencing (and anyway refers to a bug that was fixed during betatesting, so is not present in 4.0 or 4.1 final release versions). I am 99% sure that this is either user error or system configuration error - VST-DX is very widely used, and believe me, if this "bug" was for real we'd know about it and have fixed it by now.

Like Whyterabbyt says, uninstall VST-DX and reinstall it (best to use 4.1, as it has some built-in registry cleaning abilities). If the bug is still there, email support@fxpansion.com and we'll get some diagnostics on your system.

I wish users would email the authors direct with these personal problems

some people could actually believe such posts are true..

Artdude wrote:

I blew $60.00 on v3.3 just to have fxpansion go tickering around with it to create v4.0 - which doesn't allow any vst plugins to function in Sonar 2. Sure v3.3 works fine, but that's not the point. Everybody wants upgrades, yet the upgrade to v4.0/1 causes a 'DirectShow error [0x8004022A]' box to pop up disallowing plugins to work. DirectiXer works great on every plugin, but i'm not gonna spend more blood, sweat, and tears (= money) on another adapter. This is a real screw up in that Sonar is so popular. It's one of the three major seq's in the world. I have searched and found no fix or work around for this. Others have experienced this too: http://www.kvr-vst.com/forum/viewtopic.php?t=7001&highlight=directshow Come on fxpansion, please remedy this asap! This is one that shouldn't have been overlooked when coding v4.0/1. Thanx.. Tim S Harris win98se directx 8.1 Delta 1010 optimized DAW tharris4@jam.rr.com

4.0 works awesome for me...I am using it with fruityloops, pro 5, and a few free vst's and it works so good I don't even think of it as a wrapper!! It just seems like Sonar supports vst's and that's it

4.0 works awesome for me...I am using it with fruityloops, pro 5, and a few free vst's and it works so good I don't even think of it as a wrapper!! It just seems like Sonar supports vst's and that's it

I always found that doing a "full reset" with the old version, then rebooting and then scanning with the new version helps to stop any errors.

Dave

I've also been using v4 since beta with SONAR2 and have never had this DirectShow error either....been working perfectly for me.

Please forgive for possibly scaring people away from vst-dx adapter!
Naturally common sense tells you a well know product as this will definately work on most systems or fxpansion counldnt stay in business. Its just that:

1) Ive tried all the suggestions above (i KNOW how to work it) and no success.
2) Ive been working on and servicing pcs for over 10 years so i understand the 'in an outs' of software and hardware (programmed in object pascal for 2 years). Ive had Sonar 2 since it came out - i know it and vst-dx adapter well.
3) My daw is thoroughly optimized and i use high quality components - P4, 512 mushkin rdram, asus board, matrox 450, 2 Deskstar drives, and a delta 1010 card.
4) And most of all, i formatted, did a fresh install of win98se, dx81, sonar2, vst-dx adapter (v4.1), and sound forge.

...and STILL the same d*nm directshow error message on every vst plug i try to apply to a wav clip. The vsts work fine when you run them in real time from a track. I just dont understand it. Thats why i said it had to be a flaw it the new version (v3.3 works fine). The link i provided above does 'indirectly' give a hint at what the problem 'could' be. The responder said:

'4.0b4 interfaces to DirectShow rather differently to v3.3, and will break some "weaker" DX hosts, but Sonic Foundry's hosts should work well in this respect'.

He may be right or wrong but all i know is everything is setup properly on this end, v3.3 works fine, and so does directiXer. I had the Klez virus, but i cleaned it and formatted my partition. Im at my wits end. It has to be supernatural or something
the adapter should be working ...AUGHHH.

Anyway, thanx for your posts..

Art
p.s. i have a pic of the error messege Angus if you would like to see it.

Any particular reason you're running Sonar under 98, BTW?

Ah, well THERE's the critical bit of info you missed before

*when you try to apply a DirectX effect to a track*.

Sometimes SONAR tries to process clips offline at 16-bit; the adapter insists on 24/32bit operation (which is what SONAR, and every other modern audio app, uses the rest of the time). Try running your projects as 24-bit rather than 16-bit, or process the clips in a different way (trackbounce, or launch them in to SF/CEP/WL if you have one of those set up that way).

The DX changes you talk about that I mentioned in the other thread are something different. Namely, VST-DX 4.1 uses different buffers for input and output, and a few very weak DX hosts can't deal with this.

Regards,
Angus.

Didnt even notice that was you Angus who was the responder on that thread link. Anyway, the vst plugs worked in 24 bit mode. Im still presently using 16 bit, as are most or at least half of the daw population, so i typically thought vst-dx adapter would work well with both formats.
But dont get me wrong, im all for increases in technology and higher sampling rates. We are on our last tune in 16/44. We have already planned on recording 24/96 after this song, as well as upgrading to winxp (bad timing i guess for the negative post ).
So all in all that's good news about vst-dx adapter, especially the upgrade to multiple outs.
Again, sorry about all the mess!

Art