AudioBox 1818VSL, 44VSL and 22VSL
30 postsPage 2 of 2
1, 2
I'm not sure what you mean when you say "rolling back is not an option". If you mean using 1.3 instead of latest UC driver, 1.3 is not "rolling back" but is the last approved working version that included VSL console.It is working here for me on latest Win 10.

Did you do the full install first as recommended?

http://www.presonus.com/support
Windows 10 X 64 : AMD Phenom II X 4 945
ATI Radeon 5450 / 512 RAM
8GB RAM / 1T SATA

Mac Mini (Late 2014)

Faderport and Faderport 8
Yamaha S-08
Fishman TriplePlay
Logidy Controller

Assorted PreSonus Gear

To add your software and hardware specs to your signature to make it easier for us to help you, click HERE.
Answers at http://answers.presonus.com/
User avatar
by kondzio on Sat Jun 17, 2017 9:08 am
I meant about Windows rolling back to previous release not the driver.
The issue is that i can't install 1.3 driver. I've just installed a fresh copy of windows (ver. 1703 build 15063.413 - it's Creators update) (I needed format c anyway) and after plugging in my audiobox 22vsl it clicks and pops (like it couldn't initialise). Then when I tried to install 1.3 driver i got an error. Tried that multiple times but failed. The only thing that works is Universal Control (but still the device clicks and pops when trying to play sound etc.), but i need that VSL console :)
I've also tried uninstalling UC (completely) with 3rd party uninstaller, but it didn't help and still cannot install 1.3 version :/
Sooner or later Microsoft will force us to get this Windows update, that's why i don't want to roll back to previous release
Any ideas?

error code and screen:
Image

[EDIT]
After hours of struggle I managed somehow to install v 1.2.2 driver and it seems to be working fine for now.
User avatar
by mamuefa on Fri Jun 30, 2017 6:53 am
kondzio wroteAudioBox driver ver. 1.3 does not work on Windows 10 Creators Update


Second that!

1. Make sure you check your USB-Hubs in the Device-Manager (Win+X).
2. Uninstall all old drivers of your 22VSL.
3. Install the Universal Control Software.

That worked for me. BUT: There is no VSL Software anymore. In fact there is nothing anymore. The 22VSL has become just a normal USB-Audio Interface with no "good to have"- features unfortunately!
:evil:
User avatar
by Skip Jones on Fri Jun 30, 2017 7:59 am
robertstarbuck wrote
(2) If I find the Universal Control is unsatisfactory, de-install it, and then re-install the AudioBox 1818's VSL that Presonus offers, will it be the SAME as the successful VSL product I started with? Or will Presonus' replacement "legacy" VSL installation be something different?

Thanks (again), Bob


A.) 1.3 UC was not re-coded, it is the same version that includes the VSL console.

B.) Not one poster has replied that they opened a Support Ticket, as suggested. A Support Ticket is the BEST WAY to get any issue resolved. You may get suggestions here on the User Supported Forums but we are not PreSonus Support. Please, if you are experiencing issues, open a ticket.

C.) It would be helpful for the community if you would post your system specs in your signature. Click on the hyperlink in my signature to create your system specific signature.

D.) I am on Win 10 Creators update (latest build) and the 1.3 VSL does work.

E.) Thank You charlescohen for your post. I am happy you are up and running.

Regards,

Skip

http://www.presonus.com/support
Windows 10 X 64 : AMD Phenom II X 4 945
ATI Radeon 5450 / 512 RAM
8GB RAM / 1T SATA

Mac Mini (Late 2014)

Faderport and Faderport 8
Yamaha S-08
Fishman TriplePlay
Logidy Controller

Assorted PreSonus Gear

To add your software and hardware specs to your signature to make it easier for us to help you, click HERE.
Answers at http://answers.presonus.com/
User avatar
by cristofe on Fri Jun 30, 2017 1:59 pm
:+1 What he said! :mrgreen:

http://www.fandalism.com/cristofe

PC'S: HP XW6000 Dual 3.2GHz Intel Xeon, 8GB RAM WinXP SP2 HP 6005 Pro AMD Athalon X2 B24 3.0Ghz, 4GB RAM Win8 Pro Dell Latitude E6410 Laptop Intel i5 2.67Ghz 8GB RAM Win7 Pro x64 Audio Interfaces: Terratec EWS88MT PCI (2), Audiobox 1818VSL USB & Firestudio 26x26 Firewire, Line 6 PodXT, Roland GS-10, NI Rig Kontrol 3

Monitors: Yamaha HS50M's DAW: S1 3.2.1 Pro

To add your software and hardware specs to your signature to make it easier for us to help you, click HERE.
User avatar
by kondzio on Sun Jul 02, 2017 4:32 pm
Ok, i found one more way to install the 1.3 driver on Creators Update, which worked IN MY CASE.

