FWIW, this update has made C8 unusable for me due to lengthy hangs which show up in Resource Manager as Cubase not responding. After installing the update, this is my experience as it happened:
Loaded a template project, added an instrument track, clicked in some midi, right clicked and selected Render In Place (Current Settings). Nothing happens for about 20 seconds then the render starts then it hangs again for another 20 seconds or so and eventually completes.
I repeated the render in place and noticed that it renders the original midi even if it is muted and about 1 in 5 renders where going via the “mystery hang” routine when nothing happened.
Oh well, close that project. Start a new one from scratch so File New/Empty. Added an Instrument Track. The Instrument GUI appeared but I am presented wiht an empty project screen. After about 30 seconds, the instrument track appears in the project window. I retried the render in place test and it was better this time.
So I closed that project to try another but as soon as I clicekd close, it hangs again - 20 or 30 seconds with nothing happening. This is when I loaded Resource Manager to see what is going on - couldn’t tell but it shows Cubase as Not Responding. Is it a thread lock or something like that? (Trying to sound technical here!)
I really want to like Cubase 8 but I can’t. I gave up on it and went back to Cubase 7.5 and am also exploring Bitwig as an atlernative and I keep hoping C8 will get useable with each update but it doesn’t.
So, after installing 8.0.30, I am getting frequent hangs and also there are still problems with windows not being put to front after using dialogs so the mixer or key editor on my right screen keeps getting hidden by explorer or whatever else I have open.
The hangs are the main problem and I wasn’t getting these so frequently (once in a while ) in 8.0.20 so from my PoV, this is an update to use with caution. None of these problems exist in C7.5 or Bitwig or Studio One or Sonar X3.
I don’t appear to have these hanging issues that you are experiencing so it could be installation specific. A start may be to try running Cubase in safe mode to see if the issues persist.
i wonder if its another layer in the copy protection (polling the USB dongle) that $teinberg have added for this update that is causing this lag. Of course they would not tell us about changes to their copy protection code in the update summary. But ive found in many cases the lags and “stalls” that you experience are a result of the copy protection slowing things down.
maybe its causing these render hangs reported, as Cubase rolls through certification code…maybe its causing this Midi jitter as it gets tangled up in the midi areas as well ? would explain why theres nothing else new to the midi editing windows really but we are experiencing this.
i would not be surprised if this was the case. $B may need to rethink if this extra layer of new protection is “worth it” for the hit it seems to be causing to users
I think with 8.0.30, we’re seeing two things factor into what you’ve observed.
First, that build would have had issues gathered from potentially long before its release.
It’s like how the light from a far away galaxy is looking into the past.
Second, I think the windowing issues (one major bug that I reported, related to that, too) sorta crept up on them and became a core thing they had to rework.
Also, the thought that there are probably dependencies between the PC and Mac versions, deep in the code; that they probably have to tweak both even when an issue in one platform is the “offender,” boggles my mind. I’d be surprised (and impressed) if they’ve found a way to be fully insulated from this inherent engineering challenge.
So, Microsoft updates something with a window API and they have to fix it for that new thing, keep it working in older versions of Windows AND not break parts of the code that the Mac version shares.
It’s my feeling that some of the whole mobile revolution that we’re still seeing (OS changes that are good for mobile, only), is trickling down and cause much pain for developers both in Windows and Mac OS.
Yeah, there was a post somewhere (maybe a YouTube video at a tradeshow?) from one of the staff, that made a passing remark to he having a preliminary 8.0.30 internal build.
I swear I’m not imagining it (but we can’t rule that out completely). >
I’m pretty sure it was at least a year ago.
If so (and I’m not crazy), nothing at all unusual about that, just pointing out that a build (or branch) can be cooking on a back burner for a long time in software development.
That is incorrect. The build date is on the about page of the software. Please don’t start rumors.
Now that I’ve been able to give it some more time, I am not getting the midi drag delay that people are reporting but I am getting serious lag when resizing parts in the project window and the behaviour matches that which another user posted a video for.
It is perhaps maginally slower with audio than midi.
The CPU load isn’t doing much so that can’t be making it bad.
And finally for now, I cannot see any improvement in window focus after using dialogs.
If I go into Device Setup for example, when I close the dialog, Cubase jumps to the back and my internet session gets focus!
I have the mixer/editors set to use the right sceen and they keep disappearing behind Explorer windows and others.
One of the biggest pains in C8 is that you have to keep clicking in the task bar to get it back after you do most things that involve a dialog. It’s not fixed folks. Sorry. I can’t tell any difference.
I’m very pleased so far with 8.0.30! I’m not experiencing sluggish performance with MIDI editing as some are reporting.
The biggest improvement is in stability. I am no longer seeing those random red VST spikes! I have one project specifically that would hit red for no reason from 30% to 100%. This no longer happens.
i’m very pleased with 8.0.30 too. I noticed that performance on VSTi heavy 96/24 projects is greatly improved. Out of curiosity i’ve tested projects i remembered i had to be creative with bouncing/freezing stuff … and those all work now without any trickery.
The AISO Guard seems to be finally working as intended!
Performance wise this is the best release since 6.x. Great Job! Don’t touch it!
Seeing as the bug doesn’t happen for everyone, Steinberg can you please advise on how we can help you test the MIDI editor problems – should we be contacting support so they can get our complete specs?
I updated last weekend. All went smooth. Still running C8 on Win10 and no more problems. I did have to rescan my VST’s. It lost where I had them installed on another drive. But after I rescanned the VST Plugin’s all works now.
can anyone point me at the old 8.0.20 update link please? can’t find it anywhere
this update is not working for me at all, either no sound from vst’s or major bitcrushing effect. a lot of GUI issues along. it’s just awful
simply unusable for me.
