1/24/2024 0 Comments Altiverb 7 winVE Pro 5 will put up an error when it fails to find AV 6 (even though AV 7 is now installed). I upgraded to VE Pro 5 to test if Alitiverb 7 really will load Altiverb 6 projects in the version of VE Pro 5 that Audioease apparently beta tested. They will investigate my case as it was not what they were expecting, so we will see if it is a one off on my system or not in due course. (I have not tested this - still on VE Pro 4). They say that their beta testing was with VE Pro 5, which is supported - meaning that AV 7 will transparently replace AV 6 in VE Pro 5 projects. I will send a ticket to Audioease in the meantime.Īudioease support have answered my ticket. Has anyone found that their AU version of AV 7 upgrade is behaving correctly? I cannot test this outside of VE Pro as I do not run Logic. Is this a VE Pro issue? Or an Altiverb issue? Despite the surprise that AV 7 (vst) magically slots in with Nuendo (and Protools I have read) this magic is not working in VE Pro. Unfortunately, VE Pro standalone (32 bit) does NOT do this. I have tested an old project and AV 7 does indeed load into the Plugin slot where AV 6 was previously loading. Well this is true on Nuendo (Mac) at least. There is also a new release of AV 6 that is Lion compatible at install too, before you jump to 7 for that single reason).Īudioease state on their website that projects that load up an AV 6 will automatically load up AV 7 and sound exactly the same. Unusually, the install OVERWRITES Altiverb 6 in the plugins directories, for all formats. You may be aware Audioease have now released Altiverb 7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |