Well somehow or other, using a combination of try-outs you mentioned and other stuff, eventually something seemed to click and I can now see all instruments and their presets. I’ve since gone through Mediabay in Cubase and asked it to ignore my Desktop and Download directories, as I like to keep things there that I’d rather Cubase not try to bag and tag as usable media.įinally, double check that you don’t have some sort of filter set by accident in your Sonic Media Bay. When I moved all that stuff to some directory that I know the Cubase Media Bay ignores, all my problems went away. I had quite a few things in a directory on my desktop, and at the time Cubase was set so it would keep tabs on stuff kept on my desktop. It seems like I once had some problems when identical content got scanned twice (once by HALion itself, and again via the Cubase Mediabay). Be careful not to keep backups or unzipped installers containing vstsound archives of HALion content packs in a directory that gets scanned on a regular basis via your Cubase “Mediabay”. In short, you want to make sure the actual vstsound files are in ProgramData, otherwise permissions problems can arise if you try to use things from different user accounts.Īnother thing I’ve found that seems like it might cause issues if you happen to use Cubase. Personally, to clean it all up, I ended up moving all of the actual vstsound archives from the various user AppData locations to the ProgramData location, and optionally deleting any of the shortcuts in “%AppData%\Steinberg\Content\VST Sound”. In some cases you might find ‘shortcuts’ in your User AppData folder pointing to the above location, or vice verse. In a nutshell, if you want content to be available to all system users, it should be in the “%SYSTEMDRIVE%\ProgramData\Steinberg\Content\VST Sound” directory. “Install for all users on this system” or something like that. When this is NOT ticked, things tend to go into the AppData directory of the administrative account installing things. Some confusion comes into play on installation locations based on how a user ticks a box upon running the installer. As I don’t have Sonic 2 I don’t currently have a way of overcoming this. In another thread someone suggested that Halion 3 does not install all bits of older versions, e.g. I guess I am asking if anyone knows an appropriate file location for the presets and for the sounds themselves so that they become visible to Halion. I thought I knew what I was doing when it comes to daws and software but I have now had three goes at this and it has me beat. In my appdata folder the two groups appear in different VST folders, one in the Content VST folder, the other in the Halion VST folder.Įven more confusingly the additional VST content appears under C: program data Steinberg etc. In Library Manager I can see the file pathways and have tried moving locations but to no effect. In Library Manager these show as ‘Installed’. Some instruments such as World Percussion don’t appear in Halion at all. In Library Manager these show up in the ‘Managed’ list. Instruments such as Skylab, Hot Brass and the like are visible within Halion but with no available presets and obviously they don’t load. All licensed and recognised and works as a VST plugin should. Installed Halion 3 for use as a VST plugin in a non-Steinberg sequencer. Well I have read all the other posts I could find on this and I am still utterly confused.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |