Darbuka crashes Sonar 7

Just insert the plugin and BOOM!

Works fine in Sonar 6.

tried it, it gave me this




, then a SEND/DONT SEND then a blue screen/restart....


Cakewalk, Can this be of any help ???????? and Quick.... i need Darbuka on like every project i do...

oh God oh God, that is not a good day.... definitly not a good day

Strange. I don't have Darbuka but Latigo is working fine.

Doesn't work for me either.

ORIGINAL: 7XL

Doesn't work for me either.

Very strange. I was under the impression that Darbuka and Latigo were the same player with different samples? Very strange indeed.

ORIGINAL: crash_3210


, then a SEND/DONT SEND then a blue screen/restart....


Cakewalk, Can this be of any help ???????? and Quick.... i need Darbuka on like every project i do...

oh God oh God, that is not a good day.... definitly not a good day

Mine doesn't BSOD but it might as well.

I'm in the same boat as you crash. I write a lot of Middle Eastern influenced stuff for dancers (yes, belly dancers) and until I can run Darbuka, Sonar 7 is on the shelf!

Strange. I don't have Darbuka but Latigo is working fine.

They are different .dll's. I'm going to install the Latigo demo and give it a shot.

Latigo gives me the same error.

Obviously there is something amiss. There is another thread about Karma FX synth not making any sound. Somehow the handling of certain VSTi's that work fine in 6.xx no longer function properly or at all.

Yep,

Latigo crashes on mine also. The app would come up before I got it certified (so it could load the samples).

Once I did that, the results were the same as Darbuka.

This is a show stopper!

ORIGINAL: dinopop

Yep,

Latigo crashes on mine also.

Time for specs, then.

On my DAW:

AMD Athlon(tm) 64 Processor
3500+
2.21 GHZ
2.00 GB RAM
Windows XP Home Version 2002
Service Pack 2
MOTU 2408 mkIII
Sonar Producer Edition 7.0.1

I'm having no problems running Latigo.

Windows XP Pro, Service Pack 2
Frontier Wave Center PCI card
2 GB ram
AMD Athlon 64 XP processor 2800
Sonar Producer Addition 7.01

Which drivers are you using with your Frontier Wave Center PCI? ASIO, WDM? Newest?

it can't be a driver problem, it has been working for me since SONAR 4 !!!! same Audio Drivers (ASIO4ALL)
Hey Cakewalk , You Changed something , bring it back or make it work ... Pleeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeease




you can NEVER imagine how Essential is Darbuka to some users Including myself

ORIGINAL: crash_3210

tried it, it gave me this




, then a SEND/DONT SEND then a blue screen/restart....


Cakewalk, Can this be of any help ???????? and Quick.... i need Darbuka on like every project i do...

oh God oh God, that is not a good day.... definitly not a good day

Zeta+, SFX, Dropsone, RXP and Raputure all behave similarly. Really anoying. but seems to me like the problem is with OS. I am interested in a solution please if anyone has.

ORIGINAL: Dele Abegunde
Z3ta+, SFX, Dropzone, RXP and Rapture all behave similarly. Really annoying. but seems to me like the problem is with OS. I am interested in a solution please if anyone has.

No problem with any of the synths that you mentioned.

7XL

No problem with any of the synths that you mentioned.

me neither, just DARBUKA... & LATIGO...

just a thought...

i inserted Darbuka > un-check ALL boxes (no MIDI tracks/ no audio outputs... no plugin interface...)

nothing happened...

so i inserted an audio track, assigned its Input to Darbuka stereo output and BOOM.... same crash instantly... is this of any significance ?

I just went from 7.0 to 7.0.1. Everything seemed fine. All of a sudden Firebird and Novataion Bass Station started to crash Sonar. Just like what you were showing. I tried to get help from Tone2 and ........ well, we won't go into that here. Anyway, I also sent an e-mail to Cake and havn't heard back yet. In the meantime, I discovered I had to uninstall and reinstall the synths. Now, both work fine.

I have lots of softsynths and, to date, these are the only two that have created the problem. I know it is a pain, but that worked for me.

