The important thing (if you want it to show up in the HALion media bay), is that the VST3 presets using them should be in one of the directories/folders that HALion keeps scanning for potential new content. Establish your own locations and file naming structure as you see fit. While the VST Presets between Groove Agent and HALion 6 aren’t compatible…unlocked samples packed in their vstsound files are! So…the Cubase Media Bay can be used to bag and tag pretty much every sample and VST Preset living anywhere on your system! It’s great stuff, and once you get past the absurdity of how ugly, yet POWERFUL this relational database truly is…it’ll make quick work finding samples and designing things on scales both micro, and macro.Īs for managing raw samples that aren’t packed into a vstsound archive, or registered as a library…that’s up to you. In essence, Cubase/Nuendo can bridge all of your HALion engine content together. It’s my understanding that you can check off any directories here that you want Cubase, HALion, and more…to keep scanned for potential usable content. If you use Cubase or Nuendo, there’s yet another avenue through the Steinberg “Media Bay” to specify directories/folders, to tag/audition and more. The option in HALion’s “Browser” tab to import things, and have them automatically added to Media Bay on import. I believe it’s also possible to add directories that HALion will keep scanned for content in the Media Browser tab. If you are managing a workstation with multiple user accounts for the OS, and wish for all users on said system to have access to the VSTpreset(s), you might consider keeping them somewhere in “%SYSTEMDRIVE%\ProgramData\Steinberg\Content” %USERPROFILE%\Documents\Steinberg\HALion Sonic SE\VST3 Presets %USERPROFILE%\Documents\Steinberg\HALion Sonic\VST3 Presets %USERPROFILE%\Documents\Steinberg\HALion 6\VST3 Presets There’s also a button in HALion’s media bay that’ll force an update scan if something isn’t showing that you know should be living in a registered file path.Įxamples of common default locations for user made VST3 presets on a Windows setup: If you save or export VST presets and you want them listed in the MediaBay, make sure they are in a path that HALion keeps scanned. It can also hold extra library information such a version number, name, author, copyright info, etc. It can also hold scripts, macro XML info, graphics, and more. Point being, if it lives in a relevant path, it doesn’t necessarily have to be ‘registered’ by the Library app to use samples from it in your HALion and/or Cubase/Nuendo instances.Ī vstsound file can have just samples, just presets, or both. This can also hold true for some things like imported AKAI or Roland sample disk images. I think you can also make vstsound archives that have nothing in them but samples and or VST Presets (not true rolled libraries)…and simply having them in any directory that HALon and/or Cubase/Nuendo keeps scanned for content. You can also elect to copy/move the archive, or register it from where it’s already living. Using your native OS file explorer, double click the vstsound file (or one of them if you’ve made a library that uses multiple vstsound files), and Library Manager should open, where you can control where/how every vstsound library living in that same folder can be registered. If you’ve exported a vstsound library (packed the samples and programs into a vstsound archive), be sure to register it with the “Steinberg Library Manager”. Either move it to a place HALion keeps scanned, or ‘import it’ with the HALion “Browser”, or tag the directory it lives in with the Cubase/Nuendo Media Bay…etc. Of course you can pull it back into media-bay at will, however you see fit. You’re intentionally ‘exporting’ it to an isolated place…perhaps for sharing, perhaps for archiving, perhaps to pack into a library later, etc. Keep in mind that ‘exporting’ anything doesn’t show up in media bay on purpose.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |