Steinberg HALion 6 & HALion Sonic 3

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic

Post

Compyfox wrote:
aMUSEd wrote:It's the fact that there was no warning of this change in licensing that is most annoying, had I known it would nuke Hypersonic I would have held back from jumping on it straight away.

I have suggested that they compensate Hypersonic users by opening up the addons as well.
I hope you do believe in miracles... :scared:
No need for miracles. If you open a second instance, of Hypersonic 2, all expansions already unlock. IE The first instance retains limitations. Any instance, beyond the first, opens everything. It's a well known "feature" which has been there since Hypersonic 2 was launched, afair.

The HALion 5 replacement license has been confirmed to activate Hypersonic 2. But I have no idea if the replacement license manages to carry over this "bug". It should, but it's something someone with the new license would have to confirm through testing..

The other thing, to be very aware of, is the soft-elicenser option is only available with brand new HALion 6 purchases. That is, if you already have a HALion license, it must remain on the dongle.

There's currently no way to transfer HALion 6 from a dongle to soft-elicense. So, if you buy the full HALion 6 and want to continue to use the soft-elicense option, you can't let it anywhere near a dongle. If you transfer from your soft elicense, to the dongle, your license will be permanently locked into using dongles.

Post

EvilDragon wrote:W10 is honestly better and faster than W7 ever was. 10 seconds for start menu? It's instant here. Not to mention a lot of other things you mention simply aren't true, or were perhaps true in the very first W10 release - everything is smooth sailing for over half a year here. Anniversary Edition runs great.
Please bear in mind that your own experiences are not universal, especially when replying in threads where the software's own vendor has previously warned that Windows 10 can cause performance decreases.

Again, Windows 10 may cause performance decreases according to Steinberg's own testing. Personal experiences may vary, though my own experiences broadly align with those of Steinberg.

There's numerous issues regarding Windows 10, and its removal of user control, which aren't helpful to DAW users. Whatever, audio users should choose their OS based on its performance with their chosen host software. Since around Cubase 8 time, IMO Steinberg users are now being better served on the Mac OS side of things, or Windows 7 if you plan to stick with Windows..
Last edited by PAK on Mon Feb 20, 2017 4:16 pm, edited 1 time in total.

Post

What's funny, about the whole Windows support situation, is HALion 6 apparently runs just fine on Windows 7. But some Windows 10 users are reporting graphical corruption issues inside HALion 6 on their Windows 10 machine ;)

A lack of Windows 7 support was never about technical limitations to HALion, and reversing the decision confirms that. It was likely Steinberg's attempt to send an early signal about dropping Windows 7 in the next Cubase / Nuendo release.

I have -some- sympathy for Steinberg's position. Microsoft sells Windows 10 users on how its telemetry (spyware) and rapid update cycles mean they can now identify and fix problems faster than ever. The bit MS always forget to add is that some of these problems are created as a direct result of the speed of those updates, which present more challenges versus the old release cycle, which was a major OS release every few years. Stability takes a back seat when your main concern is that you may not even be relevant, in the consumer space, within a few years..

On top of the Windows 10 difficulties, Microsoft's "aggressive" new approach might see a Windows 7 update which "accidently" breaks something major at any time. Or they could make Windows 10 changes which present greater challenges for Windows 7 support. In these circumstances it's entirely understandable why Steinberg seek to limit the headaches MS may cause them, just as it's understandable that a significant portion of Steinberg users will continue to avoid Windows 10..

Post

Yes, Pak, I agree.

I use Win7 Pro and do not want to upgrade under any condition. I hope Steinberg (and other companies) start to take Linux seriously, and if they don't, I stay with what I have. Much good music has been created with soft that could not do half of what we can today. It's not necessary to have 'the latest and the greatest'.

I *may* get Halion later this year, but there is no hurry.
Windows 7, Cubase 9.5 and some extra plug-ins | Takamine EN-10C and PRS Mira

Post

PAK wrote:What's funny, about the whole Windows support situation, is HALion 6 apparently runs just fine on Windows 7. But some Windows 10 users are reporting graphical corruption issues inside HALion 6 on their Windows 10 machine ;)

