ORIGINAL: ttoz

are we only talking xp64 here?

Nope..where did you see that? It's 7.01 it seems..too many VSTi's behave bad or crash..

PS. crash_3210 is the man!!!

Amplitube 2; sorry....

Chuck

ORIGINAL: crash_3210

AT2 ??? is that Auto-Tune 2 ???

i didn't get the chance to test the reported plugins on 7.0... i installed it and updated it instantly....

installed S7, restart, run S7, install 7.0.1, run 7.0.1, restart.... i mean it can never get cleaner than that....

IMHO -

At this point it's time for Cakewalk (or CW+some help from Microsoft) to develop a utility for checking ALL the Windows components (versions installed, missing..locations etc.) necessary for Sonar to run as it should.

Two versions already (6 and 7) with lots of hit and miss patches (upgrades that make things worse), suggestions like "format and reinstall Windows" - all that can be avoided if there was a utility to verify your "system"..this will also show that Cakewalk in on top of things, know sepcifically what can impact Sonar running as it should and not just guessing (at the tech support) what's corrupted on each computer. This will also save lots of headaches... Sonar users don't want to look for files and find solutions such as checking versions and installing stuff..it's all too technical and makes it hards for CW to realize where the bugs actually exist in some cases.."your system configuration" can't be an excuse for everything - at least publish a list (besides all the REG keys) of other system files and causes that might make your Sonar much less stable. The C++ problem is one good example - people get that in many different situations and don't know what to do really.

Why should Cakewalk or Microsoft check to see if you jacked up your system? If you screwed up something in your system that is your fault. If you built a machine using cheap parts, that's your fault.

Gee..you didn't get my drift at all. I'm not talking about hardware at all or people who "screw up" their systems..not talking about virus infected machines, spywares and such.
I'm talking about DAWs that might have this .net version or another, that C++ libraries or others.. the regular stuff we often see here in the forums.

The issue that we're discussing here is a few third party plugins that don't work

All those "few 3ed party plugins" used to work in Sonar 6! There's something about 7.01 you know.. read the first few pages of this forum again.

Not trouble shoting your system problems.

Right, I just repeat what I said in some other threads a long time ago, especially the C++ errors which DO seem to bother some with specific VST's but sometimes not at all.

I simply believe that if there was a tool for verifying some of the basic components of Sonar itself, files paths and reg keys, users will be able to give better details to the TS or even fix the problem based on their findings which would be much more clear than shooting int he dark (or- a detailed and maintained list from CW..where the users should go and check a-z the "environment" of what Sonar needs to run fine..not the regular "1000 windows tweaks" and so called optimizations..and not the regular "delete all CW registry keys" which everyone I guess know about already)

if they aren't written "correctly", what do you do if version x breaks these 4 plug-ins and version x+1 breaks these other 3? Whose "fault" is it? Which version is the "right" one to use?

Hey KP..you are right as always, good point. Yeah, that's a problem right there:) Now, the WinSxS situation..have you read all those threads from about 3 months ago? I wonder how good Sonar 6 and Sonar 7 are "written to cope with this" as you just said. There were many with unexplained MSVCR80.DLL errors.. I posted many links with info about the side-by-side assemblies..it helped some (also downloading and reinstalling VC libs)

I see some reports here about synths crashing Sonar with a C++ error (Sonar 7.01) ..saying 6 works fine. Something is broken- the patch (the way the setup.exe works) TO 7 / 7.01 or 7 itself changed something to be less compatible with many plugins.

ORIGINAL: Honest_Al

if they aren't written "correctly", what do you do if version x breaks these 4 plug-ins and version x+1 breaks these other 3? Whose "fault" is it? Which version is the "right" one to use?

Hey KP..you are right as always, good point. Yeah, that's a problem right there:) Now, the WinSxS situation..have you read all those threads from about 3 months ago? I wonder how good Sonar 6 and Sonar 7 are "written to cope with this" as you just said. There were many with unexplained MSVCR80.DLL errors.. I posted many links with info about the side-by-side assemblies..it helped some (also downloading and reinstalling VC libs)

