KVR Audio

ShawnG · Post by **ShawnG** » Sun May 20, 2018 11:46 pm

fmr wrote:
Googly Smythe wrote: I suspect a graphics driver was the problem, but who knows.
Funny you said that. After two days of intense troubleshooting, I think I located the problem. I suspect it is related with the fact that the laptop uses Intel HD Graphics 3000.

This graphics chip is not supported by Intel in Windows 10, according to the informations I gor on the Net: https://communities.intel.com/thread/11 ... 5&tstart=0

The laptop was from my daughter, and I borrowed it to make some presentations. She upgraded from Windows 7 to Windows 10 during the time it was available as a free update, and probably didn't notice the compatibility warnings (assuming there were compatibility warnings).

What is a mystery to me is why I had Cubase working OK until this 1803 Redstone, and after the update, all of a sudden started to crash. Anyway, I reported to Steinberg. They released an update for HALion that solved the problems I had with the GUI (in that same machine). Maybe they will release some update that allows me to work again with Cubase in it. Otherwise, the only solution is to format the hard drive and reinstall Windows 7.

that graphics chip hasn't been supported in any version of windows 10, including the one you were working with quite happily until you upgraded. I would have my doubts as to whether that is the issue. Before you take the step of reverting to an earlier OS, I would personally suggest uninstalling cubase correctly and reinstalling it. If you just install over the top, it will likely not fix any number of file corruptions or registry stuff that might be the issue. over the top install would only fix an issue if it was a file that was missing completely.

EnGee · Post by **EnGee** » Mon May 21, 2018 1:25 am

Also, try checking the BIOS (if there is a new update) and in fact all the hardware drivers in the manufacturer's website.

Topcheese · Post by **Topcheese** » Mon May 21, 2018 5:04 am

I would also look at just rolling back the update.

fmr · Post by **fmr** » Mon May 21, 2018 8:13 am

kb420 wrote:I just updated to 1803 this morning. The ONLY issues I had weren't with Cubase at all. I have a program that adjusts my Fonts that I had to reprogram (A+ System Font Size Changer). I also had to run elicenser twice because something failed the first time. It might have been because I didn't open it with "Run as Administrator".

Cubase started right up with no problem. I can open and close the mixer using F3. All is well.

Thanks for your report. I think I narrowed my problem now, and it is related with the graphics chip, which unfortunately was not updated by Intel for Windows 10 compatibility.

I had problems with the HALion GUI before, but Steinberg managed to solve those with an update. Let's hope they come up with something also for Cubase. Otherwise, I'm locked down regarding Cubase on that machine, unless I downgrade to Windows 7 and start over. I just use it for presentations anyways, and I already migrate anything to REAPER for the task that's coming.

Regarding eLicenser, yes, that's a known issue. Every time Windows has a major upgrade, we need to run ECC as administrator once. After that, everything comes back to normal.

fmr · Post by **fmr** » Mon May 21, 2018 8:19 am

ShawnG wrote:
fmr wrote:
Googly Smythe wrote: I suspect a graphics driver was the problem, but who knows.
Funny you said that. After two days of intense troubleshooting, I think I located the problem. I suspect it is related with the fact that the laptop uses Intel HD Graphics 3000.

This graphics chip is not supported by Intel in Windows 10, according to the informations I gor on the Net: https://communities.intel.com/thread/11 ... 5&tstart=0

The laptop was from my daughter, and I borrowed it to make some presentations. She upgraded from Windows 7 to Windows 10 during the time it was available as a free update, and probably didn't notice the compatibility warnings (assuming there were compatibility warnings).

What is a mystery to me is why I had Cubase working OK until this 1803 Redstone, and after the update, all of a sudden started to crash. Anyway, I reported to Steinberg. They released an update for HALion that solved the problems I had with the GUI (in that same machine). Maybe they will release some update that allows me to work again with Cubase in it. Otherwise, the only solution is to format the hard drive and reinstall Windows 7.
that graphics chip hasn't been supported in any version of windows 10, including the one you were working with quite happily until you upgraded. I would have my doubts as to whether that is the issue. Before you take the step of reverting to an earlier OS, I would personally suggest uninstalling cubase correctly and reinstalling it. If you just install over the top, it will likely not fix any number of file corruptions or registry stuff that might be the issue. over the top install would only fix an issue if it was a file that was missing completely.

I did that too. I uninstalled EVERYTHING I have from Steinberg, cleaned up the system, and reinstalled, starting with Cubase. The result was the same. I then reinstalled everything else. No changes in the behavior. The reason I attribute this to the graphics is because I had problems before with the GUI of HALion 6, and Steinberg specifically addressed hat as related with them, and issued an update that solved the matter. And Cubase lkaunchs OK, up to the point I can see the welcome window, and I can even create a new Empty sequence (opening the Arrange window. It's just when I try to open a mixer, or simply create a track, that Cubase crashes. This is really weird, but can't be related to any corrupted installation, since I uninstalled and reinstalled everything from scratch.

fmr · Post by **fmr** » Mon May 21, 2018 8:21 am

EnGee wrote:Also, try checking the BIOS (if there is a new update) and in fact all the hardware drivers in the manufacturer's website.

I might check that. Didn't occured to me before, since everything else was working fine.

lfm · Post by **lfm** » Mon May 21, 2018 8:27 am

fmr wrote:
EnGee wrote:Also, try checking the BIOS (if there is a new update) and in fact all the hardware drivers in the manufacturer's website.
I might check that. Didn't occured to me before, since everything else was working fine.

Even check for chipset driver updates - manufacturers usually have those as well. So these are separate files on computer and not same as BIOS.

4damind · Post by **4damind** » Mon May 21, 2018 12:35 pm

It seems some people have different problems with the 1803 update (or no problems).

For me Cubase could not find the eLicenser, so I updated to the latest version which solved this problem.
Steinberg audio hardware (UR interfaces) has also a known and confirmed problem since the previous update... this needs a re-installation of the USB driver and the mixer apps.
Anyway, the result is the same: Cubase doesn't start.

fmr · Post by **fmr** » Sun May 27, 2018 9:41 pm

Hey guys. Just to let you know that, after noticing in the last Cubase 9.5 update (9.5.30) a reference to solving a problem that prevents Cubase to start with some Nvidia drivers, I decided to reinstall Cubase 9.5 in my laptop (I was using Cubase 9.0 there) and this update solved the problem. Cubase 9.5 works again in my laptop.

So, I was right, and this was a compatibility problem between Cubase and the graphics. I suspected that because I had experienced problems with HALion too. All is well now, except that I am forced to use my Cubase 9.5 key.

chk071 · Post by **chk071** » Sun May 27, 2018 9:46 pm

4damind wrote: For me Cubase could not find the eLicenser, so I updated to the latest version which solved this problem.

Same here. Executing the eLicenser Control Center with administrative rights, and doing the repair and maintenance stuff fixed it for me though, not updating.

EnGee · Post by **EnGee** » Sun May 27, 2018 9:57 pm

fmr wrote:Hey guys. Just to let you know that, after noticing in the last Cubase 9.5 update (9.5.30) a reference to solving a problem that prevents Cubase to start with some Nvidia drivers, I decided to reinstall Cubase 9.5 in my laptop (I was using Cubase 9.0 there) and this update solved the problem. Cubase 9.5 works again in my laptop.

So, I was right, and this was a compatibility problem between Cubase and the graphics. I suspected that because I had experienced problems with HALion too. All is well now, except that I am forced to use my Cubase 9.5 key.

Good to hear that. Thanks for reporting back

jens · Post by **jens** » Mon May 28, 2018 9:09 am

I'm a bit late to the party, but - without knowing Cubase will or your specific saturation in regards to this -
would I have to make a wild guess, I would say it might be related to secondary screen settings - something roughly along the lines of:

- Cubase was set to put the mixer and what not on a secondary screen if available

- after the update Windows for some reason falsely reported a secondary screen available (perhaps one that had been used before with this laptop but was currently not connected?)

Something like this - Cubase would try to output the mixer window to unavailable hardware and then poof as a result.

fmr · Post by **fmr** » Mon May 28, 2018 5:26 pm

jens wrote:I'm a bit late to the party, but - without knowing Cubase will or your specific saturation in regards to this -
would I have to make a wild guess, I would say it might be related to secondary screen settings - something roughly along the lines of:

- Cubase was set to put the mixer and what not on a secondary screen if available

- after the update Windows for some reason falsely reported a secondary screen available (perhaps one that had been used before with this laptop but was currently not connected?)

Something like this - Cubase would try to output the mixer window to unavailable hardware and then poof as a result.

No, it wasn't anything like that. It was simply a driver incompatibility. I had updated Nvidia drivers (because I was experiencing problems with Waldorf Nave, and Rolf advised me to update the drivers). The update solved the problem with Nave, but I didn't try Cubase after that, because I was using mainly REAPER (the key for Cubase is usually connected to another computer). I thought that the problematic graphics were the Intel because the chip isn«t supported in Windows 10 anymore, and it is the main chip in use (a weird choice - it seems the Nvidia is reserved for the output graphics, not the internal). But after updating Cubase 9.5 to the latest version, Cubase is working OK again, and Steinberg references that this update solved a problem with Nvidia graphics.

On the presentations I am now giving, I decided to use Cubase, so, I took the key and launched Cubase again. It was the first time after updating the driver, and by coincidence, I had just updated Windows to 1803. Cubase opened but was (and version 9 still is) crashing as soon as I try to open a mixer or even if I just try to create a track (which doesn't involve opening anything, actually).

After this last update, version 9.5.30, Cubase returned to normal behavior, and I am able to work OK. Version 9.0.40 however still crashes. Unfortunately, I don't think Steinberg will issue an update for that version, so, I have to use my 9.5 key or update the other one.

Cubase Pro 9 mixer incompatible with Windows 10 1803 (latest)