Look in the “knowledge base” under your device or in this thread: I just had my friend to have a mess around with it, and it seems that when Pro Tools gives you the error message “ASIO device properties have been changed by the device control panel. This setups just works on all firewire devices. I never had a need to. However, just this evening, I was unable to get any sound from my presonus at all.

Uploader: Tygohn
Date Added: 16 February 2013
File Size: 67.30 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 29855
Price: Free* [*Free Regsitration Required]

It comes with UC 1. I DO have computer sounds through my speakers Cubase that perform automatic ASIO latency compensation. Since this guess-o-matic does not always yield correct results, you can measure the actual round trip latency for audio using a loopback cable and adjust the wsio in the “Latency compensation” section of the ASIO4ALL v2 control panel accordingly.

I have had the same problems.

I never had a need to. Look in the “knowledge base” under your device or in this thread: I usually use port 3 on the back, as for some reason, this gives me better audio This message was edited 1 time. I’m pretty sure I have the most updated software, as it was running before. I live in Kenosha. They have the old driver up there too.


First time poster here. Never had a problem. I’ve tried downgrading to Pro Tools 9, but this is still happening. So I gave up after 10 years with Presonus and bought a Focusrite 2i2.

I never had any issues like this with Cubase, but unfortunately for Cubase, Pro Tools has a lot more features beneficial to me. But from what I have experienced and read, P has issues with alot of interfaces right now. There was a great cheese store accross the street from our hotel big surprise. Thanks again, -Chris p. Presobus XW Dual 3.

Getting ASIO drivers to install on Windows 8 for Firestudio Mobile

I thought about losing money and re-selling it on eBay. Nothing insulting intended, just curious. Universal Control seems not to have installed fully. I have no problem using pro tools 9 at this time if that works best. I have a horrible clicking almost like a metronome and my first set of LEDS are lighting up like im getting a fieestudio signal with nothing plugged in. Yes, my did not work properly with the computer I originally intended to use it with.


Studio Firestudko Pro 2 2. Ok, yes I whined about it a bit.

I’m using the right kind of firewire card OHCI compliant We were on tour playing Chicago, Millwaukee, University of Wisconsin, etc. Thanks in advance, Chris I have 2 clients using it with Pro Tools 9.

Also if you run that and it gets you nowhere meaning the OHCI tool recognizes the firewire connection and has not problems with it Check the IRQ’s and see if there is something else on the buss I think the reason I can’t hear audio when plugging into the headphone jack on the presonus has something to do with the driver issue was well.

Universal Control, in my experiences, has more issues with the DAW open. I’m looking into purchase the firestudio if i can find out if its working good with pro tools. Btw i see u live in Illinois