Reloading Default settings for Aud.ini: BitsPerSample=32 FileBitDepth=16 RenderBitDepth=32 I manually change it to: BitsPerSample=24 FileBitDepth=24 RenderBitDepth=32 Opening and closing X2 Trial leaves me with BitsPerSample=32 FileBitDepth=24 RenderBitDepth=32 Clicking on the 'Asio Panel' button does nothing?!

On this forum clicking the 'Preview' button returns "undefined" in the preview window. I feel like I'm in the Twilight Zone.

I have a feeling one of your installs went wrong and, after that, without removing all of the Sonar remnants from old folders and the registry, the situation has just gotten worse.  (Bottom line, the standard Windows uninstall wasn't enough to fix your problem).
 
Before trying yet another reinstall, do a clean uninstall of Sonar - including all remaining CW folders and registry entries).  If you need help, there are a few old forum threads that explain in detail how to do this.
 
Also, as a precaution, you should temporarily disable the antivirus (and disconnect your internet connection before you do this).
 

FWIW, I have never been able to get Sonar to open the ASIO control panel for the 44VSL. I have to open it from the system tray. In fact, that may be why Sonar can't open it; because it's already open.

Regards

I too have had inconsistent results trying to open an ASIO control panel from inside SONAR and not just with Presonus; not a big deal.

Thanks jond,
I actually think I have a very clean Sonar install. I'm a long time Sonar user and I am pretty well organized. I have never re-installed Sonar or either of the couple VSTIs I have. (Never had a major problem). When I mentioned re-installing above I was referring to Presonus audiobox drivers only. As mentioned above every single time I use Revo Pro to search the registry for orphaned strings (many of these for Audiobox) and leftover files on the HD (amazingly many). I've decided I'm not willing to mess up my organization on the chance that will get this blankety blank box to work.
Thanks for the replies about the ASIO Panel button. I learned this weekend that you are right, it is no big deal. Some ASIO drivers provide a panel-some don't. Audiobox doesn't, but thanks again for taking the time to help.

joakes


Formatting ? Wow, thats really last resort !!!

You've probably done this, but, you'll need to disable the on-board sound in the BIOS as well as deleting all its drivers and associated software.

Also, uninstall the Presonus drivers, run Ccleaner (the Registry tab)  to get rid of any orphanned registry strings.

Re-boot and then fresh install your Presonus drivers.

Cheers and good luck,
Jerry

Most of that is not required. There would appear to be something wrong with either the driver install or version, and/or Sonar, because multiple people have posted that it works on their system.

Bob Bone
 


Bob Bone

I've had time this weekend to work on this some more. I installed Sonar and Audiobox on my wife's XP machine.
I should mention that I forgot above to include the fact that I made sure Windows Control Panel -> Sound -> Advanced is set for Audiobox 24 bit (Play and Record). EVERY other Audio interface I've used defaults to 24bits in Windows. Audiobox is an exception and Windows evidently reports this status to Sonar. I think that is a flaw of both Audiobox and Sonar.
Results:
Windows 7 machine
    1.0 drivers
        8.5 compatible but crackles
        X2 Trial compatible but crackles
    1.2 drivers
        8.5 records only 16bit but crackles (I couldn't even get an input signal on my last
             re-install, but I didn't waste too much time worrying about it.)
        X2 compatible Trial reads 32bit (records 24bit) but crackles
    1.21 beta drivers
        Same as 1.2
XP machine
    1.0 drivers
        8.5 is compatible but crackles
        X2 Trial is compatible but crackles
    1.2 drivers
        8.5 record 16bit only NO CRACKLES!
        X2 Trial is compatible NO CRACKLES!
    1.21 beta drivers
        Same as 1.2
My conclusion is that Presonus Audiobox drivers are unusable in some Windows 7, I7-Sandybridge) configurations like mine. (Keni, maybe you're lucky.) Also, Presonus Audiobox drivers are unusable in Sonar 8.5
If you disagree, maybe you haven't read my previous entries here and at http://forums.presonus.com/posts/list/33331.page
 

I'm bitter about this.
I bought the Presonus AudioboxVSL for use with Windows 7/64 and Sonar 8.5. I had and presently have no intentions of upgrading to X1 or X2. Cakewalk makes it harder and harder for me to work with MIDI (especially notation) with every newer version. An apparent upgrade would, in actuality for me, be a major downgrade. Is that why I'm bitter? Of coarse not. Cakewalk has provided a fully functional trial download of a product they are selling and I appreciate as well as respect the fact that they did so. They made their decisions, I made mine; end of story.
Presonus is a different matter. They marketed a new product that was, at the beginning, unusable for many people. (I know that fellow long time Sonar users are laughing as they read this) :) I bought it from Sweetwater even before it was released so I was disappointed but not shocked when I discovered the pops & crackles that it's drivers rendered. But it WAS compatible with my DAW (Sonar 8.5). If not I would have immediately returned it. Sweetwater and the Presonus forum both assured me that a new 'popless' driver was in the works. Hang in there, they said. I hung in there way past the 30 day return period. I should have returned it immediately instead of listening to "trust me" dialogue. My bad. Now I'm screwed.
Now I realize that my Presonus Audiobox 1818VSL will NEVER work with Sonar 8.5! Please try to follow me on this as I'm not sure how logically I can explain this to you.
Presonus CHANGED the minimum requirement specifications for their (defective) product MANY MONTHS AFTER they shipped it to customers.
Suppose you bought a new state-of-the-art game. The minimum requirements are posted on the box.  OS is not mentioned but it's a new game and you have W7. Also the 'professional' game reviewers all give it high marks without mention of OS. You install it, it doesn't work so you go to the games forum and find out that lots of other people are experiencing the same bugs. The company recognizes that fact and promises to come out with an update patch that will fix the problems. (So far, normal stuff!)  The rub is that it takes 6-9 months to provide this patch fix and when it finally comes out, many customers still can't play the game. After this additional grief, frustration, and wasted time you discover (not from the game publisher but from other customers!) that the new game 'fix' now requires W8!
BTW I'm not buying anything else from Sweetwater. I didn't ask for or even mention a possible return to them (after a whole year, lol). I did describe to them the Presonus business ethic that I am describing on this thread and their attitude was very defensive of Presonus. I was told "This kind of thing is not unusual". OK, goodbye.
Now...
Would anyone like to buy a used 1818VSL? It's a year old but like new. (it was only used to record 20-30 10 sec. test runs)!

Do you have the Presonus plugged into a USB 2.0 or a USB 3.0 port?

I had lots of early trouble when I had mine plugged into a USB 3.0 port.

I had the 1818VSL running flawlessly in Windows 7 Ultimate x64, with Sonar 8.5.3, X1a through X1d expanded, and am now running under Windows 8 Pro X64 with X2a (which also had X2 prior to that).

I am going to send you a PM with my cell phone number - I would be happy to review all of this with you over the phone and see if between us we can get your situation resolved.

Bob Bone