According to the update FAQ "HALion 6 will replace your HALion 5 or HALion 4 plug-in installation.
After the installation of HALion 6 HALion 5 will not be available on your system."
Will next generation HALion installer/license do same behavior like H6?
If yes, do we need migrate preset/instance files AGAIN when upgrade to next generation HALion (7,8,9…) if using VST Host which HALion installer / VST Host apps will not be replaced (e.g. VEP, other VST plugin Chainer)?
Yes, all HALion generations since HALion 4 share the same plugin ID. This way the plugin of each generation can just be replaced with the latest generation and full project compatibility in DAWs is garanteed. It would be interesting to know what causes the issue in VEP.
If VEP uses the dll name instead of the internal plugin ID you could try renaming the halion 6 dll to the name of the halion 5 dll. This should make no difference to cubase and might save you from VEP problems.
Hope this helps.
That should not happen. Be sure to get the right dll (see in the Vep setup what folder it is scanning) and don’t change any other names as that will probably break halion. The dll has a different name but is still halion 6. Maybe after only setting the right halion to 5 force a rescan. And it must be the exact name halion 5 had when it was used by VEP.
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).