Out now: HALion 6 and HALion Sonic 3

Mac user here, so no W7 input. That said, very impressed with the H6 upgrade from H5. Sternberg clearly put in a lot of effort into this. Between the incorporated scripting and macro environment, the new instruments, ease of install, etc., great job. It’s certainly a large (size) upgrade, but the Download Assistant worked well and relatively fast. I manually moved the sound files to an external drive and replaced with alias files (which took some time). Really a more significant release than I expected. Clearly H6 is a capable competitor with the other sampling products. Will be interesting to see what content get’s released for H6, over time. Good job Sternberg team!

What do you mean by ‘replaced with alias files’?

Hi,
I´m win7 64bit, bought HS3 upgrade from HS2,
installation and activation went fine,
when I try to open HS3, cubase (6.5) crashes every time.
Please update for win7.
Kind Regards

It’s a no brainer, HALion 6 must have decent WIN 7 support!

My WIN 7 DAW with Cubase 9 works beatifully and is as solid as a rock, the best system I have ever had. Please don’t loose touch with the musician’s usability. I need my system to work as it does for a few years yet without ‘technical issues’ getting in the way. I understand eventually I will move to WIN10, but I also understand most people using a PC with Cubase/Halion currently use WIN 7.

++1 exactly as above.

I will not upgrade my H5 license until WIN7 is on the supported OS list from Steinberg

My Steinberg is down cant authorise my H6, seems to have been like this for a while, any info ?

If you take an installed HALion 6 .vstsound file and move it to another drive, then point to that newly located .vstsound file with an Alias file in the original location, the HALion 6 will use the Alias file as a pointer to the actual sound file. On a Mac, the sound files are stored in the Macintosh HD/Library/Application Support/Steinberg/Content/ folder – and in the case of HALion 6, (many) new sound files are written into the HALion and VST Content sub folders there. Just a way to free-up space on the system hard drive, given the large size of the HALion 6 sound files. I haven’t used the HALion Library Manager app yet, so it may in effect do the same thing (perhaps easier than the manual process).

Thanks for that explanation, but where do the ‘alias’ files come from? How are they created?

In OS X on the Mac, right-click on the moved .vstsound file(s) you want to make Alias’ for, and select “Make Alias” from the drop-down list in the menu. An alias file will be created with the same name and “.alias” added to the end of the filename. In the case of .vstsound files, it will end up being a .vstsound.alias extension on the file. Just delete the .alias portion (so that the alias is exactly the same name as the .vstsound file(s) in the original folder), and your good. I believe in the Windows/PC world, the equivalent would be called a Shortcut, with the same process applied.

If you Hold Command and drag the original sample files to a folder on the alternate drive, it will move instead of copy them.
Then if you hold Command and Alt/option and drag them all back to the original folder, it will create Aliases of those files without the .Alias on the end of each file.
You may find this technique handy and less work.

Hope his helps.

Rick