halion 1 to halion 2 question...

stephanie · Posted: Mon Jan 17, 2005 3:38 pm Post subject: halion 1 to halion 2 question...

I just learned that I can install sx2 and still keep and use my good old cubase vst 32.....am I assuming correctly that I can use both halion 1 and 2 as well?

...thanx! smells like I'm going to upgrade many things real soon Smile

J L Bowie · Posted: Fri Jan 21, 2005 7:55 pm Post subject:

Hi Stephanie, are you talking in general about being able to use Halion 1 and 2 on separate systems as a legal owner, or simply wanting to know if you can run them on the same system? In any event, the answer to the first part is, yes, you can use both Halion 1 and 2 on separate systems, they are both yours. afterall. However, if you are asking about whether or not you should use them both on the same system, the answer is no, you should deinstall the older version prior to installing the newer one to avoid any conflicts, and the same applies to Halion 3. I hope one of these answers your question.
_________________
Originally registered Nov. 2002

XPHM SP2
Sys1: XPH, DM4800 via FF800 , UAD-1x2, Cubase 5.5, GA 3, Sys 2: Win7 64bit, DM4800 via IF-FW/DMmkII, Houston, Nuendo 5.01 +NEK 64bit, Omnisphere & Trilian, HSO 1.5 64 bit, Hal 3.5 64bit

Alex D · Posted: Tue Jan 25, 2005 1:26 am Post subject: Thats's not a proven problem

That's not a proven problem.

I run HAL2 and HAL 3 on the same machine without a prob.

You need to install hal2 and open cubase once.
Now rename HAL2 dll to something else like Halion2 and rename the HAlion folder to HALion 2.
Create a new HAL 3 folder and install HAL3 to that folder, be carefull not to wipe out HAL 2 in the process
by accidentaly allowing HAL3 to install to the HAL2 folder, if you do you need to uninstall and start again.

Now you will have HALion 2 available in Cubase VST rack & HALion (HAL3).
Now you can create copies of the HAL3 dll&srf and rename them to versions that you can use to have
personalised output configs. Try a seperate sub folder inside the HAL3 folder for this.

The Origional HAL3 dll must remain Halion.dll, this means the standalone can load it and any projects
created with HAL 1&2 are compatible with that origional named version of the HAL3 dll.
It unfortunately means that if you open up a project created with HAL2 and HAL3 is currently installed
HAL2 wont appear, HAL3 will appear becuase it is now the installed dll named 'Halion.dll'.

I havent tried creating a seperate folder outside of the standard Steinberg VST plugins folder for HAL 3,
doing this may afford the freedom to have HAL2 as the default version occupying the 'Halion.dll' label.
I can say that the standalone version of HAL3 needs a HAL3 dll named 'HALion.dll' or it wont work.

Regards

J L Bowie · Posted: Tue Jan 25, 2005 2:20 am Post subject:

Nothing like keeping it simple; but the question remains, why would you want to keep them both? Anyway, despite all that, I would get the old one off my system completely before installing the new one, per Steinberg's suggestion.
_________________
Originally registered Nov. 2002

XPHM SP2
Sys1: XPH, DM4800 via FF800 , UAD-1x2, Cubase 5.5, GA 3, Sys 2: Win7 64bit, DM4800 via IF-FW/DMmkII, Houston, Nuendo 5.01 +NEK 64bit, Omnisphere & Trilian, HSO 1.5 64 bit, Hal 3.5 64bit

Helge Vogt · Posted: Tue Jan 25, 2005 8:46 am Post subject:

I don´t want to go into too many details, but there CAN be problems installing HALion versions parallel. The short answer is: all HALion versions use the same VST ID number and this number is used to remember a Plug-in by many Hosts (not the name alone). Under specific circumstances the Host may be confused which HALion to load as they share the same ID. In this case it may just load the dll which name comes first in alphabetical order. If the HALion versions wouldn´t share the same VST-ID you wouldn´t be able to load old projects with a newer version of HALion. Sharing HALion versions is therefore not recommended (and unsupported), though it usually works in Steinberg Hosts.

Helge

stephanie · Posted: Fri Jan 28, 2005 7:10 am Post subject:

Thank u all for the answers....hmm....guess I better not play with fire!
The reason I wanted to run both is simple....I want to compare both, especially on the "cpu effectciveness" factor, among other things and also, like a smooth transition, meaning, keeping using (for work) the H1 i know so well while learning H2. I just hate removing a software I like and that runs smooth.....! THANX AGAIN!