Good luck.

this doesn't apply here to Darbuka or Latigo... re-install doesn't do anything....

being here on the forum lately a lot, i found out that MANY MANY VSTi's are crashing SONAR 7.0.1 instantly after inserting...


http://forum.cakewalk.com/tm.asp?m=1192800

http://forum.cakewalk.com/tm.asp?m=1191964


Hello Cakewalk... Anybody there ..... knock knock... at least tell us we aren't insane and there IS a problem....

Oh, And BTW, while you are doing this one, please please check that lost feature of NOT being able to scroll tracks while selecting the Key+ or the Time+ areas...

my original post (about S6):

http://forum.cakewalk.com/tm.asp?m=996518&mpage=1&key=noel??

6 months later (after S7 was released):

http://forum.cakewalk.com/tm.asp?m=1162429&mpage=1&key=noel%2Cback�

ORIGINAL: crash_3210

this doesn't apply here to Darbuka or Latigo... re-install doesn't do anything....

Sorry it didn't help. Uninstalling and reinstalling is not a favorite way for me to spend time. I (originally) though 7.0.1 had more bugs than 7.0, it acted so strange after I installed it (it would switch off my metronome track etc.) However, reinstalling those two synths made everything work fine..... go figure.

Good luck.

Unfortunately, Crash, this doesn't help you, but Predator just followed the same behavior as Bass Station and Firebird. I had to do a reinstall and reboot and now it appears to work fine. Hopefully this may help some others who have installed the 7.0.1 patch though.

Good luck with Darbuka
Take care

Latigo crashes my SONAR 7.01 immediately upon inserting it.

I had to do a reinstall and reboot and now it appears to work fine

Reinstalled what? ...the softsynths or Sonar 7.0+7.01 or just the 7.01 patch?

(I can't see how reinstalling synths can change anything for Sonar)

Reinstalling the soft synths. Don't ask me why (or ask if you want to, but I won't have an answer) but the 3 I mentioned all work fine now and crashed before I reinstalled them.

Ok guys, I've submitted bug reports to both Cakewalk and M-Audio (who now own Darbuka and Latigo). We'll see what happens.

BTW, I have found a work around for any of you that own Project 5 or other Rewire-compatible VST hosts. I can load Darbuka in P5 and then rewire it into Sonar 7 and it works fine.

Pretty ugly, I know. But it's an option.

update

plugins crashing SONAR 7.0.1


http://forum.cakewalk.com/tm.asp?m=1192800 Kontakt 3

http://forum.cakewalk.com/tm.asp?m=1191964 Zeta+, RXP, DropZone soft, Rapture, SFX synths

http://forum.cakewalk.com/tm.asp?m=1193236 Virtual Bassist

http://forum.cakewalk.com/tm.asp?m=1193157 RA (not actually crashing!!!)

& Of COurse This Thread... Darbuka & Latigo

For mw, AT2 when I begin looping..... (but I think it is an AT2 VST issue).

ORIGINAL: crash_3210

update

plugins crashing SONAR 7.0.1


http://forum.cakewalk.com/tm.asp?m=1192800 Kontakt 3

http://forum.cakewalk.com/tm.asp?m=1191964 Zeta+, RXP, DropZone soft, Rapture, SFX synths

http://forum.cakewalk.com/tm.asp?m=1193236 Virtual Bassist

http://forum.cakewalk.com/tm.asp?m=1193157 RA (not actually crashing!!!)

& Of COurse This Thread... Darbuka & Latigo

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

Ok, Here's A Thought...
Can the creator of this thread (dinopop)please RENAME it to something like "Worked on 6 , not any more on 7" to put a list of VSTi/VST plugins that NO LONGER work and Used to work all the time on 6 and stopped on 7.0/7.0.1

oh no, i'm not letting this post fade away... even if i keep replying to myself forever or until i get kicked out of the forum

are we only talking xp64 here?

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!!!

Nope, I had (and occasionally find a synth that needs reinstalling) in XP 32 bit. Personally, I think it had something to do with the 7.0.1 update.

Amplitube 2; sorry....

Chuck

