OK, so after I thought everything was OK, I recorded two tracks at the same time and "BAM", the problem has returned.

At this point I am giving up on trying to fix it. I have a couple work around's that I can employ:
1 ) go back to the A|WDM (MME32) driver.
2 ) Go back to 7.0.1

Since I use a mixer for input monitoring, I can live with long latencies. And since 7.0.2 has step sequencer enhancements, I will opt for using the A|WDM drivers that run under MME32 and keep using 7.0.2.

I remember when my Tascam-244 had track 3 died on me back in 1984. I still used it for 10 months like that. So I guess it's all relative. I apologies to the bakers for ****ing up a storm over this driver issue. It's time I got back to making music and time I stopped whining.

Thanks for everyones help anyway. It's a great forum.

I think you may be right about that Bill.

ORIGINAL: Bassmanx

Time for a new computer

Johnson J-Station

Ah, just go for it, you'll find nirvana ;)

I'm scared. I finally got 6.02 working fine and started thinking about upgrading to 7. I'm really sick of having to pay good money for an update every few years only to have to spend months getting everything to become stable. Why the heck do we keep paying for it?? (rhetorical question...I keep paying for it too)

I had the exact thing happen to me as Jose posted while using v6 and a MOTU card. It never happened before. At the time, I had the playback loop enabled. Once I shut that off the problem went away and never happened again. Not looking forward to hearing that sound again.

So, after reading this thread again, does this problem only happen on systems with Aardvark cards?

ORIGINAL: synthjunkie

I'm scared. I finally got 6.02 working fine and started thinking about upgrading to 7. I'm really sick of having to pay good money for an update every few years only to have to spend months getting everything to become stable. Why the heck do we keep paying for it?? (rhetorical question...I keep paying for it too)

I had the exact thing happen to me as Jose posted while using v6 and a MOTU card. It never happened before. At the time, I had the playback loop enabled. Once I shut that off the problem went away and never happened again. Not looking forward to hearing that sound again.

So, after reading this thread again, does this problem only happen on systems with Aardvark cards?

Well it shouldn't but the fact is, it's an out dated card. (I think it's a great card). However, it is no longer supported and therefore they probably don't do any tests using Aardvarks.

I'm a bit calmer than I was when the problem first happened and I was able to find a work around. BUT yes I wish Sonar's Audio engine was the most "solid" in the business. Maybe it is. It's hard for me to say when I have a dinosaur for a sound card. It may even be my machine, though it is pretty a standard P4 with an Intel 845PE chip set.

I don't regret getting Sonar 7. It's work flow is the best, period at any price!!! The problem I have with 7.0.2 is the first "real" problem I've ever had with the product. What had me p*ssed was the fact that it happened on the 2nd maintenance release.

If you have up to date gear, you should be fine. I think the other people that were having trouble with motorboating will tell you it's been fixed. I'm pretty sure mine is more of an isolated case.

Also, there were a few GUI bugs that I reported in 7.0.1 and they fixed ALL of them. That's a responsive team.

Bottom line:

7.0.2 is worth it. I still plan on getting Sonar 8. It's still the best value out there.

If you think the Step Sequencer, the Publisher, the CD burner, Pitch to MIDI, Side Chaining and the Mastering Plugs will benefit you, then you should consider the upgrade. They are all great. For me the the z3at+ was the best part.

I can't stress enough that I don't want my ranting in this thread to keep anyone from upgrading. Like I said, I've calmed down and I feel bad that I got so irate in the first place.

Very true Bill. Before I make any final judgements, I'm going to completely wipe the hard drive clean and start over. I will install nothing but Sonar and see how it goes from there. It could be anything causing this so, in my frustration, I'm just going to start over.......don't talk me out of it It's time for my PC to "molt".

Can I recommend one thing BEFORE you do a full wipe/clean/install?
Try using the Windows XP "repair" option.

Backup first, of course. Then boot off the XP CD. Use the repair option. You'll have to reinstall any OS updates of course, but sure is a lot less consuming of time than a full wipe.

It may not work, but it just may. Others have done so successfully.

If that fails, then I promise not to talk you out of a full wipe/install

ORIGINAL: Bassmanx

Very true Bill. Before I make any final judgements, I'm going to completely wipe the hard drive clean and start over. I will install nothing but Sonar and see how it goes from there. It could be anything causing this so, in my frustration, I'm just going to start over.......don't talk me out of it It's time for my PC to "molt".

robby, are you using an aardvark soundcard or something else?

Hi Chris-

ORIGINAL: exectrader2001

me too. got some nice pops n clicks now i got motorboating. using the asio drivers too also with wmd. this sux, now i have reinstall!!

Have you tried the suggestions in this thread? I wouldn't just assume a reinstall would solve the problem. I'd try tweaking some settings first, if you haven't already.

-Susan

FWIW the Aardvark guys met with me at NAMM. We're sending them the latest version of SONAR and they will be sending us some of their hardware so we have reference points. The issue they know about and wish to investigate is a crash when launching SONAR with their ASIO driver. Not sure if they have heard of this other issue.

ORIGINAL: Noel Borthwick [Cakewalk]

FWIW the Aardvark guys met with me at NAMM. We're sending them the latest version of SONAR and they will be sending us some of their hardware so we have reference points. The issue they know about and wish to investigate is a crash when launching SONAR with their ASIO driver. Not sure if they have heard of this other issue.

Aardvark?????? Seems too good to be true. I thought they were long gone Noel?

The Status of my Aardvark situation is currently this:

It appears that my “Aark24” has some sort of problem. I don't know what it is yet but when I switched everything over to the "Aark20/20", the problem went away.

The fact that all my troubles started with the 7.0.2 were probably coincidental, though it all happened exactly at the time of the upgrade. Once again I find myself apologizing to Cakewalk for slamming 7.0.2. It's just that the timing of the problem with the introduction of 7.0.2 lead me down the wrong path. Sorry Noel.

P.S. What can you tell us about the Aardvark guys? Is there any kind of contact possible?

Not a 4 year old post. I too am STUNNED about Aardvark!

ORIGINAL: LionSound

Must be a typo. I'll bet he meant Edirol or Echo or someone. But not our armored little friend, the Aardvark! Last I heard he was roadkill on the information superhighway.

I fear that you are correct

ORIGINAL: hugojacquet

Hello,

Well I do have the "motorboating" problem too now with 7.02!

Some other problems where solved like the play button "lag" with the UX2 with the asio driver, but I get random occuring "motorboating". The ASIO driver gets "stuck" with a "brbrbrbrbrbrbrbbrbr" sound....

Not nice! Hope this gets solved in a next update!

Hugo

I am gonna bump this thread regularly. Besides that, it got so off- topic! This is still about the MOTOR- BOATING problem!