You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got the Beta 1.2 version working fine so far on PC windows 10 Pro Tools 12
The folder hierarchy is all wrong with the beta 1.2 version aax plugin the aax just goes to plugins folder, not in folders like the 1.1 version so do this
Install version 1.1 then go to c drive/program files/common files/Avid/audio/plug-ins
And copy the 3 Audiogridder folders and paste them to a folder on your desktop
then uninstall version 1.1 and install beta v1.2
then go back to c drive/program files/common files/Avid/audio/plug-ins
and cut the aax plugin and replace it to the one in folders on your desktop/folder you created/Audiogridder.aaxplugin/contents/x64 paste and over ride original file
and do the the same with instrument and midi aax
then copy the 3 folders back to the plugins folder
do a restart then it works fine
The server needs VST plugins installed on it.It dosent scan AAX kind of works similar to Blue Cats Patchworks as a vst wrapper
Tested it with waves V13 plugins so far what i Found so far VST presets not visible But the VST3 presets work
Noticed minimal latency on default settings with 5 Plugins on the chain
Haven't fully tested it yet but got it working for an hour
Keep up the Outstanding work Guys looking forward to future releases
Update Pro Tools Crashes when I click the lined square box to the left of the +- icons in the top right of the plugin box
Plugins working
FabFilter
Flux
Slate VMR
Amplitube
Waves
UVI Drum replacer
Sound Toys
Not Working
T-Racks not being seen in vst folders
But can see it on instrument tracks
Edit update
getting random audio artefacts on play back with AG plugin and still there when I remove the plugin. Playing back on all tracks either a scratchy crackling noise or a delay type noise depending on what plugin was used! System restart fixes the problem!
Unusable for me at the moment will wait for an update before I try using it again
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I got the Beta 1.2 version working fine so far on PC windows 10 Pro Tools 12
The folder hierarchy is all wrong with the beta 1.2 version aax plugin the aax just goes to plugins folder, not in folders like the 1.1 version so do this
Install version 1.1 then go to c drive/program files/common files/Avid/audio/plug-ins
And copy the 3 Audiogridder folders and paste them to a folder on your desktop
then uninstall version 1.1 and install beta v1.2
then go back to c drive/program files/common files/Avid/audio/plug-ins
and cut the aax plugin and replace it to the one in folders on your desktop/folder you created/Audiogridder.aaxplugin/contents/x64 paste and over ride original file
and do the the same with instrument and midi aax
then copy the 3 folders back to the plugins folder
do a restart then it works fine
The server needs VST plugins installed on it.It dosent scan AAX kind of works similar to Blue Cats Patchworks as a vst wrapper
Tested it with waves V13 plugins so far what i Found so far VST presets not visible But the VST3 presets work
Noticed minimal latency on default settings with 5 Plugins on the chain
Haven't fully tested it yet but got it working for an hour
Keep up the Outstanding work Guys looking forward to future releases
Update Pro Tools Crashes when I click the lined square box to the left of the +- icons in the top right of the plugin box
Plugins working
FabFilter
Flux
Slate VMR
Amplitube
Waves
UVI Drum replacer
Sound Toys
Not Working
T-Racks not being seen in vst folders
But can see it on instrument tracks
Edit update
getting random audio artefacts on play back with AG plugin and still there when I remove the plugin. Playing back on all tracks either a scratchy crackling noise or a delay type noise depending on what plugin was used! System restart fixes the problem!
Unusable for me at the moment will wait for an update before I try using it again
Beta Was this translation helpful? Give feedback.
All reactions