I concur.  Registry and BIOS information can make your computer stop DEAD and sound the diagnostic BEEP codes that you just never want to hear.
Then you'll have to open up your computer and mess with the jumpers, assuming that you have a tower. Tread lightly.  

Sorry to intrude, but these are sensitive things to mess with.  I've been through it all before during my learnin' days.
Duke

+1 on registry manipulation cautions.

For Gio's situation, no registry entries were harmed during the process of solving his problems :)

It just doesn't like USB 3.0 ports in the driver's current form.  They are in the process of incorporating changes to their drivers and will hopefully fix that in the next Presonus driver release.

Bob Bone

We all tend to post constructive information and assume that everyone is a technical guru.  Being doing IT well before Bill Gates and the former Steve Jobs (Am I dating myself ).  Where has all the time gone?  Thanks for the update.

JonD

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?   

Bob is correct and confirmed by Presonus support.  There is an issue with their 1.2 AudioBox drivers and USB 3.0.  They have addressed this in their forthcoming 1.3 release.  This issue may apply to anyone's specific hardware/driver, so rule out USB 3.0 first. FYI, Using a 128 ASIO buffer size in X2 to match the AudioBox settings in Control Panel has produced a very favorable result of 7.8ms RT.  That I can live with .  


The Presonus AudioBox 1818VSL is a hot item right now. GC has a waiting list for them.  Luckily I got mine from one of the San Diego stores.  What I like about this unit is that it has it's own set of direct driver plugins (aka FatChannel) that has a Filter (phase), Noise Gate, Compressor and GEQ for mixing "Live" sound and I can record to the DAW (X2) without worrying about RT latency. This has been my "So called"..."Quest for the Holy Grail".  Now I can save my back and decrease my setup time by not having to lug around a 32-channel mixer and a 10U rack of EQ's, Compressors, FX, etc.  What I may elect to do is keep my FOH EQ (Behringer DEQ2496) and Crossover (Behringer DCQ2496) in my 6U rack with the AudioBox.  Always a work in progress, eh? 


Anyway, this forum is about X2 so I don't want to get off track too much.  So with this configuration, I can send a multi-mix down to X2 dry to record the live gig and add the effects, etc later for post production final mix.


Thanks to everyone who contributed to this thread.  All good stuff!!

robert_e_bone


+1 on registry manipulation cautions.

For Gio's situation, no registry entries were harmed during the process of solving his problems :)

It just doesn't like USB 3.0 ports in the driver's current form.  They are in the process of incorporating changes to their drivers and will hopefully fix that in the next Presonus driver release.

Bob Bone

I see you are online. I have had all the same problems and have other thread on this forum and others. Had the problems on a new DellXPS 702X with 8mb ram and never could get it below 23ms with any drivers--I`ve tried them all. So, had someone build me a new system that flies with 16mb ram (yes matching) and even worse problems but similar. I can`t go below 23ms 1024 samples without rice krispies. And this happened with a client in the studio and wasted 2 hours of his time and also Sonar suspending and crashing. I would happily phone from Japan to anyone who can fix this. I have tried every tweak the internet has to offer as far as I know. Presonus 1818vsl. I managed with the laptop to have a 3 days drum bass session using all inputs and not a hiccup at 23ms. I so feel for you man. Thank God my studio is padded as I have put my head to the wall and cried. Please someone put all of your major tweaks that aren`t common tweaks that you can find on google in a post/thread and save us all.

So, had someone build me a new system that flies with 16mb ram (yes matching) and even worse problems but similar. I can`t go below 23ms 1024 samples without rice krispies

You probably need more RAM...................

Karl,


Good to see you chime in here.  It was USB 3.0 that was the issue.  Have my ASIO buffer size set to 128 and having great results (7.8ms RT).

FastBikerBoy


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.

  sorry--16gb typo

Good to see you chime in here. It was USB 3.0 that was the issue. Have my ASIO buffer size set to 128 and having great results (7.8ms RT). USB 3.0 was your problem? I`m happy for you but I am using USB 2 and still the same issues.

In the ASIO driver settings the audio driver bit depth, thoguh greyed out, is 32bit. Does that mean anything. I feel bad now because I am straining at anything I can find. I am using the latest drivers and firmware for the Presonus. I would be very interested to see what the rest of your settings are.