Produktion steht danke dieses Fehlers bei CUBASE Pro 14 System Build: 14.0.41
Es wäre sehr EFFEKTIV eine Lösung für dieses Problem schnellst möglich darzustellen.
Workaround
what ever
Menschlich: es NERVT extrem wenn man nicht arbeiten kann und solche Fehler nicht einfach zu korrigieren sind
KURZ
Ich bitte die Entwickler und oder Programmierer eine schnellst mögliche Lösung zu finden (wahrscheinlich für einige User)
Zum verschrotten wäre das Produkt zu teuer (ES ist frustrierend!!! Wohl verständlich dass ich ungehalten bin)
Danke für Eure schnelle Hilfe
Wie gesagt: Produktion STEHT und wartet auf Service Techniker
Wäre schade, wenn man anderen Musikern abraten müsste das Produkt zu kaufen (würden mehr Leute über EXTREME! Fehler berichten)
dennoch freundliche Grüße
Matt
Production is at a standstill due to this error in CUBASE Pro 14 System Build: 14.0.41
It would be very EFFECTIVE to find a solution to this problem as quickly as possible.
Workaround
Whatever
Humanly speaking: it is extremely ANNOYING when you cannot work and such errors are not easy to correct.
IN SHORT
I ask the developers and/or programmers to find a solution as quickly as possible (probably for some users).
The product is too expensive to scrap (IT’S FRUSTRATING!!! Understandably, I am upset).
Thank you for your quick help.
As I said: Production is at a STANDSTILL and waiting for a service technician.
It would be a shame if we had to advise other musicians not to buy the product (if more people reported EXTREME! errors).
This error usually points to a missing image, font, or theme file that Cubase needs to draw its interface, and a fresh download/installation usually resolves it.
First, try switching to a different default theme and then back to your preferred one. This can force the GUI to reload resources and may solve the issue.
Second, select your Cubase installation in the Steinberg Download Assistant, click “Installation” to download the latest version and re-install it to update potentially missing or corrupt files.
As a first step I would uninstall Cubase. Afterwards install it anew.
Cubase uses a couple of skin files. They have the suffix .srf (Steinberg Resource File) and are located in the Cubase program folder.
Usually people are missing the file that is responsible for the plugin GUIs, but that would not produce an error message.
In the first post, a user mentions that they were able to fix the problem by repairing a Windows system file. Unfortunately, they were unable to name the file, but it could be the Microsoft Visual C++ 2015-2022 Redistributable (x64).
Apart from that, it would be advisable to open a Steinberg Support Request (in MySteinberg) regarding this issue, if you haven’t already done so.
Regarding my post yesterday. I found the other file (skin) in a different folder in Cubase 15 (15.0.6) LE.
In this context, I noticed that this 15 version was updated on the same day. This Cubase 15 LE also works with VST PlugIn Manager!!! Just as it should.
So now I’m wondering if these versions are incompatible? Everything is stored in different folders.
Production has come to a standstill. I’ll write to Steinberg right away.
And I’m considering running everything on my full license of Ableton Live (oh no, I don’t want that).
I wanted to let you know this because I know what it’s like when a post stops in the middle and there’s no solution to read!
I’ll also let you know the solution IF there is one.
Do you have two installations of Cubase 15 on one machine?
If yes it does not make sense, because the executables for the different releases are completely identical. It is just the license that decides what release to start.
I have several versions on my computer because they came with the hardware as a bonus. I let others use the simple versions on my computer who don’t need the PRO 14 version.
CUBASE 14 PRO is the version I use for productions.
Cubase LE 15 is simply on the computer for other people’s simple projects.
I can also see Cubase LE 13 in the Download Assistant.
NO version needs an update.
I already thought that it wouldn’t have any influence. Unless one driver outsmarts the other (from different versions / is replaced by…), then I can only imagine that it could have an effect.
The .srf files from C14 and C15 differ significantly from each other for the most part. Therefore, using files from a different version may lead to malfunctions. In this case, a new installation would be the better alternative.
… I thought so too, but it was worth a try. And for whatever reason, it worked… I’m speechless.
The folder for Skin was empty in the FULL VERSION of Cubase 14 PRO. For whatever reason.
I already tried reinstalling it using the Steinberg Download Manager. It can’t always be that you have to win in the end with something like this. Maybe it’s a brute force method.
For example, I’ve NEVER had to renew a Windows installation. Which others seem to do on a daily basis. (exaggerated)
I reported it to support. This isn’t the first time this problem has occurred. My computer is very well maintained.
The UPDATE to version 14.0.41 also arrived recently.
Everything works fine in Cubase 15 LE. But I don’t use that myself.
I’ve also had files disappear on their own, so to speak - at least, that’s how it seemed to me. But like you, I’m fortunately well organized and can quickly remedy such an unusual situation, because I create regular backups of all my data carriers. Since the Cubase folder in Program Files\Steinberg can simply be replaced with the backed-up version, the time required is manageable.
For my case - I solved this by complete preset removal and reinstall of 15.0.6. Not really PRO friendly, but it works for me as I have presets saved too. Like everywhere.
I am afraid to symlink settings to cloud storage centrally, since if something breaks all things break during migration. Steinberg should seriously consider graceful settings migration feature.
In my experience, restoring one of the folders you mentioned from a backup you created yourself works without any problems. Alternatively, you can of course perform a new installation (for the program itself).
I also think that Steinberg should invest more in Cubase’s error tolerance and self-healing capabilities. Currently (and for 30+ years), this has been left almost entirely to the users and their skills. I can certainly understand the outrage and criticism surrounding this policy.
Five (5!) days without support (directly from Steinberg) even reading my request for help. Nothing. No response.
Why do TV programs always focus on companies that don’t care? Perhaps something like this would also be interesting for affected musicians and studios. How many problems do the individual programs cause? How good is the service?
The FUTURE will be: service comes before sales. Or: people will only buy from places that provide service.
I am very disappointed with Steinberg.
There were at least a few suggestions here in the forum.
You’re left alone with your problems with the programs after you’ve paid for them. It’s like buying a car, the engine breaks down, and the possible response is: “What kind of car do you drive? It just happens that it’s defective. Don’t bother us.”
Large programs such as CUBASE etc. should have a function that checks whether all functions are working or even still available.
Unfortunately, I fear this will NOT happen at Steinberg.
I appreciate your distinction between us, the contributors to this forum, and the Steinberg Support Services staff. Furthermore (see previous post), I agree with you regarding the necessity of self-analysis and -troubleshooting of modern software, especially since the company’s support leaves much to be desired. Shifting this responsibility to the end user or user forums is unacceptable in my opinion. Perhaps freeware programmers can afford to do that, but not vendors with professional aspirations who sell their products at high prices.
Simply reinstalling via the Steinberg Download Manager will NOT make any difference.
A little side note: back in the days of Windows 95b, people always said that everything had to be reinstalled, and some people certainly reinstalled Win95 100 times. My system also didn’t run properly at one point, and I always got it running 100% using normal means
This mentality should be outdated in state-of-the-art programs. Components can be replaced in a modular fashion. Could be –
but of course I see the difference between the forum, where people make an effort, and Steinberg’s NO service
“We don’t give a damn” and the people who sit at the machine and work with it themselves and have had problems from time to time.
The “little programmers” are probably committed to their own egos and would immediately tackle the problem. I have already supported some small programmers with a small donation when I used their programs. That should be a matter of course.
Maybe I should go back to the ATARI version (pure MIDI). BUT then there’s also the storm of indignation on TV about the company. I already have experience with that. Most companies are reasonable before the storm is necessary. It works out well for companies 95% of the time. 4% end up on public TV or are dealt with elsewhere. All of this is, of course, cleanly and properly researched, it goes without saying.
