drag the vst preset into a slot, locate the samples, then click on the diskette icon in the toolbar above the program list. Each time you load the preset from there on out it should load seamlessly. You can also right click on the preset listed in the slot and choose save program…
In this scenario, the vst.preset is referencing the original samples?
But what if I want to make a vst.preset that is “portable”? Do I have to use the “Export Multi with Samples” for just one program? Or some other procedure like manually duplicating the source instrument and samples to a desired location for HALion programs, then import and save?
Referencing the original samples would save hard disk space, but I would like to have the preset and samples together for easy archiving and to avoid confusion.
Here’z the solution: Selecting the preset in either the Slot, or in the Program Table, makes it active in the Program Tree. Right-clicking on the program in the P-Tree gives me the contextual Import/Export>Export VST3 Preset with Samples.
Looks like I need to save my custom H4 vst3 presets in the same folder as my custom samples for the EXS 24.
I can then use the Export function above if I need to burn to disc.
Given that my folder(s) of custom samples are well organized, etc, it seems to make sense to simply follow the recommendation initially given so that the user presets show up in Media Bay. Otherwise “importing” is a pain…
Dr. V, can I ask you to try something for me please? Once you’ve exported your bass as a vstpreset together with samples, is it then possible to load that vstpreset into HALion Sonic SE for playback only?
[EDIT] perhaps what I mean is a “.vstsound” file, as it is mentioned in the manual that H4 can created these, as long as no samples from protected existing HSBs are used. I don’t yet have H4 but I’m looking for a reason to crossagrade, and this would be a major one if HSSE could load and play self-created .vstsound files.
Thanks Dr. V for that information. I’ve asked the same question over here but got no response, so at the risk of hijacking this thread I’ll repeat the reasons I think it would be great if HSSE could load “basic” vstsound files created in H4 (in case anyone from Steinberg is reading!)
HSSE is now available across the entire Steinberg sequencer family (including Sequel 3) so this means e.g.
– a trainer could create a soundbank in H4 (using only basic features that HSSE can play back) and distribute it amongst students so they can all work from the same material.
– a Cubase 6 user could use Cubase Elements 6 to work on an arrangement using a laptop without risking the Steinberg Key on the road. With version 6, Steinberg already very sensibly abolished the artifical restrictions on project file compatibility between editions (you can now open a C6 file in CE6), so the company is certainly aware that this compatibility is important to users.
– internet collaboration is made much easier because you only need to exchange the (bandwidth-hungry) sample bank once, then just email the project files around as work develops.
– a community would quickly establish for the exchange of self-produced sounds which HSSE (i.e. all Steinberg sequencer) users could benefit from.
At the moment, H4’s main competitor product requires the full version in order to play even unprotected sample banks created by other users, and the “free” player will timeout after 15 minutes in demo mode. Now, seeing as there’s no “free” stand-alone version of HSSE, but every current-version Steinberg sequencer user has it already, it would IMHO be a massive (sic) advantage for HALion 4 if self-created sounds could be played by lesser versions.
Clearly I don’t expect that sounds based on advanced features like the synthesis section of H4 would be playable in HSSE, but surely simple sample playback is possible? Again, I’m only talking about soundbanks created from one’s own samples using H4.