CUBASE 5 UPDATES INSTALL
If you try an upgrade within windows rather than a clean install from scratch, just backup everything in Acronis to be safe. By doing a clean install, it’s easy to grab the latest version of each plugin. I’d say that is more likely due to some plugins needing newer versions to function properly in Windows 10. I upgraded a system from Window 7 to Windows 10 a few years ago with no problems with Cubase but Steinberg suggest a clean install. If upgrading to Windows 10, I’d personally suggest using an image/backup/system clone software like Acronis to clone your system before upgrading to Windows 10 in case it doesn’t go smoothly. I feel like there should be a more obvious warning as not everyone is going to read the fine print. After checking, I noticed that it’s only in extremely small text under system requirements when you go to buy the update.
CUBASE 5 UPDATES UPDATE
I didn’t see this warning when purchasing the update but I know about this from the discussions on the Cubase forums prior to release. Whether that means it will or won’t work on other versions of 64bit Windows, I don’t know but it’s likely to be buggy so upgrading to Windows 10 is highly recommended.
CUBASE 5 UPDATES 64 BIT
Not only that, it requires the 64 bit version of Windows 10. This is the first time Cubase has required Windows 10. Yes I was clicking it! Warning: Not Officially Supported on Older Versions of Windows Anymore.Ĭubase 10.5 is not officially supported on older Windows OSes other than Windows 10. Activate Project button sometimes doesn’t work now…īug 5 The activate project window button just refused to activate on a project no matter how many times I clicked on it to activate. This could be a pain for wanting to import only mixer settings from a large orchestral project as it would un-necessarily take a long time.īut that’s not all, Bug 4 The Import Tracks from Projects feature when importing many tracks at once crashed Cubase 10.5 even when importing mixer settings from a previous version of the same project which contains the same plugins. For now, avoid using this feature on any track(s) that have Automation until they fix it.Īlso, forcing the Instrument tracks to reload seems like a waste of time if you only want to bring the mixer settings over as you can’t separate the two. Completely wipe it! Unlike when using Save and Load Selected Mixer Channel from by physically opening the new projected and manually saving the channel setting and manually loading it back in. If you try to import the mixer settings from one project to another, if you select not to bring the Automation over from the project, it will still wipe the Automation on the track in your project. You can watch the Import Tracks/Settings from projects flaw here. The new Import Tracks from Projects feature unfortunately has a major flaw. I was pleased to see my Steinberg forum feature request appear in Cubase 10.5 as one of the new features! So you can thank me for the idea… but unfortunately, it has a major flaw and some stability issues that need to be ironed out. Thirdly, Bug 3 I was hoping this one would work properly.
Secondly, Bug 2 Jbridge does not work in Cubase 10.5 on Windows 10 unless you run Cubase in administrator mode Import Tracks from Projects, Automation bug and unknown crash bug/stability issue… Jbridge needs a tweak in Cubase 10.5 to work again. I almost can’t make a new Dark Theme as it does not allow me to select as Dark Shades of Grey anymore ? The second issue (easy fix). It is not working after the Cubase 10.5 Update and causes the transparency issue. Whatever you do, DO NOT use my Cubase 10 dark theme in 10.5.
It doesn’t seem to offer as the same color customization as version 10.
CUBASE 5 UPDATES HOW TO
How to fix it for now is explained in my video. Colors/preferences are messed up.įirstly, Bug 1 Something weird has happened with the colors that causes preferences saved in Cubase 10 that use custom colors for events in the Arrangement window to not work and default to transparent! This makes all the events vanish. Issues with the new Cubase 10.5 Update (on release day) The first issue/bug in Cubase 10.5.