Since I've upgraded to Pro Tools 10, I seem to be having a problem with the hardware buffer sizes in Pro Tools along with the ASIO4ALL driver. If I set a buffer size in Pro Tools to say, 1024 samples, ASIO4ALL won't match this buffer size and instead set itself to 512 samples. The buffer size in the Presonus Universal Control for my Firestudio Project won't change at all either. In other words, the buffer sizes across Pro Tools, ASIO4ALL and the Presonus Universal Control, are all different and not matching the same buffer size. Things were fine in Pro Tools 9, and this has only occured since upgrading to Pro Tools 10. I've tried downgrading to Pro Tools 9, but this is still happening. Has anyone else had this issue?
Presonus Firestudio Project and ASIO4ALL Buffer Size in Pro Tools 10.
2 Answers
-
Well...You don't want 1024 samples for recording, latency for recording and monitoring should be as low as possible. Is the Firestudio showing up in the set up menu? It should show up under PT as "Presonus Firestudio" or something along those lines.Let pro tools handle buffers though, if you set the buffer in one place chances are it's going to change elsewhere, so try uninstalling the drivers and ASIO and re-install the FS and go into PT and set your buffer size and that should work.
Use 2048+ for mixing, 64-512 for recording.
If you aren't using another DAW for recording, you don't particularly need to mess with the Presonus UC, save that for using other native DAWs that really and truly rely on ASIO like Reaper, Studio One 2, Cubase, etc.
-
I know, I use 1024 samples for mixing and lower samples for recording. I have to use the ASIO4ALL driver in Pro Tools otherwise if I use Firestudio Project driver, Pro Tools constantly crashes. I'm still able to use the Firestudio Project for monitoring and recording with this driver though. I've tried uninstalling all the drivers and Pro Tools but to no avail. I'll give it another try though.
Martin Swain | Jan 06 at 12:01
-
I see you have 9....How about trying going back to 9 and using the FS driver....I've heard a LOT about PT10 crashing like mad....Frankly I quit supporting avid but that's another story. I'd stick with 9 until 10 is way more stable. If it doesn't work or isn't solved shoot me an e-mail, I'm heading back home tomorrow and I'll be at my PT rig and I'll troubleshoot with you.
Astral Plane Studios | Jan 06 at 11:01
-
I do have PT9, and I've tried downgrading to it and trying it again but the same thing still happens, which makes me think that if it's doing it in 9 as well, then I can get it working properly in 10. I know what you mean about Avid, I used to use Cubase Studio 4 and never had issues like this. I just wish they'd stop beating around the bush and make their software more reliable for Windows systems. Thanks for the support.
Martin Swain | Jan 07 at 03:01
-
-
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. Pro Tools must be restarted for these changes to take effect. Please restart Pro Tools", it's best to ignore it and make sure that Pro Tools doesn't close down again so that you can still change things with ASIO4ALL.
From ignoring this error message, you can set the buffer size to what is set in Pro Tools and then restart Pro Tools again. From restarting Pro Tools, the buffer size in the Pro Tools and ASIO4ALL should be matched.
Astral Plane Studios Not the answers you're looking for? Try asking your own question.
