Tired of Steinbergs Upgrade to fix attitude

[chk071]

You know, I feel a bit stupid now, having fallen for the OP's claims without any proof of anything. Should have known better, considering the OP's posting history (of exaggerations and false claims). Will wait for confirmation next time.

[thebutler]

You know, I feel a bit stupid now, having fallen for the OP's claims without any proof of anything. Should have known better, considering the OP's posting history (of exaggerations and false claims). Will wait for confirmation next time.

I should learn from this too

[fese]

So this is what the plugins being 'broken' means - a UI window, 1 pixel out of place..? FFS

You need to read more carefully - it wasn’t just one pixel (you have to move the window at least one pixel to make the displacement go away). At least for the mixer window it was like 3-4mm, and that meant involuntary e.g. bypassing a plugin instead of opening the plugin window despite having the mouse clearly over the right button. It totally f-ed up your muscle memory, especially as it wasn’t consistent behavior because as soon as you moved the window, it was back to normal. Really really annoying, and it took Steinberg nearly a year to implement a fix.
To be fair, it seemed to be one of those problems that only affected some people, not the majority, and it didn’t make Cubase unusable. Still, for those affected it was a serious workflow slowdown.

And i gotta say, my experiences with SB support aren’t exactly positive either. No reply for weeks or even months... you’re usually better off on the forums.

[jancivil]

didn't chime in on the issue, sorry for the offtopic useless rant (it does seem a widespread impression, they don't have the staff for much of support atm) but I'da bet money this was a windows problem I wasn't going to see here. You might see something relatable to an issue on the forum and a workaround or something, but it isn't technical support, and isn't much of a forum IMO. My issue is also an issue limited to some and not all users, or so I have to imagine, which would need a closer understanding than I have, or that most of users have. This one is one of the numerous bugs they abandon during the life of a numbered version. Mine is a somewhat botched feature they may or may not notice, but I gave them a chance to.

[thebutler]

So this is what the plugins being 'broken' means - a UI window, 1 pixel out of place..? FFS

You need to read more carefully

What.? Gimme a break...

The topic started off about Padshop/Retrologue 'no longer working in C10.5'

A further post reveals Windows being '1 pixel out of place' as the actual issue at hand

Your post is the first mention of the mixer window/bypass buttons being involved
Your post is the first mention of 3-4mm of this 'displacement'

[LeVzi]

So this is what the plugins being 'broken' means - a UI window, 1 pixel out of place..? FFS

Cubase 10.5.0 was released Nov 2019; Wikipedia says Windows version 2004 (codename 20H1 or known as May2020 update) was released May 27 2020.

So change of attitude - I don't believe SB 'knowingly' broke anything... how could they.? How could anyone have possibly foreseen, that what was being coded during mid-late 2019, was going to 'cause an issue' in a Windows update that wouldn't exist until 6/7/8 months later..?

1 pixel out of place, = the whole GUI doesn't work until you move it. Everytime you close / reopen the GUI it has to be moved again or it doesnt work.

I'd call that broken.

[LeVzi]

You know, I feel a bit stupid now, having fallen for the OP's claims without any proof of anything. Should have known better, considering the OP's posting history (of exaggerations and false claims). Will wait for confirmation next time.

Exaggerations and false claims ? hush up fanboi, just because I made you cry last time. How does that pill taste, more bitter than normal ?

[fese]

The topic started off about Padshop/Retrologue 'no longer working in C10.5'

A further post reveals Windows being '1 pixel out of place' as the actual issue at hand

It is visible on the left side of the video: the thin white border. When this is present, mouse-clicks are displaced of the same number of pixels making up that border.

To retrieve the correct operation, the window needs to be moved by at least one pixel. Another option is to roll back to Windows 1909.

Again, nowhere does it say that it is a "1 pixel out of place", it is about a "thin white border" and the respective displacement. "thin" doesn't equal 1 pixel, and from my experience with the mixer window (technically the same problem) that "thin" displacement could lead to very annoying behaviour with misplaced clicks.
So yes, you didn't read correctly or misunderstood.
I agree though that "not working any more in C10.5" is also not really correct. I thought that they stopped producing sound or permanently crashing upon reading the title. Having to move the plugin window every time you open it is annoying, and SB should fix that, but it is hardly "not working any more".

[chk071]

You know, I feel a bit stupid now, having fallen for the OP's claims without any proof of anything. Should have known better, considering the OP's posting history (of exaggerations and false claims). Will wait for confirmation next time.

Exaggerations and false claims ? hush up fanboi, just because I made you cry last time.

Not quite. It's rather that everything I read from you is utter bullcrap. Just like this thing right here.

[fese]

BTW, I have 10.5.30 and both Padshop's and Retrologue's GUI work fine, no white line. I cannot say whether I had that problem in 10.5.20 as I never use them, but I definitely had the "white line" problem with the mixer windows and others. Maybe it is a different problem that affects systems differently and hasn't been solved with 10.5.30.
Still, the answer from the SB support is uncool, just pointing to a paid update as a solution is just lame. At least they should offer a generous upgrade discount for the people affected.

[fese]

Maybe this can help:
https://www.blueingreen-recordings.de/C ... BorderFIX/

[thebutler]

So yes, you didn't read correctly or misunderstood.

OK, my apologies - I did misread/misunderstand

[fmr]

I think they mean Windows 10 20H2, which is the current version. There was a version 1909 which was pretty stable. Then MS introduced some changes, notably in the GUI, which may have caused the issues you are experiencing.

No, I suspect the original reference they made was correct.

According to Wikipedia, Win10 20H2 was released Oct 20th 2020, which would be far too late to get any 'fix' for breakages it caused, included in time for the Cubase 11 release - which was only around 3 weeks later, Nov 11 2020.

Windows 20H2 was in Beta, and available to Insiders long before that.

Windows was launched in 2015. How could they be talking about a Windows version from 2004? I'm not sure that even Windows 7 did already exist in in 2004.

[jancivil]

that's the name of the build, 2004

[LeVzi]

Maybe this can help:
https://www.blueingreen-recordings.de/C ... BorderFIX/

I'll definitely give this a go, thanks, and it's a problem they know of, they blame windows , but it's their software that is broken, not a 3rd party dev's VST. But I have to upgrade to V11 to get the fix.

And their support is awful, took 6 weeks to get that reply.