Remove everything in registry startup that is not critical (Use regedit or a startup utility for this)

This is like giving a baby a grenade to play with!

Unless you are really comfortable about editing the Registry, the general advice is DON'T!

You could render your entire machine unbootable if you're not careful.

Giving out advice is fine. Giving out bad advice should be a stoning offence

Bristol_Jonesey

Remove everything in registry startup that is not critical (Use regedit or a startup utility for this)

This is like giving a baby a grenade to play with!

Unless you are really comfortable about editing the Registry, the general advice is DON'T!

You could render your entire machine unbootable if you're not careful.

Giving out advice is fine. Giving out bad advice should be a stoning offence

You're right.  I should have mentioned the standard warning when messing with the registry...  (So.  Read Jonesy's warning above!).  
 
*Edit: I just realized that this isn't like me -- to advise users to use regedit.  Then I saw my mistake:  I meant to say MSCONFIG, which is pretty safe, since in the startup tab, you are only disabling non-critical items.  
 
Still, I'm ready to accept my stoning, officer.  Can I get a reprieve, or do I bring my own post?   

"That piece of Halibut was good enough for Jehovah"

I also sent a private message to Gio with this update.

He had sent me a message late last night with updates from his end, on some things I had suggested to him in our phone call.  Something in what he said in that message made something click in my brain, so I wanted to post that out here, in case it helps someone else.

When I was first installing and configuring my Presonus AudioBox1818VSL, I also had crashes and driver issues, and no output in Sonar, but eventually got it to work properly on my machine, and have had ZERO problems since.

When after Gio and I matched up on every single possible parameter between Sonar and the Presonus ASIO driver settings, and he STILL dropped the audio engine, he was quite frustrated and I was quite at a loss to explain what was happening.

He went on to try this all out using a laptop that happened to have a clean X2 install on it, and everything worked.

As he explained this in the email, he threw in one of those 'by the way' comments about also having it initially plugged in to a USB 3.0 port on the failing desktop.

That INSTANLY reminded me that I had had that exact same problem.  The Presonus AudioBox1818VSL interface does NOT like to be plugged in to USB 3.0 ports.  The Presonus tech support folks helped me work that one out, and I had COMEPLTELY forgotten about it.

So, when Gio wakes up - he is on sprouts time (California), I will talk to him and make sure all is ok.  I am QUITE sure that this was the issue, and that he will be once again a happy camper.

To ALL, make sure for this interface that until they fix it otherwise, you only use USB 2.0 ports for it.  The other critical thing is to make sure your sample rates are set the same between Sonar and the interface.  No match, no sound.

Bob Bone

I just gotta say this forum is the shizzle.

I was born in the groovy era, so I don't have a clue about fizzle, or nozzle, or drizzle, or whatever all of that new-fangled terminology is.

If by shizzle you mean it's the cat's pajamas, then I am definitely with you.

Bob Bone

Dude!

The one in the middle SCARES me!  And, YOU scare me even more!  Yikes!

It's really wrong what humans do to pets sometimes - :)

Bob Bone

The USB 3 thing does not surprise me at all.  Many USB 3 drivers seem to have been in a state of flux for a long time.  Also, many USB 3 ports on motherboards use 3rd party chipsets while the USB 2 ports are straight into the southbridge bypassing other buses and 3rd party chips.

This problem will probably settle down as more motherboard chipsets have native USB 3 support and mature drivers.  But at the moment - yes, this could easily be a problem for harpman.

The I/O buffer sizes in Preferences-->Sync & caching will also have a bearing on dropouts. If the buffer is too small supply of data to the audio engine is to slow and it'll drop out. Too large and it can take to long to fill.

In my experience there is no right or wrong figure, just one that'll work better for any given system and even then it can depend on ASIO buffer size.

Good news is it only needs to be set up once.