Actually it doesn’t work with VEP 6.
I uninstalled version 6, and now VEP 5 recognizes H6 as H5 when I change its name.
Now, individually saved channel sets load with H6.
BUT, my existing VEP project (Metaframe), and this is the most important, still doesn’t load previously created channel sets, using the newly renamed H5.
This is ridiculous. One gets the advice to open a ticket. But nothing happens with that ticket until one starts complaining here.
I have also opened a ticket and heard nothing after the automated reply.
I was about to get the HS 5 to HS 6 upgrade. From reading the discussion here I take it that up"grading" actually sets you back in regards that one can’t easily use HS 5 besides HS 6. One has to remove HS 6 and “reinstall” HS 5 to get older projects working. Unless this issue has been solved i think i will have to pass on HS 6 for now, too much time consuming hassles in my case … F
No, H6 is compatible with H5 projects. All the content packs of previous versions are still there, and work the same way as before. You can even download and use true legacy HALion content in the old formats (from the ftp site) if needed, and use that in H6. You simply get new content, better stability, and a long list of new features/abilities.
It should not be a problem unless you need to use a 32bit host, or run on a really old OS such as Windows XP. That should be the only reason you’d need to downgrade to older HALion versions. If this is you…then you’d simply apply for a legacy ‘add-on key’ for your dongle.
I can load all my old Cubase 7 and 8 projects (even if they were made with 32bit versions) that were made with HALion 4 and 5 in my existing Cubase 9/HALion 6/Windows 10x64 or Mac setups without issue. All the old content packs stay with me…all the old fxb plugin set-up information kept in older daw projects still work, etc.
I can still load old Sibelius 7.5 - 8.x projects that I made with HALion 5. Because the plugin id is the same…Sibelius doesn’t know the difference…H6 loads where H5 did before. It loads the project and parses my default HALion setup as it always did. I just double Check HALion to make sure it has the program table and other settings I want (I store these as multi-presets), and keep right on working as before.
All my old 64bit Bidule setups that I created with H5 still work with H6 as they did before.
I can NOT get HALion 6 to work with Finale 2012 and Sibelius 6 on my old 32bit Windows XP laptop. In this case, I simply apply for an H5 add-on key for my Steinberg dongle, and roll back to whatever 32bit version of HALion works best for my old XP Laptop.
So…unless you need to roll back to support a 32bit Host or and old OS etc…you just use H6…even with your ‘old projects’ that may have been made using previous versions of HALion.
Occasionally I fire up an old 32bit DAW or sequencer on my 64bit Windows 10 system. Rather than uninstall H6 and roll back, I just use a virtual MIDI loopback port, reroute audio through the DAW, and run HALion in stand alone mode (or better yet, host it in Bidule and use rewire and reastream).
Really great that there is an update for Halion 6. Also it fixed my issue for Halion 6 in a Very Small Window not Sizeable. I hope that does not happen again, it was unworkable.
My question is, Why does Halion 6 or Steinberg Update software does not see or warm about this update to me as a user. It also happened with Wavelab 9 pro Update last time. I have to find out there is an update for Steinberg software available myself each time by looking at the support site or forum here ? If i log into my steinberg account no warmings about updates. If i use Wavelab 9 , halion 6 or C9pro, no warnings about new updates…
Is it really so every users must find out themselves by going to support or the forum to look themselves for updates ?
I have been using Halion Sonic 2, then 3 - just updated to Halion 6 and now all my projects using Sonic 2 or 3 are trashed. My authorizations for those instruments are gone, the project doesn’t load Halion 6 in their place, my sounds and settings are lost. I’m about to have some very unhappy clients. Any suggestions? I still have Sonic 2 and Sonic 3 installed, but they won’t load because my authorizations are gone.
If that didn’t fix your issues…open that elisencer app, and make sure you have the proper keys for Sonic and HALion on your dongle or soft elisencer. Be careful if you want to keep things on the software elisencer, as once you put it on a usb dongle, it can never go back to a software elisencer. You can move it from dongle to dongle, but never back to software eLisencer. So, be careful to put the key where you want it! If you did ever put it on a usb dongle, then that MUST be plugged in for anything to work properly.
Note…older HALion stuff will not work from a software eLisencer at all. Those MUST be run from your usb dongle. So…if you have upgraded to HALion 6, Sonic 3, and have a need to run HALion 5, Sonic 2 plugins, or older…you should contact support for a special ‘add-on’ key that works with those old plugins. I believe the special roll-back add-on key has to be on a dongle, and you’ll also need the H6/Sonic 3 keys properly set up somewhere on the system. Also note, that you should not really need to do this unless you’re trying to run some old 32bit host(s). Personally, I bridge instead of trying to roll things back in the rare case I need to run HALion in some ancient 32bit host. Options for bridging 64bit plugins to old 32bit hosts include jBridge, or running a 32bit instance of Bidule hooked up over ReWire.
If you still have plugins for older versions of HALion on the system, it’s probably best to uninstall them (or move the dll and/or VST3 wrappers to a VST directory that your DAW is not scanning for plugins). Keep all the content, but get rid of the apps and plugin wrappers.
I.E. I’ve got legacy HALion content going back to version 1. I’ve also got stuff I imported from AKAI and Roland Sampler disks. I’ve got HSO, and other things as well. I did not touch any of that ‘content’. I just uninstalled HALion 5, Sonic 2, while leaving all the content alone and then installed H6 and Sonic 3, which added new content, registered the old, and keeps plugging right along with my older projects.
Exceptions being really old projects that still try to call up HALion ONE. In those cases, I need to redirect the track(s) to H6 or Sonic 3 and manually set it up to use the old sounds.
Double check your plugin directory for your DAW. Make sure it is finding your H6/Sonic 3 plugins. Make sure it is NOT finding older versions of HALion and/or Sonic.
By Default, I believe the newer retail HALion and Sonic releases like to place their plugins in one or more of the following locations:
“%SYSTEMDRIVE%\Program Files\Common Files\VST3” (VST3 variants)
“%SYSTEMDRIVE%\Program Files\Steinberg\VSTPlugins” (VST2.x variants)
“%SYSTEMDRIVE%\Program Files\VSTPlugins” (VST2.x variants)