Folks,
I want to try to post a potential solution for an issue that I have been seeing a lot lately with PT. And the reality is, ever since AVID’s open standard of audio hardware in PT version 9, this has been an issue. I first had this issue in version 9. Back then, I have solved it primarily by using specific audio hardware. But recently I changed hardware, I went from RME-audio which worked flawlessly with PT to using a Presonus SL 24.4.2 Mixer as my audio interface as a way of gaining some I/O. The RME has 16 channel I/O, the Presonus has 24. With Presonus hardware, all the errors of what I went thru in version 9 trying to talk to Focusrite equipment came back to haunt me. With Presonus, I get that non-stop relentless “ASIO properties have changed in control panel, protools must quit, etc, etc” - and it would be nice if rebooting or relaunching the app was all you had to do to fix it, BUT ITS NOT. This issue would NOT GO AWAY for me. I discovered thru the help of other forum users that its VITAL that your firewire use the LEGACY drivers, not the ones Windows will put on by default. If you don’t know how to do this, refer to the performance tuning steps for AVID, I believe its there. If your system is like mine, this will not be the end all fix for you:
Next concept:
I went to ASIO4all.com and downloaded their free driver. As I understand it, asio4all is a sort of dummy do nothing audio engine that cant produce any sound what so ever. Its only job in life is to make PT think it has something on your box that resembles an audio engine to talk to. But if you get the error I get, you’ll want to use ASIO4ALL to help you launch PT and hopefully work. This loading sequence seems to work for me for everything from version 9 thru 11. Try this if you are having audio control panel issues in PT:
1) EACH AND EVERY TIME YOU Launch Pro Tools and as soon as you see the black load up window, press and hold down your “n” key and do not let up until you get the new window asking about what engine to load up for pro tools.
2) Specify “ASIO4ALL” and click OK
3) Once PT fully loads, do not load a song yet, go back into your audio engine and specify the audio engine you intend to use for your normal day to day projects.
4) Load up a project and test it out, for me this process has worked each and every time regardless of versions.
Below is the relevant parts of my SANDRA so you know what Hardware I have and how it may compare to your system:
Mainboard : GigaByte X58A-UD3R
BIOS : Award (OEM) FB 08/24/2010
Total Memory : 16GB DIMM DDR3
----------------------------------------------
Processors
Processor : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (4C 3.1GHz, 2.16GHz IMC, 4x 256kB L2, 8MB L3)
Socket/Slot : FC LGA1366
----------------------------------------------
Chipset
Memory Controller : Gigabyte X58 I/O Hub 2x 2.43GHz (4.86GHz)
Memory Controller : Gigabyte Core Desktop (Bloomfield) UnCore 2x 2.43GHz (4.86GHz), 3x 8GB DIMM DDR3 1.08GHz 192-bit
Memory: 24Gig
----------------------------------------------
Graphics Processor
Peripherals
FireWire/1394 Controller 2 : Gigabyte TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller
SMBus/i2c Controller 1 : Intel ICH SMBus
What you don’t see here in my SANDRA is, I still have my RME card on my system. One day I curiously disabled that card in control panel of Windows.. From that point it should theoretically NOT BE ACCESSABLE to ANY software when you do that. But for some stupid reason, This is NOT the case with PT. Even disabled in Windows, PT still has that as one of the options of audio engines in the list. This is very fishy to me.. I believe AVID HAS some issues in how audio engines load..
But anyway, I want to share this with as much people and hope it helps some out at least. Its been a long time issue with AVID and I really don’t know if its ever going to get fixed. If I hadn’t discovered the above, I would have no choice but to cut AVID PT lose forever.. Either you can make music with or you can’t, its just that simple!!
Have a great day!
I want to try to post a potential solution for an issue that I have been seeing a lot lately with PT. And the reality is, ever since AVID’s open standard of audio hardware in PT version 9, this has been an issue. I first had this issue in version 9. Back then, I have solved it primarily by using specific audio hardware. But recently I changed hardware, I went from RME-audio which worked flawlessly with PT to using a Presonus SL 24.4.2 Mixer as my audio interface as a way of gaining some I/O. The RME has 16 channel I/O, the Presonus has 24. With Presonus hardware, all the errors of what I went thru in version 9 trying to talk to Focusrite equipment came back to haunt me. With Presonus, I get that non-stop relentless “ASIO properties have changed in control panel, protools must quit, etc, etc” - and it would be nice if rebooting or relaunching the app was all you had to do to fix it, BUT ITS NOT. This issue would NOT GO AWAY for me. I discovered thru the help of other forum users that its VITAL that your firewire use the LEGACY drivers, not the ones Windows will put on by default. If you don’t know how to do this, refer to the performance tuning steps for AVID, I believe its there. If your system is like mine, this will not be the end all fix for you:
Next concept:
I went to ASIO4all.com and downloaded their free driver. As I understand it, asio4all is a sort of dummy do nothing audio engine that cant produce any sound what so ever. Its only job in life is to make PT think it has something on your box that resembles an audio engine to talk to. But if you get the error I get, you’ll want to use ASIO4ALL to help you launch PT and hopefully work. This loading sequence seems to work for me for everything from version 9 thru 11. Try this if you are having audio control panel issues in PT:
1) EACH AND EVERY TIME YOU Launch Pro Tools and as soon as you see the black load up window, press and hold down your “n” key and do not let up until you get the new window asking about what engine to load up for pro tools.
2) Specify “ASIO4ALL” and click OK
3) Once PT fully loads, do not load a song yet, go back into your audio engine and specify the audio engine you intend to use for your normal day to day projects.
4) Load up a project and test it out, for me this process has worked each and every time regardless of versions.
Below is the relevant parts of my SANDRA so you know what Hardware I have and how it may compare to your system:
Mainboard : GigaByte X58A-UD3R
BIOS : Award (OEM) FB 08/24/2010
Total Memory : 16GB DIMM DDR3
----------------------------------------------
Processors
Processor : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (4C 3.1GHz, 2.16GHz IMC, 4x 256kB L2, 8MB L3)
Socket/Slot : FC LGA1366
----------------------------------------------
Chipset
Memory Controller : Gigabyte X58 I/O Hub 2x 2.43GHz (4.86GHz)
Memory Controller : Gigabyte Core Desktop (Bloomfield) UnCore 2x 2.43GHz (4.86GHz), 3x 8GB DIMM DDR3 1.08GHz 192-bit
Memory: 24Gig
----------------------------------------------
Graphics Processor
Peripherals
FireWire/1394 Controller 2 : Gigabyte TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller
SMBus/i2c Controller 1 : Intel ICH SMBus
What you don’t see here in my SANDRA is, I still have my RME card on my system. One day I curiously disabled that card in control panel of Windows.. From that point it should theoretically NOT BE ACCESSABLE to ANY software when you do that. But for some stupid reason, This is NOT the case with PT. Even disabled in Windows, PT still has that as one of the options of audio engines in the list. This is very fishy to me.. I believe AVID HAS some issues in how audio engines load..
But anyway, I want to share this with as much people and hope it helps some out at least. Its been a long time issue with AVID and I really don’t know if its ever going to get fixed. If I hadn’t discovered the above, I would have no choice but to cut AVID PT lose forever.. Either you can make music with or you can’t, its just that simple!!
Have a great day!
Aucun commentaire:
Enregistrer un commentaire