If we tell it to ‘copy’ the content, it makes a ‘copy’ of the vstsound archives to “ProgramData\Steinberg\Content\VSTsound” and registers them. If we tell it to ‘move’ the content when registering, it moves the whole file to “ProgramData\Steinberg\Content\VSTsound” and registers it. When double clicking on a *.vstsound archive, it scans all vstsound files in the same directory and if they are not already installed we get some options. The new Library Manager allows us to register content from any location we like. “C:\InstallerScreenTank”) and see if that clears things up. If so, try moving your installer directories (any installers that contain unpacked vstsound files) elsewhere (I.E. If you’ve not installed anything out of ordinary on your own using the Library Manager, it still might be that the directory where you downloaded and installed Halion 6 or Sonic 3 from, happens to be in a directory that gets scanned for MediaBay on a regular basis. The point is, if you’ve got extra copies of some vstsound archives lurking somewhere, make sure that you do not keep such extraneous copies in a directory that Halion and/or Cubase keeps scanned for content. I reinstalled those user content packs with the Librarian, and they worked as expected, plus, no more popups. So, I moved the fresh archive that seemed to be causing trouble to a location that doesn’t get scanned, and the pop-ups went away. In the past I’d also kept some vstsound archives in here that I often got samples from to build with in Halion 5, but didn’t have any important ‘Halion presets’ stored in…so I’d simply been treating them like MediaBay browseable sample containers. I checked the Media Bay in Cubase, and as suspected, I had toggled this directory for continuous scanning of potential content, since I often keep lots of wav/aiff, and other shorter sample content stored there and like to have it bagged, tagged, and preview ready in Media Bay. So I figured, Halion must still be asking for this content for a reason…but why?Īt some point it hit me, “I wonder what would happen if I move this vstsound archive that I’ve kept lingering in “C:\Samples” to a directory that is NOT set to be scanned by the Cubase Media Bay for content?” I kept getting the popups after doing this, even if I used the Library manager to unregister, and delete the said content from “ProgramData\Steinberg\Content\VSTsound”. I’d installed it with the Halion Library Manger, which also put a fresh copy (I’d asked it to copy rather than move) into the usual “ProgramData\Steinberg\Content\VSTsound” directory that Halion likes to keep things. The catch seems to be that I’d asked the MediaBay in Cubase to keep a continuous scan for any samples and other content stored in “C:\Samples”. I unzipped them to a location (“C:\Samples\Halion\VSTsound”). I had downloaded some User made content packs ( found here) individually at some point. I got this at one point, but tracked it down to what seems to be this: In testing, I install and uninstall lots of things Halion related, and more often than not, reinstalling and cleaning up eLicenser clears things up for me. Over time I’ve learned to start here anytime something Steinberg acts up, particularly after installing new Steinberg software or updates. Even if it’s the latest version, go ahead and download a fresh copy and reinstall.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |