^This!
I have to roll back to 14.0.10 b/c this latest ‘update’ now hides the fader level values when I display many tracks (which I always do).
Worse still, SB won’t acknoledge whether this is a bug or feature.
Why are they so damn careless with every update?!?
It conjurs bulls running wild in the proverbial china shop leaving behind mounds of broken glass.
I used to look forward to updates but now they evoke an overwhelming sense of morbid dread.
It’s f-ing exhausting!
Can you post a screenshot so that we know what you mean exactly?
Never mind. You are the same person that described the issue in another topic already.
I get confused easily when people post the same thing in different topics.
You can just increase the width a bit. It will increase the space required about 1 narrow track width per 14 tracks. This is discussed on this thread:
I personally think reverting back to .10 is an extreme reaction, but everyone’s different!
But why was it changed? I can’t think of a single solid reason.
Pure speculation on my part, and predicated on a presumption that it wasn’t change for change’s sake, I have to think it’s an iterative step towards some manner of custom/extended font selection. It very well could be some manner of unwanted artifact stemming from the new “multi-window fader/rack” options in the Project Window MixConsole if they’re re-writing the scaling options for both - one has to assume some manner of common code library between the two. But again, I have no idea.
Right! That’s the correct question to ask.
As usual this ‘upgrade’ didn’t fix any of the numerous bugs that I have to deal with everyday, so I lose absolutely nothing by rolling back (and I’ll gain the latest feature which I’ve lost).
Because of a previous bug that broke the toggle button that enables/disables all plugins, I now have to see all channels to make sure that when I do my 2-channel mix-down that all the plugins are actually enabled. I frequently have to enable some (sometime a lot) manually.
Also, I look to see if all theVIs actually produce sound; sometimes I have to unload and re-load a VI to make it produce an output (that was another bug).
My ‘workflow’ has become a turturous set of ‘work-arounds’ b/c SB is so damn careless when they change their code.
They now introduce new bugs with every release. And they don’t correct most of the old ones, so they just keep accumulating. WTF?!?
Cubase has always been in a state of flux, going back to the Atari days. A lot of changes seem to be for no apparent reason.
But how is this different from any other software?
For example, I use PaintShopPro a lot, and I happen to think that, compared to earlier versions, it’s a whole lot harder to use, especially on first use, all because the devs thought they could “improve” it with their programming shenanigans.
I’m not sure that’s the correct one for WoA. I think someone forgot to put the WoA version up. I wonder if there are any diagnostic logs in the Steinberg Download Assistent?
I think a good feature for the download assistant would be to add a diagnostic log feature just like the Activation Manager has.
I use music software from 200+ different companies and none of them are as careless as SB.
Whenever I do find an issue I contact support and, in most cases am contacted within a few days and provided (at least) an acknowledgment of the issue and sometimes even a temporary solution. Although that consumes my time, in the long-run it’s a good investment.
Most software has bugs, but for SB the combination of 1) creating new bugs with every update, 2) not correcting most existing bugs, 3) wasting time on features that work poorly or were not requested by users, and 4) a long update cycle ensures that Cubase will remain on a downward trajectory.
SB is currently running a “Cubase 14 Feedback Survey”. Well let me save them the time of reading everyone’s responses. SB, the problem is that Cubase is becoming increasingly unusable! Users have been complaining about this for years but little has changed.
So much of my time is now spent taking extra steps to work around broken features. Doing so stifles productivity and creativity.
Viewed from the outside, it seems that the coders at SB don’t fully understand their code. Or maybe the code is so old and/or poorly written that proliferating bugs is the best case scenario. I wonder if it was originally written in something ancient like BASIC with lots of “goto” statements and global variables. That would explain a lot.
There are just normal logs. On the regular x86-Windows they are located here:
%userprofile%\AppData\Local\Steinberg Download Assistant\logs
Now, in the selected folders of media bay, when you press the back arrow, you do not go back one step, but return to the very beginning, where again you need to click the mouse a billion times to get to the same folder.
I’m writing about the media bay that is on the right, in the project window.
You already wrote this one day ago in this topic.
I realized long ago that I have to write to Steinberg several hundred times for him to pay attention to it. It’s not a fact, of course. Everything I write I ask for is usually phrases into space.
The support of the Studio One team is also not very responsive. They all need to learn from the Reaper team.
Steinberg, I’ll tell you what you need to do first.
I’ll tell you one thing.
Just one thing, one really important thing.
No matter how dumb you are, you know that this is more important than anything else.
Focus on fixing as many bugs as possible before adding new features.
And if you want to increase sales in the long run, just show that Cubase is the least buggy Daw.
I really don’t care about “this feature, this feature, this feature,”
.
It has less bugs than any other DAW
Compared to this, the new features are secondary
On my Cubase Artist 14.0.20 the range autodetection is functionalless. If I follow the description to use the range tool, I have no auto detection.I have Win 11. Or is this feature only for Pro?
As much as I can be the first one to moan, there are some exaggerations here, some things did improve massively with some releases.
Overall Cubase is a much better tool today than ever before.
That said, a 20% more effort on reducing bugs and improving workflow and stability in place of the effort developing new tools would work better for us already paying users.
And we do help to promote the software … So fixing bugs is great marketing.
Cheers.
The Track Delay feature remains broken, changing the values via the keyboard is disabled and adjustments in 0.01 values for precise control has not been possilbe for some considerable time now. Makes me angry Steinberg continue to ignore this bug and issue, yet fix other less important things.
The whole inspector, font sizes and control for altering values leaves a lot to be desired.
I have 9.5, 11 and 12, as well as 14 installed. Sometimes I open the earlier ones, but very soon go back to 14, despite the teeny tiny fonts here and there.
And 14 is the most stable, in my experience. YMMV, as always.
