Tired of Steinbergs Upgrade to fix attitude
-
- KVRAF
- 35679 posts since 11 Apr, 2010 from Germany
I still wonder if this is a general problem. Maybe someone with the latest version wants to install 10.5 parallely to check?
Thinking about it, I really can't imagine this being a general issue. Where's the shitstorm?
Thinking about it, I really can't imagine this being a general issue. Where's the shitstorm?
- Banned
- 954 posts since 3 Apr, 2018
Steinberg support was always excellent for me.
Instant reply to my issues (hardly any over 20 years).
Instant reply to my issues (hardly any over 20 years).
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
I had an absolute show-stopper of an issue not long ago. I got nothing from Steinberg support except acknowledgement of the support ticket. They were nice enough to send a second email, of equally zero use.
The issue more or less quit on its own, but I saw it today for a second. "Ramp curve is not supported for tracks with MIDI channel All". I wasn't in a MIDI track at all when I saw it, I was in the project window. I might have brushed against a MIDI track, not sure. I wasn't editing MIDI in any way at that moment. But at the time I couldn't touch any part of a Cubase project without seeing it.
Their forum is abysmal, too.
The issue more or less quit on its own, but I saw it today for a second. "Ramp curve is not supported for tracks with MIDI channel All". I wasn't in a MIDI track at all when I saw it, I was in the project window. I might have brushed against a MIDI track, not sure. I wasn't editing MIDI in any way at that moment. But at the time I couldn't touch any part of a Cubase project without seeing it.
Their forum is abysmal, too.
-
- KVRAF
- 9146 posts since 7 Oct, 2005
The best support I had from a DAW software is from Bitwig. They are fast and friendly. I also have good experience with Ableton and Presonus.
However, Bitwig support is the best for me. I heard that Apple has excellent support, so how is Logic's support? I'm thinking of it because if Apple continue designing such great chips, I would definitely buy an M2 or MX Mac in two years or so!
However, Bitwig support is the best for me. I heard that Apple has excellent support, so how is Logic's support? I'm thinking of it because if Apple continue designing such great chips, I would definitely buy an M2 or MX Mac in two years or so!
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
this was the first actual support for the workings of the product I've needed I think ever. I've had broken dongles, and dumbass installation issues in the beginning. I had someone by email after pretty much everybody had left getting me a license to cover my ass on a broken dongle at like 5PM, no one was picking up a phone by then.
I've never kvetched about teh bloat. But I haven't had stability SNAFUs like this in many years, and that leaves alone the weird feature breakage of the last two updates. Stability over new features, and I don't personally consider deleting a note bar by double-click much of a feature.
I've never kvetched about teh bloat. But I haven't had stability SNAFUs like this in many years, and that leaves alone the weird feature breakage of the last two updates. Stability over new features, and I don't personally consider deleting a note bar by double-click much of a feature.
-
- KVRAF
- 5444 posts since 15 Feb, 2020
Apple have great HW support, always had a positive outcome. For SW? Wouldn't even know where to begin to actually get any.EnGee wrote: Sat May 22, 2021 1:27 am The best support I had from a DAW software is from Bitwig. They are fast and friendly. I also have good experience with Ableton and Presonus.
However, Bitwig support is the best for me. I heard that Apple has excellent support, so how is Logic's support? I'm thinking of it because if Apple continue designing such great chips, I would definitely buy an M2 or MX Mac in two years or so!
I lost my heart in Cap de Creus
-
- KVRAF
- 9146 posts since 7 Oct, 2005
Support is very important and there is no excuse IMO for a bad support. But it seems, the music industry has really bad support in general (compared to other professional fields) especially from the big companies unless maybe if you are a "VIP" customer or a known studio!
For individuals (like KVR users for example), I believe that small companies has a better support and a friendlier one. Although, Ableton used to have really a very good support, but somehow I feel it now not as great as in the past few years.
Anyway, the best is to search in the net first. This solves 99% of my problems. If I can't find it in the net, then possibly the support can't help me
For individuals (like KVR users for example), I believe that small companies has a better support and a friendlier one. Although, Ableton used to have really a very good support, but somehow I feel it now not as great as in the past few years.
Anyway, the best is to search in the net first. This solves 99% of my problems. If I can't find it in the net, then possibly the support can't help me
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- 9146 posts since 7 Oct, 2005
Oh! That's not encouragingrevvy wrote: Sat May 22, 2021 2:09 amApple have great HW support, always had a positive outcome. For SW? Wouldn't even know where to begin to actually get any.EnGee wrote: Sat May 22, 2021 1:27 am The best support I had from a DAW software is from Bitwig. They are fast and friendly. I also have good experience with Ableton and Presonus.
However, Bitwig support is the best for me. I heard that Apple has excellent support, so how is Logic's support? I'm thinking of it because if Apple continue designing such great chips, I would definitely buy an M2 or MX Mac in two years or so!
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
- Banned
- Topic Starter
- 4491 posts since 8 Jul, 2008 from UK
The email was lost but the support is in mysteinberg help and reads thus :
Dear Sir,
The issue is related to the window frame-displacement introduced with Windows 2004.
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.
This has been corrected in Cubase Pro 11.
Best regards,
Georges Boboé
Steinberg Technical Support Representative
So Windows is to blame, from 2004 LOL Both Padshop Pro and Retrologue have been working flawlessly since I bought them, and all of a sudden in 10.5 they "break" and it's windows fault and i'd have to roll back to a previous version of windows.
No, no, I think anyone can agree here, that Steinberg broke the plugins and are aware of it, and fixed it in V11 and expect me to pay to get the fix. They could easily release a 10.5.xxx to fix this, but they won't. It's not like the plugins had this issue from the start, because they haven't. They were both working fine and if the change was made in Windows in 2004 ? Sorry I just have no clue what they are referring to.
Dear Sir,
The issue is related to the window frame-displacement introduced with Windows 2004.
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.
This has been corrected in Cubase Pro 11.
Best regards,
Georges Boboé
Steinberg Technical Support Representative
So Windows is to blame, from 2004 LOL Both Padshop Pro and Retrologue have been working flawlessly since I bought them, and all of a sudden in 10.5 they "break" and it's windows fault and i'd have to roll back to a previous version of windows.
No, no, I think anyone can agree here, that Steinberg broke the plugins and are aware of it, and fixed it in V11 and expect me to pay to get the fix. They could easily release a 10.5.xxx to fix this, but they won't. It's not like the plugins had this issue from the start, because they haven't. They were both working fine and if the change was made in Windows in 2004 ? Sorry I just have no clue what they are referring to.
Don't trust those with words of weakness, they are the most aggressive
-
- KVRAF
- 2630 posts since 16 Jan, 2013
2004 is the Windows 10 version. It's confusing because it could be easily assumed to be a date, however in this case it stands for April 2020. After this they switched from year/month format to year/half as they rarely released the update on the month it was named after anyway. The current Windows 10 release is 21H1.
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
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.LeVzi wrote: Sat May 22, 2021 7:43 am So Windows is to blame, from 2004 LOL Both Padshop Pro and Retrologue have been working flawlessly since I bought them, and all of a sudden in 10.5 they "break" and it's windows fault and i'd have to roll back to a previous version of windows.
No, no, I think anyone can agree here, that Steinberg broke the plugins and are aware of it, and fixed it in V11 and expect me to pay to get the fix. They could easily release a 10.5.xxx to fix this, but they won't. It's not like the plugins had this issue from the start, because they haven't. They were both working fine and if the change was made in Windows in 2004 ? Sorry I just have no clue what they are referring to.
Fernando (FMR)
-
- KVRAF
- 2065 posts since 14 Sep, 2004 from $HOME
So this is about the window displacement problem? I thought that was fixed with the latest 10.5 update. At least for me it was with the mix console window, which had the same problem before since that windows update....
There was also a little utility program from some clever guy which provided a workaround (quickly move the mixer window a tiny bit upon opening). Don’t know whether that works with plugin windows, too. It was someplace on the Steinberg forums, maybe I’ll find it again...
There was also a little utility program from some clever guy which provided a workaround (quickly move the mixer window a tiny bit upon opening). Don’t know whether that works with plugin windows, too. It was someplace on the Steinberg forums, maybe I’ll find it again...
-
- KVRist
- 410 posts since 9 Oct, 2013 from uk
No, I suspect the original reference they made was correct.fmr wrote: Sat May 22, 2021 8:49 am 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.
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.
System 1 - Win11; i9 13900HK miniPC; 64Gb; Iris XE graphics; Cubase 15.0.30; Studio Pro v8.1;UR44 i/o
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
-
- KVRist
- 410 posts since 9 Oct, 2013 from uk
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..?
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..?
Last edited by thebutler on Sat May 22, 2021 10:13 am, edited 2 times in total.
System 1 - Win11; i9 13900HK miniPC; 64Gb; Iris XE graphics; Cubase 15.0.30; Studio Pro v8.1;UR44 i/o
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4