I’ve been working with HAlion 6 the last few days, having upgraded from Absolute 2 to 3. With all due respect, a few observations and suggestions: HALion works well, and have quickly been inspired to improv a number of new pieces quite easily. Much fun, very nice on this custom Mac Pro 5,1 & Mac OS Sierra.
I note there is much discussion elsewhere on this forum about downloads and library location issues, but as far as I see, that discussion appears exclusively related to Windows users. Here I also run Win 10 with parallel installs, but not as much recently given that Win generally takes much more time & re-boots vs. Mac OS.
Re. the library location issues. I run all of my sample libraries from a dedicated 2GB SSD (Spectrasonics, AIR, Steinberg, Avid, Ableton Live, Native Instruments etc). The Steinberg installer seems very good: download the installer application, choose the app (say HALion) and download to a drive. Run the installer & choose ‘custom’ to point the library location to the correct folder on the SSD. Fine. However, the confounding issues I find with all Steinberg installers (Absolute 3, Cubase Pro 9, Nuendo 7) are this:
It is very vague as to if libraries need to be replaced /updated and what goes where, when. One is somewhat left to guesswork. In the case of similar installation updates from some other manufacturers, once the first installation has been done and the file path set, this is remembered via preferences and subsequent installers can act intelligently, accordingly (NI, for example).
Would be very useful if Steinberg installers explicitly followed the same approach - maybe some do in a roundabout way, but it is never really made known to the user. We really shouldn’t haven’t to be installing the same base libraries over and over, just to ‘be safe’. At the very least, I suggest Steinberg provide some basic installation documentation with each installer to make this clear. For example:
In the case of my Absolute 2 to 3 update, it is not made clear in the installer as to exactly which components are required to be downloaded and installed, and in particular, which libraries need to be updated. As it happens, I took a guess based on some forum comments and only downloaded HAlion 6, then installed /updated its libraries. That would seem to be all that was required – all seems to work fine & the new library manager is a welcome addition which seems to confirm this. Again: would be useful for Steinberg to be specific about this in the documentation. It would seem that Absolute 3 only provides a new HALion, and that is all that is required (vs downloading gigabytes of Absolute 3 VI installers, installing them and wrestling with libraries for ages).
Otherwise, a couple of other observations & suggestions:
-
Very odd that HALion does not have (say) an iPad app for use with the Sphere and other controllers (just like Spectrasonic’s Omnisphere). HALion has so much control potential, but presently remains confined to mouse clicking or manual setup with external controller(s).
-
Eternal control. I’m using an Akai Advance 61, also Ableton Push, and other colleagues similar with various Akais, Novations, NI etc. The Advance did set up well with HALion for controlling macros etc, but in all was a manual process with much trail and error, and often on a per patch basis. I suggest that a number of external controller profiles be made available in the HALion setup prefs, or perhaps as per the Cubase /Nuendo CP where at least this only needs to be learned & configured once as a MIDI controller.
Would also be nice to see VST3 support in the Akai VIP and/or NI Complete Kontrol, but that’s another story …
Loving HALion 6, a solid contribution to my musical instrument collection.