I don't know if I'm doing something wrong, or downloading things that are incompatible for my daw. I'm using Pro Tools Express for now, and according to their FAQ:
Q: Does Pro Tools Express support 64-bit?
A: Like Pro Tools 10, Pro Tools Express is compatible with Mac and Windows 64-bit operating systems. However, it does not run natively as a 64-bit application at this time.
Q: Is Pro Tools Express compatible with third-party AAX and RTAS plug-ins?
A: Yes, Pro Tools Express supports AAX Native (32-bit), RTAS, and AudioSuite plug-ins from Avid and our development partners. You can find these in our Plug-in Finder.
I've been looking for some amp sims, and I stumbled across a GK one I wanted to try out. Invalid Link Removed
The compatibility specs for the plugin, according to the link are as follows: AAX 32b, AAX 64b, Standalone app, VST2 32b, VST2 64b, VST3 32b, VST3 64b
For whatever reason, I can run the app as a standalone, but my daw will not recognizing it. I keep getting a pop up stating, "Pro Tools could not load it because no valid authorization could be found, the iLok key could not be found, or the plugin was damaged.
Given that it works as a standalone, I doubt the plugin is damaged, my daw loads when I close the standalone, so it's not the iLok. I also had to register, and input a serial number to be able to download the plugin, so I'm leaning against it being unauthorized.
I really wouldn't care, but when using it as a standalone, I can't load my daw. I get a message that states, "The selected ASIO audio device could not be initialized. Please choose another audio device." If I close the standalone version of it, my daw is then recognized and works as it should. Am I installing it in a wrong folder, (I'm using the default folders it prompts to save them in.) am I misunderstanding the info on Pro Tools FAQ, and the plugin's compatibility, or is it something entirely different? I'm at a loss now, and have not one clue as to what to do. This is also not the only plugin this has happened to me with. Seems to happen with most I've tried to check out. The difference this time is, this one doesn't sound to bad, and I'd likely upgrade to the the professional version if I could get it to work. So if anyone can help me get this sorted, it's greatly appreciated.
Q: Does Pro Tools Express support 64-bit?
A: Like Pro Tools 10, Pro Tools Express is compatible with Mac and Windows 64-bit operating systems. However, it does not run natively as a 64-bit application at this time.
Q: Is Pro Tools Express compatible with third-party AAX and RTAS plug-ins?
A: Yes, Pro Tools Express supports AAX Native (32-bit), RTAS, and AudioSuite plug-ins from Avid and our development partners. You can find these in our Plug-in Finder.
I've been looking for some amp sims, and I stumbled across a GK one I wanted to try out. Invalid Link Removed
The compatibility specs for the plugin, according to the link are as follows: AAX 32b, AAX 64b, Standalone app, VST2 32b, VST2 64b, VST3 32b, VST3 64b
For whatever reason, I can run the app as a standalone, but my daw will not recognizing it. I keep getting a pop up stating, "Pro Tools could not load it because no valid authorization could be found, the iLok key could not be found, or the plugin was damaged.
Given that it works as a standalone, I doubt the plugin is damaged, my daw loads when I close the standalone, so it's not the iLok. I also had to register, and input a serial number to be able to download the plugin, so I'm leaning against it being unauthorized.
I really wouldn't care, but when using it as a standalone, I can't load my daw. I get a message that states, "The selected ASIO audio device could not be initialized. Please choose another audio device." If I close the standalone version of it, my daw is then recognized and works as it should. Am I installing it in a wrong folder, (I'm using the default folders it prompts to save them in.) am I misunderstanding the info on Pro Tools FAQ, and the plugin's compatibility, or is it something entirely different? I'm at a loss now, and have not one clue as to what to do. This is also not the only plugin this has happened to me with. Seems to happen with most I've tried to check out. The difference this time is, this one doesn't sound to bad, and I'd likely upgrade to the the professional version if I could get it to work. So if anyone can help me get this sorted, it's greatly appreciated.
