As an alternative you could create audio exports of affected tracks. Nevertheless, plug-ins used through the VST Bridge should be replaced as soon as possible. Please keep in mind that all 32-Bit plug-ins used via the VST Bridge still have to share a maximum of 4 GB RAM - the 32-Bit limit remains regardless of the overall installed and available system memory. Your Cubase/Nuendo projects can be opened without missing plug-ins (if installed) on your new system to the greatest possible extent. It offers the possibility to switch from a PowerPC-based Apple Macintosh computer to an Intel-based model, respectively to switch from a 32-Bit PC Windows system to a pure 64-Bit environment.
The VST Bridge is meant as a transitional aid The VST Bridge runs as a separate process in the system and is not part of the host application process. However, even if a plug-in used through the VST Bridge crashes and potentially crashes the VST Bridge itself, the host application remains unaffected. Consequently, the usage of "bridged" plug-ins can result in higher CPU load and the plug-in user interface may react slowly.įollowing the VST (2.4) specifications is very important for bridged plug-ins. A plug-in which runs through the VST Bridge cannot be executed as efficiently as a version available in native program code. There are no additional latencies introduced but the computer needs resources for the translation.
You can imagine the VST Bridge as a kind of simultaneous translator for program code. In later Cubase/Nuendo versions, 32-bit plug-ins can only be loaded using unsupported 3rd party solutions like JBridge. Please note that Cubase 8.5 and Nuendo 7 are the last versions that include the VST Bridge. In both cases the VST Bridge enables compatible Cubase/Nuendo versions to execute program code not natively available for the used platform.
0 kommentar(er)
