Just filled out a new survey. Or, maybe I’m just late for the old one.
1 Like
1:00 p.m. is kind of early to shut down a support phone line. Always wondered about that.
I took the survey. 
Cubase survey???
Well how about an important word regarding ACCESS for THE VISUALLY IMPAIRED and Steinberg so-called “PRO” softwares, like Cubase “PRO” 14 and its predecessors:
Despite SEVERAL YEARS of EMAIL COMMUNICATION with Steinberg, about introducing FULL COLOR CUSTOMIZATION of the Cubase GUI in order to allow VISUALLY IMPAIRED FOLKS to be able to ADJUST the Cubase GUI’S colors and contrast TO THEIR SPECIAL VISION REQUIREMENTS, and also despite emails of me recommending key advice to Steinberg SINCE PROBLEMATIC VISION IS MY DAILY REALITY, well, I have seen ZERO improvements from Steinberg in its so-called “PRO” softwares.
Worst, the last Cubase version (14) has the MOST CONTRASTED GUI COLORS ever, and it FREAKS OUT MY PROBLEMATIC VISION EVEN MORE, and probably the vision of many others with similar vision problems, that like me, rely on GUI FULL COLOR CUSTOMIZATION in order TO WORK.
There is NO WAY for me to work with Cubase 10, 11, 12, 13, and 14 because MY PROBLEMATIC VISION CANNOT TOLERATE these HIGH CONTRASTED GUIs and ITS COLORS that CANNOT be FULLY CUSTOMIZED and FULLY ADJUSTED (unlike other DAWS that cost a fraction of the price of Cubase So-Called PRO” as I recently learned…)
…and Seinberg calls his software Cubase “PRO”, go figure (…)
I have worked with Cubase for WELL OVER A DECADE (versions 6 and 9), I have done many big projects and I have spent lots of time developing my workflow, and changing DAW at this point is as appealing as losing one eye…
Over the years, after all these detailed emails and recommendations I sent to Steinberg about ACCESS FOR THE VISUALLY IMPAIRED, and the lack of FULL COLOR & CONTRAST CUSTOMIZATION in a Steinberg software that boasts the word “PRO” in its name, it is clear to me that:
1- Using the word “PRO” in the name of its software is actually just a MARKETING SPIN as in reality this software does NOT deserve the name PRO if it cannot have the colors and contrast of its GUI adjusted so that VISUALLY IMPAIRED folks can work with the software. A “PRO” software should have such basic GUI customization.
2- Steinberg DOES NOT SEEM TO CARE 1 second for ACCESS FOR THE VISUALLY IMPAIRED in its softwares, especially the ones that boast the name “PRO” (…)
Steinberg probably has WHEEL CHAIR ACCESS in the Steinberg headquarters building since there is probably a law forcing corporations to offer this access to people with mobility impairment.
But if you are VISUALLY IMPAIRED, you’re out of luck as Steinberg won’t accommodate you since the law does not seem to force them to do so, and monetary profit at all cost seems the name of their game…
All my past emails exchanged with Steinberg over the years, prove my claims. It’s all there for ALL EYES to see, even for the eyes of the VISUALLY IMPAIRED.
Will it take a LAW to FORCE software companies to provide a simple FULL COLOR and CONTRAST CUSTOMIZATION for its software GUIs to allow ACCESS TO THE VISUALLY IMPAIRED???
And especially in software boasting the name “PRO” like in Cubase so-called “PRO”???
A software GUI can have a menu to adjust fully its colors and contrast, it’s just a question of programming it.
A VISUALLY IMPAIRED person with VISION REQUIREMENTS DOES NOT HAVE a MENU IN ITS EYES TO ADJUST ITS VISION…
In closing:
A corporation’s SOLE PURPOSE and REASON TO EXIST is MONETARY PROFIT, and sadly often, AT ALL COSTS, especially at the cost of the VISUALLY IMPAIRED in this case with Steinberg, as displayed in its many email replies to me, and total absence of improvements in the full customization of the Cubase “So-Called PRO” GUI of versions 12, 13 and 14, the worst GUI ever for the visually impaired…
Shopping for a long term DAW?
Having increasing vision problems?
Assess your DAW inve$tment wi$ely I $ay…
Ho! Is that the Grim Reaper I see over there, waving its scythe?
(…)
2 Likes
Instead of having to click the tiny square we can now hold down modifier keys (Ctrl + Shift resp. Cmd +Shift) while clicking anywhere on the event. Use Cubase 14.0.20 or higher.
1 Like
For those who recording studio. When doing it with 3 operations, the mouse is still faster than using hotkeys. My friends also deleted Cubase14 after only 1 day of use and went back to using version 12.
It’s worth making a new thread about, so that it’s separate from the survey discussion.
1 Like
Two things that would be great:
-
Folders in the mixer.
-
The ability to set a tiny fade-in every time I start and stop the transport. Pro Tools has it for start, and Reaper has it for start and stop. No more pops every time you hit play.
I don’t mean auto-cross fades when editing, or the (very cool) auto zero crossing setting. I mean a quick fade in of all audio upon starting play.
What Pro Tools can do is fade in (like 0.25ms) when you press start on the transport, even when the start position is in the middles of events, and even if the audio waveform happens not to be at a zero crossing (which would otherwise create a pop the moment you press play.)
The entire audio (playback engine I suppose?) fades in based on a global setting. Pro Tools has this setting in the transport area along with pre-roll and post-roll settings. In Pro Tools I set it for a short fade-in whenever I start playback. And Reaper has this setting for starting and stopping play, which is even better.
1 Like
I will not update until i see way better improvements in the midi-remote sector, ESPECIALLY the midi remote editor. I am not willing to learn Javascript poopies language, just to do basic midi-operations with a midi-controller. It is INSANE to expect that from a user. Plus there is no guarantee that a own written script will work in future versions. We have seen that MULTIPLE times from Cubase 12-14. How you even call that a “feature” ??? Its more pain in the ass, then anything else.
COMPLETE what has been promised regarding “features”. At least make small progress steps, instead of NOTHING in years. Even worse, destroying things/scripts that worked in previous versions. RETHINK concepts that did not work well together. For example, why are midi-remote editor scripts different from own written scripts and cannot practically work together??? This alone is a big fail. So if you have a partially working midi-controller under the midi-remote editor, you cannot just add the missing stuff (displays, LED rings, colours etc.) with a own script. You need to start from scratch with a own written script… INSANELY dumb.
My input is that it does not matter how good the product is if you are no longer supporting it!
Every time i raise an issue I wait for a month only to find out that you close the ticket as resolved (hence lying for your statistics) and ask me to re-open it if the issue still exist. With the last ticket it even happened twice, I have been wating for an answer for two whole months and this is frankly unacceptable !!!
This is the rubbish automatic update after a month of silence, appalling support.
It never used to be like that.
Dear customer,
Please excuse the significant delay in responding to your request and for not having met your expectations.
Is the request still pending? If so, please submit a new ticket and we will do our best to get back to you as soon as possible.
Thank you for your patience and understanding.
You can find the full details of your ticket right here: requests 700716
Best regards,
Steinberg Support Team
Admittingly, this is not where Steinberg shines… at all!
However, have you tried to post your question/issue here in this forum or did you try to reach telephone support?