I see some reports here about synths crashing Sonar with a C++ error (Sonar 7.01) ..saying 6 works fine. Something is broken- the patch (the way the setup.exe works) TO 7 / 7.01 or 7 itself changed something to be less compatible with many plugins.

Or it's a plug-in that now can't work with a new (different) version. It's tricky where to look.

ORIGINAL: BuleriaChk

Where can you get Darbuka? It isn't listed on any of the major vendors' sites (most say the product has been discontinued), and I can't find it on M-Audio's site?

Is it history now?

It does appear that they discontinued both Darbuka and Latigo. It actually appears that all the Wizoo products have been discontinued.

ORIGINAL: 7XL

It does appear that they discontinued both Darbuka and Latigo. It actually appears that all the Wizoo products have been discontinued.

That really stinks , kinda explains why the Cakewalk QA team might have bypassed these in testing.

ORIGINAL: Bajan Blue

Hi
I'm not sure if this is of any help, but I have both Latigo and Darbuka - I have a small network (two oldish machines) linked to my main machine. I use FX Teleport, which is very good.
I have Darbuka and Latigo installed on one of the slave machines.
I have just tried both and they work fine with Sonar 7.01 (upgraded last week).
All machines are using XP service pack 2

I'm not real familiar with Fx Teleport but, as I understand it you run their server app on your slave machines and their wrapper as the plugin in your DAW. Meaning you aren't actually running Darbuka/Latigo in Sonar.

Like I said earlier, there are workarounds if you have the necessary assets. (i.e. this solution or rewiring in Project 5, etc.)

Thanks for the suggestion, though.

Dinopop
The FX teleport system works like so :-
You set up one machine (the one you work on and which has your main DAW on) as the master
You can have any number of slave machines I think - I have 2
As long as the application is VST FX wraps it as you say
These "wrapped" applications then appear in your DAW as plug ins, just with the suffix LAN attached
You use these plug ins exactly as you would any other plug ins - actually within your DAW
The only difference being that the GUI of the plug in appears on the slave machine, so you do your set up on the slave machine, but all processing / recording etc is done within your DAW - it is all "real time"

The only thing I would say is that you need the fastest network you can get - this should not really be a problem as most machines come with pretty good network cards as standard in my experience these days. The only real cost is a good hub. FX is very reasonably priced.

The other advantage of course is that all the processing is being done on the slave machine
The slave machine does not have to be top specification either - one of the machines I am using with no problems whatsoever is my Old MusicXPC little square box, about 3/4 years old - while a great machine, just simply was too low specification for the latest software.
I was working on something the other day and just one of the plug-ins I was using on one track was registering 34% CPU usage on the slave machine - however my main machine and DAW where working fine obviously as all this processing was being carried out elsewhere.
I took this FX route some little while ago - when I upgraded my main machine (as we all do) I kept the old one and just hooked it up on the network - it has been such a success I can see me not having to upgrade my main machine ( a 2 year old Carillon Xeon Dual Core) for some time.
Hope this was helpful.
Nigel

dinopop

the basic laws of thermo dynamics and software development state that SONAR 7 BROKE SOMETHING!

Now We Are Talking.... at last... FAITH...

Bless you dinopop....

It's tricky where to look.

..but I'm sure that the bakers work day and night finding and solving these issues The 7.02 patch will arrive at some point so there's hope (that would happen AFTER finding more about all the reports we see here..maybe a quick fix? maybe 7.01 introduced something really bad compatibility wise for working with some popular VSTi's)

It Worked for me

yes i am angry and not happy.... it should work normally since it works as an insert... it MUST work...

a very big BUMP..... (although i really don't know what it means)

ORIGINAL: Honest_Al

Ok, it's been a week and not a peep out of Cakewalk on this issue, either here or in response to my Customer Support email.

Good luck with the email.

CW stopped responding here lately (as always..a week or two after a new version is out) and also don't forget - they never reply in threads where they see the puppy

It's all the puppy's fault! Bad dog ..bad dog..come here, Darbuka...what a cool name that would be (maybe not)

STFU.