A lack of Windows 7 support was never about technical limitations to HALion, and reversing the decision confirms that. It was likely Steinberg's attempt to send an early signal about dropping Windows 7 in the next Cubase / Nuendo release.

I have -some- sympathy for Steinberg's position. Microsoft sells Windows 10 users on how its telemetry (spyware) and rapid update cycles mean they can now identify and fix problems faster than ever. The bit MS always forget to add is that some of these problems are created as a direct result of the speed of those updates, which present more challenges versus the old release cycle, which was a major OS release every few years. Stability takes a back seat when your main concern is that you may not even be relevant, in the consumer space, within a few years..

On top of the Windows 10 difficulties, Microsoft's "aggressive" new approach might see a Windows 7 update which "accidently" breaks something major at any time. Or they could make Windows 10 changes which present greater challenges for Windows 7 support. In these circumstances it's entirely understandable why Steinberg seek to limit the headaches MS may cause them, just as it's understandable that a significant portion of Steinberg users will continue to avoid Windows 10..
All sensible views.

What MS probably overlook is that each software product, like a daw, use hundreds of other 3rd party software, plugins, which may all be affected in one way or another when to work together often in a single process - in realtime like for audio.

MS most likely have the average company worker, with some office tools, in mind. The much larger userbase.

Haven't seen settings for updates on W10, but a much more categorized level of updates are needed compared to what I saw so far - important and optional. That you can leave things alone most likely to cause problems - at least till you know you have time to address certain issues that arise.

I would like to see at least bugfixes as one checkbox, maybe in more categories too.
Things that might affect things on drivers level for audio and video separated as well.
Fully customized that you really can avoid things that may disrupt you day.

My daw is online only for installation of updates for tools that I use. Otherwise network stuff may interfer with realtime audio. Numerous times I felt computer was a bit slow in response - to only 10 minutes later get an flash dialog - "a new update for Adobe Reader is ready" - I forgot to turn off updates after every update that turn it on again.

I could not make Security Essentials to rest checking for updates of virus database or whatever it does. I don't use anti-virus at all anyway. So I had to uninstall MSSE.

I invested in a backup tool - and when I was about to turn off machine and call it a day - it refused to shut down saying something "Windows cannot shut down - Acronis True Image is not finished". Nothing scheduled or anything, probably this cloud stuff that all are going for nowadays. I had to uninstall that too.

It's a constant struggle to have the machine doing only what I want it to. Probably a dozen services that try to check for various updates - despite removing everything from autostart.

Booting computer and logging in - it chews disc for at least 15-20 minutes before going silent. I don't know what is going on.

Post

chk071 wrote:
lfm wrote: I did not read about updates for windows vista screwed system up for software already installed like I read about - almost daily - for w10.
Funny that it doesn't screw up software i have installed here on a daily base... you are aware that that only affects software, which is old, and isn't compatible with the new Windows 10 updates anymore? E.g., it said i can't start my CCleaner Portable, so i had to update it to a newer version. Done that, and it works again now. Big deal. :shrug: Actually, it's amazing they even have some kind of database now, with software which isn't compatible with newer updates. In past Windows version, the software just didn't work, and you wouldn't know why, until you updated, and found out that it was the old version which f***ed up.

Not sure if you even mean that though.
I think the latest was Cakewalks older plugins the other day - and probably as you say not compatible with windows 10 - suddenly????

I mean - what is so special about windows 10 to screw up what is there and worked a week ago?????
This is where userbase is screwed in my view.

Windows 10 made itself incompatible !!!!! - that is the worrying part

It's my computer - I think??? - and MS feel like doing anything to it.

I read remarks on Adobe forum that people suddenly could not start Premiere - after a windows update.
General solution going there all past fall was to revert Nvidia drivers to an earlier version.

Later in december Nvidia updated drivers to again be compatible.

It's Windows updates that makes Windows 10 incompatible what is there.
I never saw that - not once before Windows 10 came about.

Post

PAK wrote:The other thing, to be very aware of, is the soft-elicenser option is only available with brand new HALion 6 purchases. That is, if you already have a HALion license, it must remain on the dongle.
Wait, just to get things clear. The "license overwrite bug" really only happens with the Soft eLicenser (HDD) and not the USB key? What have we been discussing about then?


PAK wrote:There's currently no way to transfer HALion 6 from a dongle to soft-elicense. So, if you buy the full HALion 6 and want to continue to use the soft-elicense option, you can't let it anywhere near a dongle. If you transfer from your soft elicense, to the dongle, your license will be permanently locked into using dongles.
There never was a "move back to" route. Once you moved your license to the USB key, it stays there. And I actually find that a good thing. But then again, that's just me.


lfm wrote:It's Windows updates that makes Windows 10 incompatible what is there.
I never saw that - not once before Windows 10 came about.
Wow... without words. So Microsoft DOES go the Apple route from now on.

I see a lot of fun coming up in the future, where maintenance update corrupt formerly working plugins and instruments. :dog:
Last edited by Compyfox on Mon Feb 20, 2017 6:21 pm, edited 1 time in total.
[ Mix Challenge ] | [ Studio Page / Twitter ] | [ KVRmarks (see: metering tools) ]

Post

Has anyone purchased this through the crossgrade? If so, how exactly does it work? Do you purchase first and then send proof of purchase of other product or do you have to send proof of purchase first. I'm at the buy now screen but there are no real instructions concerning this purchase option. It just says "must meet eligibility" or something like that.

So how exactly does the purchase process work and what products are eligible?

Post

Compyfox wrote:
PAK wrote:The other thing, to be very aware of, is the soft-elicenser option is only available with brand new HALion 6 purchases. That is, if you already have a HALion license, it must remain on the dongle.
Wait, just to get things clear. The "license overwrite bug" really only happens with the Soft eLicenser (HDD) and not the USB key?
No that's not correct.

Post

I keep checking this thread to see if anyone is talking about the actual features and improvements.... :hihi:

Post

Compyfox wrote:Wait, just to get things clear. The "license overwrite bug" really only happens with the Soft eLicenser (HDD) and not the USB key? What have we been discussing about then?
No. I didn't say anything like that, and literally have no idea what you're talking about, or how what I wrote could give that impression :)

Post

Echoes in the Attic wrote:I keep checking this thread to see if anyone is talking about the actual features and improvements.... :hihi:
Now that Win7 users know they can use the product you will probably see more. Once SB gets the license situation figured out the whole thread will probably turn to what it should have been had the rollout been more typical.
For streaming and free music downloads visit http://kennethrobertsmusic.com/

Post

aMUSEd wrote:
Compyfox wrote:
PAK wrote:The other thing, to be very aware of, is the soft-elicenser option is only available with brand new HALion 6 purchases. That is, if you already have a HALion license, it must remain on the dongle.
Wait, just to get things clear. The "license overwrite bug" really only happens with the Soft eLicenser (HDD) and not the USB key?
No that's not correct.
So the "previous license nuke" bug happens no matter what? Yet Steinberg pulled something out of thin air that it has something to do with the "HDD eLicenser"?!

Now I'm completely confused.

Echoes in the Attic wrote:I keep checking this thread to see if anyone is talking about the actual features and improvements.... :hihi:
And I keep checking the thread to get an answer to "what is specifically missing in Windows 7". So far no answer either. :hihi:
[ Mix Challenge ] | [ Studio Page / Twitter ] | [ KVRmarks (see: metering tools) ]

Post

Anyone know if you can change the default patch of Halion 6 upon load?
INTERFACE: RME ADI-2/4 Pro/Antelope Orion Studio Synergy Core/BAE 1073 MPF Dual/Heritage Audio Successor+SYMPH EQ
SYNTHS: Arturia Polybrute 12/Roland Jupiter X + Juno X/Yamaha Montage M/Yamaha KX88/Softsynths + Samplers
PEDALS: Chase Bliss Mood MK II

Post

I was just using the auto threshold function to capture an ES-335. I was able to use the layer assignment option for velocity layers. It works great with the next key function. It's really fast workflow for chromatic capture. I would like a threshold on the trim function though. Also, the naming system needs some additional parameters that make more sense than the $Index. But all in all, pretty nifty.
Last edited by SJ_Digriz on Mon Feb 20, 2017 7:31 pm, edited 1 time in total.
If you have to ask, you can't afford the answer

Post Reply

Return to “Instruments”