Another Presonus interface issue

You need to post some system specs.
You say "On my 64 bit OS - the same DAW"
Is this a dual boot 32/64 system, or 64 bit OS running Sonar x86 (32 bit) and Sonar x64?
 
Tom

I have the PreSonus 22VSL, purchased because of the integrated fx (which I wanted for confidence reverb)
 
With the first driver set, it only worked in WDM mode.
With the driver update it then worked in ASIO mode but something else did not work anymore, I forget what.
There has never been another update, yet many people reported the same issues I had.
 
It is now back in the box in the cellar.

@clintmartin: That's the big brother of mine.
Do you use it in ASIO or WDM?

H'm. New 1.3 drivers, dated 21. July, 2014.
Maybe I should get it out of the cellar and try again.
Thanks!

This knowledge base link on Cakewalk was available, and I thought it would help - but refers to the Universal Control which I don't have - should not matter though since I got it to work on my 32 bit desktop/Sonar version:
 
http://www.cakewalk.com/Support/Knowledge-Base/2007013386/Focusrite-and-PreSonus-Interface-Routing-Setup
 
 

So this is a separate machine which only runs 64bit Win7. Make sure the device is attached to a USB2 port, I believe the 1818 is picky about that. Also IIRC when switching ports it may be necessary to reinstall the driver software. And although the latest driver should work, you might need to try other versions.

On the 32-bit system that's working, did you install the newer v1.3 drivers?  If not, then that might explain why that setup works and why the 64-bit setup won't (The newer drivers have dropped Vista support).

Try the Driver that was just prior to V 1.3.

Personus 828 hybrid....Also has issues in windows 10.
 
So far, it seems to be a conflict with onboard Realtec audio.
 
I removed the onboard realtec drivers..)Asio(?...seems to have a applet for the device....
 
Any hoot, it just would not play back anything No matter the version of the Personus driver used...or set set as default audio device...
 
So I thought about it not being a Presonus issue totally...But more a onboard audio issue....or conflict with the Presonus driver.
 
Once I removed the on board audio driver...and rebooted...my Audio came back....through the presonus audio...In my Daw of choice, and working ok....
 
Not sure where I saw someone saying to try doing this...But...other people are having issues also with multiple audio devices and win 10...or..input outputs being screwed up...or loud noise (squeeling and such)(stuttering and the sort)...when there should be none...if on board audio is set to win default...and the ASIO main DAW Device is not used by Windows....it should not be effected by OS..or any applet that may use default device of the OS.
 
Hence...a driver conflict is occuring....somewhere...if removal of on board audio driver clears it up for some...
 
Just more fun to make us get pissed off..and not get any work done, while trying to solve for the next batch of bugs....
 
But...at least some people try to solve things...For people to get things done, on the other side of zero.....wink.
 
Hope this helps some?
 
 
Best wishes.
 
Cheers!
 
 
 
 

FWIW I have an 1818vsl that I use in Windows 10 with SONAR Platinum (Lexington). I upgraded initially from Windows 7 to 8.1 to 10. I have had no problems with it. I know there are other SPlat users with this interface although not sure how many (if any) others are also on Windows 10.

Oh..here is something else about this problem with ""some folk"' not hearing sound...or having issues with Audio devices ..(I am using , or trying to use in Sonar)(presonus 828x)(motu midi Express) with system spec'd below...(I put a samsung ssd 500gb drive for OS and apps recently via cloning with Arconis 201x, instead of the Adata 250gb listed in my profile)((I will update as things settle in, if so)
 
After I did this today: Bios attempt to get my audio working again, By checking all settings before windows boots, and there after....((removing the Realtech Audio device Drivers, in device Manager).......I was able to open a older Sonar project...(made with Allen and Heath r16 x2)(yet could not get Sonar to open old projects with New audio device = thought to have been working since removal of Realtech audio device)(Now using Sonar for a test run)...PS ...((Studio one 3 latest build is working with Presonus...very good since the removal of..))
 
Not sure why removing the on Realtec board audio drivers, from device manager...helped get my TB Presonus 828x to start working...Did do some of...but....
 
Sonar (not latest version code name Kingston, seems to have locked onto something...weird ..
Opening a old project, not finding the Allen and Heath r16, shows messages about silent devices , or not finding...ect...So Motu is showing in availble...Right pain, and Allen and heath on the left...click ok....Adat silent device found...will remain silent until setup in properties of sonar...ect...ok....?....no, it loops back forever not setting up the audio....always opening these windows about adata outputs being silent...nothing to do in that window but select the out or in of itself..or none....tried both....still looping around....blah blah.
 
So ...should I turn off the on board in bios....Ok...shut down sonar by click on the taskbar icon and selecting "close window" several times...got it to close sonar...and a reboot...to get into the bios.
Turned off the on board audio real tech....and rebooted.
 
Opened the same project...window opens to reselect or assign audio to motu...etc...all worked out ,and only had to click ok once each window....((Normal?)...and then....weiredness....Project opens, and sound is coming out of the motu 828x...but...the sliders and such in Sonar do nothing...nor muting all tracks even the master out does not work...as audio continues to play through something?...yet no control in sonar until stop is selected on the controls of sonar....((Using audio path of unknown nature through...Presonus828x still is tied to something odd ?)
 
 
So...
 
I deselect ASIO Motu Driver in Sonar's Preferences...select WMD driver, hit apply...And it asks about adat in/outs and  I believe again....""OK""..close out and start and reselect Motu ASIO. is selected again...Project opens now...with control on the Sonar sliders for the Motu 828x audio device/volume mute and solo also working as should be.....
 
 
See who/how this could cause freaking issues...removing drivers...does not always solve for...until you flush the program also....and just refresh by preference of asio..to something else, then reselecting it after apply is done...
 
Is this a refresh issue with Drivers held? even though removed/Uninstalled............?..MS?...MB?...Sonar?...USER?.
 
 
And going a extra mile...to solve still by reselecting and setup of...software and audio asio..once doing any updates or uninstalls of audio drivers.
 
or does one have to delete the sonar inf file to make a new one, to address new setups or changes made here?
Or has Realtech done some corruption on Directing to ASIO?....and then all apps using, hold the error, until reset?.
 
So perhaps a reset of sonar's Audio preferences and such..once removal or adding new drivers..Might be necessary?...or removal of a setup inf file/ini file?...(I seen some say to do, and Sonar remakes this file when removed or deleted)....Not sure if that might help get new drivers working ...as I have not played with ini or inf files yet....((could be a bad reg listing held ?))
 
Other than that....I think I solved my problem with Sonar and Presonus 828x...for now.
 
Hope this helps many?
 
 
Cheers.