I take the view that the new H6 licensing from SB a “FORCED Cross-grade” and NOT an Up-Grade
When I upgrade my Cubase Product to C9, I can still run prior versions of Cubase, be it for backward compatibility, simply by either launching the prior Cubase version application.
It was the same when I upgrade 8.0-to->8.5, or 7.5-to->8.0 and so on … …
At any time, I could/can run any/all Cubase versions, simply by unplugging the USB-dongle from one PC to another, or to an OSX machine or to a laptop etc, all of which could have different versions of windows or OSX and/or Cubase version installed.
I have not yet paid for the so termed “Upgrade to H6” that is on offer in the SB-shop -
I am waiting for the trial version to test
I am waiting for WIN7-64bit Official support
I am waiting for the right to use my previous versions of HALion
Like many I was shocked at no support for win7-64bit, and furthermore their deprecating WIN7-64bit support without any pre announcement or fair warning from SB
NOW, … I’m reading from the below links regarding the loss and right to use HALion5 !!
ref ( https://www.steinberg.net/forums/viewtopic.php?f=262&t=112696
We as consumers/users should still be able to run BOTH H5 and H6 or other Upgrade purchases we have made.
If I want to run HALion 4.x on my old PC running an old operating system, I SHOULD STILL BE ABLE TO.
SB must not disable / remove / deactivate the use of any (32bit or 64bit) release versions of any software product from our usb-elicense keys – WE HAVE PAID FOR THE RIGHT TO USE PRIOR VERSIONS THAT WE HAVE UPGRADED FROM!!
I have even read of an offer to have an “add-on” 32bit H5 licenses installed on users usb-elicensers. from SB (refer to the URL links/posts above)
This is NOT good enough SB, consider:
if I (or any other user) is running a WIN7-64b system with C9 (or C7.5) and using rewire to also drive other software (eg Reason) in a large project consuming significant RAM resources, CPU resources, using specific audio interfaces on our platforms.
How are we to open our older 64bit address space projects, [systems that have 24Gb, 32Gb, 64Gb or more RAM] with all our other software integrated (eg rewire) if all you are offering is ADD-ON band-aid 32bit-HAL5 ?
In fact, the more I think about this, the bigger the problem gets, seeing as for example Propellerhead.Reason is not available in 32bit (since version 8.2), this now breaks down the option and work-flow operation of even being able to open all inter-connected vendor technologies. – why , because SB are revoking the purchasers use of H5 64bit or H4 or H3 (or any versions the user has paid for, in upgrade monies) if they opt to take H6
SB please consider that you are significantly impacting/imploding our ability to operate the workflows that we have built up over a long period of time on WIN or MAC platforms.
These are frameworks that we have invested time in , recorded projects in… where we use and choose what versions, of HALion or Cubase or whatever other software license that we have upgraded to over the course of years.
I for one believe that this is not good enough.
This is not an Up-Grade, it is a H6 Cross-Grade to a mutually exclusive alternate release version that is bound to specific operating system versions that SB as the software vendor are stipulating / mandating onto us.
Consider us users that have paid our way through upgrades.