Cubase 7.06 is out

[Guillermo Navarrete]

Hello TheoM,

I can confirm that this happens on my iMac. It misses a few notes.

The U.S. Steinberg techs told me to make sure ASIO Guard was OFF.

Yeah, I keep it off. I was just trying to help TheoM test.

This article says it should help performance on a Mac. Technically it does, but Cubase lets the other non-ASIO Guard tracks start while the ASIO Guard enabled tracks are still processing.

https://www.steinberg.net/en/support/kn ... and-nuendo

Thanks for confirming. So,e guy drove me nuts over at the forums with the first reply to my topic saying it simply didnt happen and I know it does.. There's no way for it NOT to happen when asio guard on an instrument is enabled. On any system, any OS. Cheers.

Me again, can you reproduce this with any other VSTi that is not from Steinberg, that supports ASIO Guard?
If so, could you please give me the names?
This will help a lot the QA

Best regards,
GN

[fandango]

EDIT - Guillermo's screenshot working now.

[Compyfox]

Here is the screenshot:



Can you guys see the image?

This usage is still unintuive as funk!
Why is it so hard to port at least ONE FR. Which is actually the most requested feature since Steinberg started this mess with the insert handling in the mixing console.

Who in the right mind thought this up? Who was that stoned to think that this is intuitive, fast, and liable? This is a constant disimprovement!


All other hosts can handle this WITHIN the insert slot field. Heck I even showed you how(!) with the FR and a screenshot from Logic. But no, Steinberg is special. So special that they say "forget usability - what we do is excellent!".


The marketing staff should be fired, and the programmers and users shall take control again. But that won't happen anymore.



Sad thing is, to continue getting support, I NEED TO update to 7.06. But I don't think my ASIO issues, my Mackie BabyHUI issues and certain other quirks will be fixed.

Time to take a closer look at Studio One, where I'm not forked over with BS!

[ObsoleteAcc99]

[DELETED]

[zvenx]

My own experience and I haven't read the whole thread to know if we are speaking about the same thing.

Almost every synth that uses samples, whether streamed or not, if asio guard is on and they are enabled to use asio guard, if they are on beat 1 bar 1, they will miss the first note. I have slowly had to disable audioguard on most of my vsti's.

However I have never seen it on vsti's that are are synthesizing their own waveform to produce sounds. like Zebra2, Diva,Dune, Spire and a few others....

and I have had reasons to test this phenomena extensively.

rsp

[ObsoleteAcc99]

[DELETED]

[SODDI]

This has not been fixed, we have it on our bug base (R-10234). But it is quite complex, therefore it will take longer to get fixed.

This is the "new" Steinberg at work. They know of a major bug, they have known about it for months, they even have a code number for that bug, yet they released a bugfix rev that does not include a fix for that bug (and others) because they are "quite complex". Why did they release a bugfix rev that didn't fix the bugs? Because they were scheduled to.

And it is complex - it is a part of a whole cluster of problems associated with Cubase 7's ASIO and driver handling, none of which seem to have been addressed by Cubase 7.06, at least as far as I can tell by the release notes.

But that complexity is why thousands and thousands of people have paid hundreds and hundreds of dollars each to license Cubase. Steinberg is supposed to be able to handle these and other issues. It's not a matter of charity, it's not a matter of doing users a favor as the Steinberg reps would have you think. It is Steinberg's responsibility to make things right, to make Cubase work right. And they have a responsibility to fix them in a timely manner.

Otherwise they are just another (pardon the American colloquialism) shitheel company, and no longer the reputable software developer I have been dealing with for years.

I have been using Cubase for around 20 years now and I consider C7 to be broken out of the box, the worst product I have ever seen from Steinberg.

[zvenx]

I can't believe I am now defending SB in public .. And I too have outstanding bugs (the cleanup bug for one) that I have insulting that they haven't fixed yet.
But from what I understand and it isn't unique to Steinberg, is if a bug is complex and by that *I* mean fixing it can possible create a whole new slew of bugs, which will require much longer testing etc, it will take a little longer to fix....
not that you don't have a right to be impatient.

rsp

[ObsoleteAcc99]

[DELETED]

[SODDI]

They've had nine months and 6 bugfixes.

[lotus2035]

Zeta 3

[zvenx]

Nexus uses samples.. I don't have any of the others in this list sadly:

Oberheim SEM
Zeta 3
Twin II
KHS One
Nexus
Waves Element

rsp

[no_barcode]

Nexus uses samples.. I don't have any of the others in this list sadly:

Oberheim SEM
Zeta 3
Twin II
KHS One
Nexus
Waves Element

rsp

ASIO Guard delay issue Happens to me with ACE.

[zvenx]

I have that, let me try that.


I have two systems.
my pre-production setup which is a macbook pro running Cubase which stays in my bedroom or if I am doing production at another studio or in the days I use to play live.
and my main studio setup which is a PC running Nuendo.....Desktop

I have shut off the studio for the day so all I took a look at was my Cubase macbookpro set up.
I found out why I don't have problems with algorithmic synths..... those that I looked at all had asio guard off, and I don't remember ever turning those off.. they may have been off from Steinberg's default......
Didn't make sense to test them because I figure there must be a reason why steinberg have them defaulted as off.

Did you turn on asio guard on Ace or was it set that way by default from Steinberg?
thanks
rsp

[ObsoleteAcc99]

[DELETED]