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.

Optimization library not found halion