I copied the extraction files that original installer makes to a different location (desktop). They are located in C:\Users\<username>\AppData\Local\Temp\is-I1P80.tmp (the last catalog may be different, so make a printscreen when the installer creates files it so you can find it easily)
Then I uninstalled any audiobox 22vsl devices in my device manager (left the one that had exclamation mark only)
I ran the installer from the desktop (setup.exe) and it was a different setup than the original one. The installation went smoothly.
Hope that helps someone :)
User avatar
by martin14 on Sun Dec 31, 2017 5:15 am
I know this is an old thread, but I think it's worth summarizing some basic things to hopefully nail the issues that people have experienced here:

(a) FOR Win7 & Win10 SYSTEMS only: The legacy VSL 1.3 driver/software with Zero Latency Monitoring still works fine for: Audiobox 22VSL, 44VSL and 1818VSL.

(b) You need to connect your AudioBox **directly** to the PCs main USB2 socket -- ie. NOT into a USB3 socket! [NB. USB3 produces the clicks and pops with Audiobox.)

(c) For a 'clean' driver installation you first need to make sure there are no remnants of old Audiobox software on your PC.

(d) I have found that the best way of cleaning old Audiobox software from PC is to install the latest Universal software onto your PC, and then uninstall it. This is because the Universal installer is very good at removing all previous fragments of older VSL drivers & settings, and it also removes any old remnants from the Windows Registry & Device Manager.

Procedure for PC/Windows:

1. Install the latest Presonus Universal driver (this will clean-out any existing Audiobox drivers and settings).

2. When the Universal driver is successfully installed (and recognises your AudioBox) then reboot Windows.

3. When Windows is running again, go to the Windows Programs Uninstaller in the Windows Control Panel, and immediately UNINSTALL the Presonus Universal control software.

4. When Universal is un-installed, reboot Windows again. [Following this step, you should now have a ‘clean slate’ onto which you can install legacy VSL 1.3 software.]

5. When you are back in Windows, run the Presonus VSL 1.3 driver setup and connect your Audiobox into a USB2 socket.

From here it should all work -- At least that’s what worked for me!

Ps. For Mac users, the above will only work if you are still running the older Apple operating system. When Apple introduced their latest OS update (macOS High Sierra 10.13), they blocked third party drivers from running at the low-level kernel !
User avatar
by Skip Jones on Sun Dec 31, 2017 9:59 am
Thanks. Well explained. I still use my ABVSL 1818 and love it. Thanks for posting.

Skip

http://www.presonus.com/support
Windows 10 X 64 : AMD Phenom II X 4 945
ATI Radeon 5450 / 512 RAM
8GB RAM / 1T SATA

Mac Mini (Late 2014)

Faderport and Faderport 8
Yamaha S-08
Fishman TriplePlay
Logidy Controller

Assorted PreSonus Gear

To add your software and hardware specs to your signature to make it easier for us to help you, click HERE.
Answers at http://answers.presonus.com/
User avatar
by Skip Jones on Sun Dec 31, 2017 5:39 pm
All of this info is available on the PreSonus Knowledge Base.
If you have questions open a ticket or read the KB.

THIS IS NOT NEW.

http://www.presonus.com/support
Windows 10 X 64 : AMD Phenom II X 4 945
ATI Radeon 5450 / 512 RAM
8GB RAM / 1T SATA

Mac Mini (Late 2014)

Faderport and Faderport 8
Yamaha S-08
Fishman TriplePlay
Logidy Controller

Assorted PreSonus Gear

To add your software and hardware specs to your signature to make it easier for us to help you, click HERE.
Answers at http://answers.presonus.com/
User avatar
by martin14 on Mon Jan 01, 2018 4:19 pm
Thanks for the feedback Skip!
You are right, it's not new. And there have been hundreds of posts on this subject, and I have read most of them. But in none of them has there been a clear explanation of the different factors and what to do. This is evidenced by the fact that there are still folks writing threads with titles like this one.

I guarantee that if Presonus had, several years ago, prominently written what I had written -- ie the simple points above -- then they would (a) have not had so many angry posts to read; and (b) they wouldn't have had all the unnecessary product returns from their PC-based customers and the defections to other brands.

By the way, I have now bought a brand new 44VSL -- to accompany my older 22VSL (which I bought when it first came out). VSL is so good for anything in real-time, and I really couldn't do without it. And it's a brilliant sound-card for games, Youtube, etc. as it allows me to route all the audio through the monitors + sub, with no latency, and apply EQ, compression & reverb in realtime, to make my games and my other audio needs -- such as live karaoke with my Shure SM58 mic -- sound absolutely great.

Happy New Year!

30 postsPage 2 of 2
1, 2

Who is online

Users browsing this forum: No registered users and 5 guests