![]() You can confirm the difference in resolution by counting the number of bars along the top - all I did was change the properties as CWS suggested. (In one of their least helpful service responses, Steinberg denied that there was any difference in resolution, so let me say that the scaling I had was, for me, perfect. So you can see what I mean, I have re-posted screenshot 3 above, which shows good Cubase window resolution but with the plugin cut off and, for comparison, a screenshot which shows what happens when I did what CWS suggested, ie poor Cubase window resolution but full plugin GUI. If you can solve that one, (or anyone else), you will earn my eternal gratitude! ![]() So the issue is now slightly modified - how can I retain my windows scaling and Cubase HiDPI settings and see the full plugin display? So, congrats to CWS, that is a solution.īut I lose the overall screen resolution I had before. Having changed the properties as CWS said, I do get a full version of the GUI. So in my screenshot of the Cubase window in my initial post above, I have good resolution with lots of legible info on the screen. Download trial version Unmatched versatility From electronic beats to orchestral arrangements, Cubase is flexible enough to adapt to any genre, catering to the creative needs of artists of all styles. See my post here: ( Cubase Pro 11 screen resolution issue following upgrade from Cubase Artist 10.5) Cubase empowers musicians with a vast array of cutting-edge tools for composing, recording, editing, and mastering music effortlessly. I spent a little time last year trying to get Cubase to display at a resolution which I was happy with. Your method does indeed solve the issue of the plugin GUI, but at the expense of screen resolution of the Cubase Window. Read more.Hi and thanks so much for your response - it’s very much appreciated. In all cases mentioned above, a logic and clean folder organization will allow you to reliably bridge where needed and get rid of the additional software when the need for a bridge no longer exists. Instructions on how to switch the bit mode of an application under Mac OS X can be found here. On Mac OS X, Cubase 6 up to Cubase Pro 8.5 can be used as a 32- or 64-bit application. On Windows, both versions of Cubase can be installed and used separately. Click Add Track to create a new Instrument Track for MASSIVE. In the Add Instrument Track window, open the Instrument drop-down menu and select the NI plug-in you wish to use. It includes a huge library of high-quality drum samples and tons of MIDI grooves and fills that you can arrange however you like to quickly lay down a drum track. Right-click on the Track list in Cubase and choose Add Instrument Track. In Cubase and Nuendo, the list of monitored VST2 folders can be managed here: Cubase 8/Nuendo 7. In any case, remember that your VST host application must know the installation paths of your VST2 plug-ins. Still, it is a viable (and possibly the best) option to open older projects that were completed with a 32-bit version of Cubase. What it does: MT Power Drum Kit 2 is the fastest, easiest way to get high-quality drums out of a free VST. 32-bit plug-ins on 64-bit Windows: C:Program Files (x86)SteinbergVstPlugins.dll. A quick reminder: a 32-bit application can only address 4 GB of RAM on a 64-bit Operating System. This option is only recommended, when you don't use sample libraries, orchestral templates or memory intensive VST Instruments. Use the 32-bit version of Cubase along the current 64-bit installation.However, please note that jBridge is not officially supported and we cannot provide support in case jBridge is causing issues. It has several user-selectable options which allow for perfect results with some experimentation and tweaking. ![]() jBridge is an inexpensive third-party solution for bridging. Usually, it will work fine with older Steinberg plug-ins, but the outcome might vary, especially with 3rd party plug-ins. Use the internal VST Bridge (only in Cubase 4 to Cubase 8.5 and Nuendo 4 to Nuendo 7).This is indeed the easiest solution to manage (system-wise), but replacing several plug-ins in existing projects might be cumbersome. Ditch old 32-bit plug-ins and find native 64-bit replacements.But in general, using 32-bit plug-ins in an 64-bit environment can be problematic and cause various problems.Īs of now, you have various options to choose from to deal with this situation: Although 64-bit operating systems and hosts are the norm for years, you might need to use older plug-ins for backward compatibility or a particular VST Instrument which has been discontinued.ģ2-bit versions of Cubase 4 to Cubase 8.5 and Nuendo 4 to Nuendo 7 came with a VST Bridge meant to make the transition to 64-bit systems easier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |