Since SM will not operate in Cubase8, I've been left to "install" the s90es as a hardware synth via the Cubase Device Manager, and assign the multi-mode instruments via the normal Cubase track routing. When opening a Cubase session, the s90es would automatically load all 16 patches, ALONG WITH their respective volume, fx, verb, etc. It was a simple and direct way to assign and manage the 16 available parts (patches) along with the associated volume, FX, reverb, pan, etc. Prior to upgrading to Cubase8 I used SM to control multi-mode voicing from the s90 engine within Cubase, via the MULTI-PART EDITOR. In order to work toward the best solution, allow me to explain how I used SM, and then perhaps you can advise on the best options to duplicate that in Cubase8. If you wish to use one of the products above with with the old Studio Manager then you must remain with the Editor version 1.4.0 (still can use SM2). Products that previously relied on the Studio Manager as "host" will continue to do so. New versions of the Editor Standalone/VST exist for the Motif XS-series, Motif-Rack XS, MOX6/MOX8, S90 XS/S70 XS, Motif XF-series, and the MOXF6/MOXF8. You will need to update your Yamaha hardware EDITOR version to 1.6.x in order to run as a standalone application. Link to External Instrument setup for Cubase Pro 8 Both are viable methodologies, as you will see. The Editor 1.6.x you'll find works just fine, right now!!! When the Updater comes you can choose to return to running as a VST3 plugin or continue running as an External Instrument plugin as outlined in the Standalone scenario. Yamaha spiced it up with advanced integration features between real synth and computer. Yes, this is a key advantage, and is at the core of Steinberg's VST protocol since the beginning. The whole concept of VST was to include both internal virtual synths and external hardware synths in the computer-based environment. The EXTERNAL INSTRUMENT feature is how any external hardware synthesizer can be setup to work with Cubase. (It actually has a distinct advantage to FW users). Other than that it works just like you've been used to, except you now can customize the Returns as you require. That is, it does not get automatically bundled into the Cubase Project File as when you run it inside Cubase. You'll need to save your Editor file separately. You still setup the Yamaha synth as a VSTi, and you'll run the Editor as a Standalone application. The Editor and the majority of the VSTi routing benefits are still available.Ĭurrently, you can use Automation, Freeze, Export Audio Mixdown, VST routing and processing by setting the keyboard up as an EXTERNAL INSTRUMENT Plugin (please see the link below for step-by-step instructions on how to set this up). Being an external device the computer has no idea of the workings of your external device, the VST Assistant (contained as part of the Extension software) will need to "teach" Cubase how to properly address the external Yamaha hardware. What seems to be broken is the software Extension that instructs Cubase about addressing the Yamaha hardware. The current Editor version 1.6.4 for Windows, 1.6.5 for Mac is fine and runs well, as a Standalone application. Or you can run it as a VST3 plugin within Cubase (that is what is broken, a fix is due shortly).Ĭubase Pro 8 has a known issue with the current Yamaha Extension (VST Assistant). The Standalone version no longer requires a separate host application. One download, that you simply launch as you require. The newer versions of the Editor contain both a Standalone and a VST version. With the release of version 1.6.0 (and later) of the Yamaha hardware synth Editors, the Studio Manager host application was obsoleted (it's over a year or more now). You now have just one program to deal with, the Editor itself, no separate host is ever necessary to run it standalone. You probably don't have a network setup or most people don't. Today's computer connectivity has taken on a peer-to-peer setup so the Editor has evolved. Stored and restored without having to do each device separately, the Studio Manager handled all external devices and their stored setups, per Project file. That is, bulk dumps of all settings could be managed neatly. Just to bring you fully up-to-date: Studio Manager, which acted as a "host application", was designed for a synthesizer/effect processor/digital mixer network setup, where an entire studio of external gear could be managed quickly and efficiently. The Studio Manager was obsoleted with the introduction of version 1.6.0 of the Editor quite some time ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |