Wait, people use Halion? I thought we’d all dropped it YEARS ago for Kontakt after Steinberg seemed to let it die with the horror show that was Halion 3.
Well, Kontakt is great for its third party libraries, but Halion 5 is another kind of beast now, much more focused (and easier) to create your own sounds than Kontakt IMHO.
Well … they try to sell us the ‘different team’ story, with every new product …
How many teams do they have ? 10 … 15 … ?
I do not buy it.
At least there must be overlaps … and thus, slow downs.
What does the Halion team do, after 3 month coding ?
9 month holiday on the Bahamas ??
And yes, Wavelab is in fact done by a different team ( ok, 1 person ).
Guess, that’s it …
Releasing a new sampler when you flagship DAW is in shambles is IMHO not a smart choice, even if the resources allocated for Halion had no impact whatsoever in Cubase, because that simply sends out a bad message: “hey guys, here’s my shiny new sampler and it is full of cool features and stuff, but hey, nevermind the fact that the host were you’ll be using it is broken”.
Instead of using the Q-Link button, you can press [Shift]-[Alt]/[Option] to temporarily
link channels. In that case, the link is only active as long as you press the keys
Strange, but I found the ONLY after you re-select the given plug(s), it will “let” you enable/disable/multi-select.
Is it because they have changed something ? dunno I think it IS because the mix console is constantly changing… this was NOT part of 7.0 to 7.04.
Also. I am almost 100% sure that loop browser/media-bay is the cause of decreased performance. I have found today that with a given project (DAW Bench) it gave me some result (which was really satisfactory).
BUT
Upon scanning tons of loops and on-shots… the performance decreased, roughly 7-10% less.
As Weasel correctly wrote, those are different teams - HALion is not being developed at the expense of Cubase.
About fixing:
Cubase 7 is not broken. But we are indeed aware that some of you are having problems and are interested in knowing why and find out what can be improved and made more reliable on as many machines as possible or help the users with solving the problem, where local.
As Support, we are committed to this, and some cases have been carried on for weeks.
Cubase 7 is working fine on most machines and we found the performance being pretty much the same of Cubase 6.5 (even better on some Windows 8 machines). Therefore, it is important that those having performance or crashes contact Support, as your issues cannot be solved by checking on a trouble-free setup and developers cannot fix what isn’t reproducible on our side.
We will look into the system, examine crash logs, study the configuration, talk to the users, do remote sessions and collaborate with Development to spot system specific issues wherever necessary. Support does this on a case-by-case basis.
Some of those who are complaining have not contacted Support – for example, I offered to contact us in order to help those receiving the “Video Engine” error in that very thread, but have been contacted only by one user.
This is not going to help the users and slows down Steinberg in its effort to constantly improve.
We are collecting data to see on which systems Cubase 7 is not working 100%, so if you contacted support and didn’t receive an answer yet, please send me a PM and I will add your reports to the collected ones.