ORIGINAL: crash_3210

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

ORIGINAL: Honest_Al

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!!!

a few posts mentioned x64 that's all.

anyway bummer problem! I am pretty much dead set on Sonar following steinbergs horrible CS so i hope this gets sorted.

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....

I was the first one report sonar7 crash.. Just after install

I was worry when i see that Microsoft visual ++ library thing during installation.. Tons of people complained when Sonar6 crashes all the time, that was the answer: they use latest code (visual .... etc), don't know much about it... Any other software including Sonar5 works fine with plug ins...

I've just close my Sonar, 2 minute ago because it's gone again..! come here to take break..!

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.

The issue that we're discussing here is a few third party plugins that don't work. Not trouble shoting your system problems.

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)

With regards to dll versions (which shouldn't be a problem nowadays with side-by-side assemblies if an application is written to cope with this), 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?

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.

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.

This (the Wizoo plugins crash) problem has nothing to do with the patch. It appeared in 7.0. I applied the patch in the vain hope that it would fix the problem.

The original post for this thread was for a very specific situation that occurs 100% of the time with these specific plugins in version 7.0 and greater and works 100% of the time in version 6.

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

BTW, I did get an email from M-Audio saying that they are looking into this. No word from Cakewalk yet.

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.

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?

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.

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

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.

ORIGINAL: Honest_Al

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.

I agree with you there Al. I bought a brand new machine--dual core processor etc. Checked out the specs here on these forums and a Cake website. Nothing on it except internet access (and oh yeah, my photo editing program....no games etc. etc.) Most of my plug-ins worked back in my old machine...unfortunately, most of them worked fine in 7.0. However, after the "update" to 7.0.1 they have a lot more problems. Sonar, in general, crashes more and so far, 3-4 plug ins have not worked properly. I do see it as a fault in 7.0.1.

I sent Cake an e-mail and was told to reinstall. Not sure that is the answer. Unfortunately, I have customized the heck out of Sonar 7 and am not sure how much of it would "stick" (key bindings, folder location etc. etc.) after a reinstall. Also, on my machine, the original install was a real pain. Crashed the machine several times. I finally got it to work and (as stated) 7 worked just fine. The patch went on smoothly, no crashes or problems... well, until I started to use the program.

Anyway, been with Cake since it WAS Cakewalk 3.0 (maybe 2.0) and nobody knew (except Al Gore) what the internet was. Doubt if I'll change now. But I sure hope they look at stability issues.

BTW, even though I am pretty careful about where I go and what I download on the internet (very few free/shareware plug ins etc.), I do lots of virus and spyware scans. I kind of doubt that's the problem.

Take care

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

I agree with you there Al.

Great! So there's one person here who agrees with me..thanks rjt.

Anyone from Cakewalk? No more 7 or 7.01 comments from you guys? ..or why those awful c++ errors creeped in?

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....

I just tried this and it works.
Instead of inserting Latigo or Darbuka into the Synth rack you can pull up an empty Audio Track and insert it into the effects Bin.
This does limit you using the multi-audio out but at least it can be loaded in a project.
It also possibly will bring us closer in finding out what happened.

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)

ORIGINAL: simeon

I just tried this and it works.
Instead of inserting Latigo or Darbuka into the Synth rack you can pull up an empty Audio Track and insert it into the effects Bin.
This does limit you using the multi-audio out but at least it can be loaded in a project.
It also possibly will bring us closer in finding out what happened.

Yeah, this does work. At first I wasn't able to get any sound but after a little fiddling and forcing a playback it started working.

I'm thinking there is something whacked in the VST wrapper. One interesting thing I just noticed as I was poking around is, if you look in the plugin manager there is a set of Plug-in Categories called Legacy Wrapped VST Audio Effects and Legacy Wrapped VST Instruments. Darbuka is in the Instruments list, however you can't really do anything with these. If you select one, the Add button doesn't activate.

Does anyone know what these are? Is this a possible clue to our little mystery?

It Worked for me

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

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.

Hellooooo! Anybody home?

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

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)

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.

STFU.

Another forum cop?