ASIO PRESONUS FIRESTUDIO DRIVER

From ignoring this error message and closing it, you can set the buffer size to what is set in Pro Tools and then restart Pro Tools again. And what is the name of the huge music store right near Kenosha? However, just this evening, I was unable to get any sound from my presonus at all. Maybe I can reinstall. I'm using the right kind of firewire card OHCI compliant

Uploader:	Meztibar
Date Added:	10 February 2009
File Size:	68.14 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	35841
Price:	Free* [*Free Regsitration Required]

This message was edited 1 time. I'm using the right kind of firewire card OHCI compliant Asio4all should see the Firestudio now with no issues BUT if you want to adjust the settings, close the DAW and then launch Asio4all and make your changes.

Or what I can do about it? I've done this with dozens of folks here on the forum. The buffer size in the Presonus Universal Control won't change at all either. Make sure the computer and OS are up to date 2. Thanks for the reply.

I cant even get imported audio to play with out being totally crackly. Pro Tools must be restarted for these changes to take effect. After getting to the "restart your computer now" instruction, and upon rebooting, nothing else happens. I can't seem to get it to work with any settings. HP XW Dual 3. I never had any presomus like this with Cubase, but unfortunately for Cubase, Pro Tools has a lot oresonus features beneficial to me.

Never had a problem.

Firestudio Project Universal Control and ASIO4ALL Buffer Sizes With Pro Tools 10

First time poster here. It comes with UC 1. Things were fine in Pro Tools 9, and this has only occured since upgrading to Pro Tools So even closer to Adio.

I've tried downgrading to Pro Tools 9, but this is still happening. Studio One Pro 2 2.

House of Worship Where y'at? I have a 64 bit system with fully updated windows 8 pro. I've had a generally really easy experience setting up the firestudio and making many, many recordings with little to no issue. firestkdio

www.steinberg.net

Bottom line question is: Has anyone else had this issue? I think the reason I can't hear audio virestudio plugging into the headphone jack on the presonus has something to do with the driver issue was well. Nothing insulting intended, just curious.

The old driver is 1. However, just this evening, I was unable to get any sound from my presonus at all. You should be able to use the presonus drivers within Audition as well not even needing the fierstudio drivers. 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 sliders in the "Latency compensation" section of firestuido ASIO4ALL v2 control panel accordingly.

But from what I have experienced and read, P has issues with alot of interfaces right now. Usually, the firestudio is set for default device, and my speakers are set to default communications device, and it all works wonderfully. Btw i see u live in Illinois