Yeah, main window will be fine. Thanksmonkeymanx wrote: Wed Dec 23, 2020 9:29 pm Is there a particular screen to take a screen shot of? The main window?
I have a 55" 4K OLED for a monitor and I sit a bit back from it so I scale at 200% so I can still read text and everything looks good to me.
Cubase 11 available now
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
-
- KVRian
- 836 posts since 12 Aug, 2005
https://www.dropbox.com/s/ehzagnzdv3bom ... t.bmp?dl=0
That's a bitmap so that you are looking at what I'm looking at.
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Thanks! Indeed it looks much better than here at 125%. Apparently they've redrawn all the stuff for 200% that was the only Hi-DPI scaling supported in v10.x, whereas the 125%, 150% and 175% introduced with v11.0 is still using upscaled bitmaps for many elementsmonkeymanx wrote: Wed Dec 23, 2020 9:48 pmhttps://www.dropbox.com/s/ehzagnzdv3bom ... t.bmp?dl=0
That's a bitmap so that you are looking at what I'm looking at.
Pretty lame.
-
- KVRAF
- 9143 posts since 7 Oct, 2005
It looks ok, but slightly blurry compared to what I see on my monitor.monkeymanx wrote: Wed Dec 23, 2020 9:48 pmhttps://www.dropbox.com/s/ehzagnzdv3bom ... t.bmp?dl=0
That's a bitmap so that you are looking at what I'm looking at.
It looks very clear when open it on another tab! Sorry!
For me It is not crystal clear for me, but it is fine
Anyway, I tried 125% scale, and still looks good for me. Here are my screenshot for 125% and 100%:
You do not have the required permissions to view the files attached to this post.
Last edited by EnGee on Wed Dec 23, 2020 10:41 pm, edited 1 time in total.
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
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Well, I might be oversensitive but my eyes just can't fix focus on the 125% when looking at the tools or that blue thingy in Inspector. Whatever I do it's blurry.EnGee wrote: Wed Dec 23, 2020 10:31 pmAnyway, I tried 125% scale, and still looks good for me. Here are my screenshot for 125% and 100%:
-
- KVRAF
- 9143 posts since 7 Oct, 2005
Yes, you are right. The tools are not clear in 125% and 150%, but surprisingly very clear at 200%!antic604 wrote: Wed Dec 23, 2020 10:39 pmWell, I might be oversensitive but my eyes just can't fix focus on the 125% when looking at the tools or that blue thingy in Inspector. Whatever I do it's blurry.EnGee wrote: Wed Dec 23, 2020 10:31 pmAnyway, I tried 125% scale, and still looks good for me. Here are my screenshot for 125% and 100%:
You do not have the required permissions to view the files attached to this post.
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
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Other than the high-DPI fail, there's few more things that make Cubase "unusable" for me in its current state:
See you at v12, I guess
- modal keyboard shortcuts - don't get me wrong, lots of things can be set up but there's very few modal ones, so you can e.g. show automation and hide automatio, zoom to selection and zoom out but they have to be SEPARATE keys
- tool shortcuts - draw tool is 3rd on the list, but it's under key 7 or 8? very intuitive

- default modifiers - I think it's the only DAW where Ctrl momentarily disables snap when moving clips or notes? Everywhere else it's Shift, because one wants to ...shift things a bit; and surprisingly it's the only one that can't be changed
- automating VSTs - the fact you need to go & find your parameter for automation from huge drop-down list is a huge turn off; I know I can record a small bit and then use that, but that's not helpful
- using MIDI controllers to control VST parameters - good luck if the VST doesn't have MIDI learn (many don't, especially FX); I watched 10+ videos, read through the user manual and asked around and still have no clue how to map Massive X's macro knobs, which is 1-2 clicks in Live, Bitwig, Studio One or ...Reason
- VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2

- Sampler Track - can anyone explain to me what's the difference between this and a Sampler device in any other DAW? I don't really understand why I have to plan ahead to use a special type of track, when I want sampler?
- Updates - it's not really updated beyond the annual pay time x.5 / x.0 cycle, is it? At least since 9.5 it's been like that, I think? If you compare that to say Studio One that releases paid upgrade every 2 years but in the meantile gives at least 5 or 6 "free" substantial updates with genuinely new stuff & improvements, then it's hard to justify it owning Cubase
See you at v12, I guess
- KVRian
- 1418 posts since 14 Apr, 2016 from Germany
That are VST3 specifications & has nothing to do with a certain Sequencer:VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2
Windows 64 Bit: C:\Program Files\Common Files\VST3
Windows 32 Bit: C:\Program Files (x86)\Common Files\VST3
Mac OS X: Library/Audio/Plug-ins/VST3

Intel® Core™ i9-9900K•Cubase 11•Presonus Eris E8 XT•Focusrite Scarlett 18i20 & Octopre•NI Kontrol S61 MK2•Steinberg CC121•Synthesizers: Arturia Casio Korg Roland Yamaha
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
I know, but in every other DAW I tried - Live, Bitwig, Studio One, Reason, Reaper, Bandlab, FL - one can add a custom folders and VST3 that are there are found & used. Not in Cubasemladi wrote: Fri Dec 25, 2020 8:21 amThat are VST3 specifications & has nothing to do with a certain Sequencer:VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2
Windows 64 Bit: C:\Program Files\Common Files\VST3
Windows 32 Bit: C:\Program Files (x86)\Common Files\VST3
Mac OS X: Library/Audio/Plug-ins/VST3
-
- KVRAF
- 1863 posts since 11 Apr, 2008
Short version: sell Cubase, you wasted your money. Don't wait for v12 because you will be disappointed again.antic604 wrote: Fri Dec 25, 2020 8:12 am Other than the high-DPI fail, there's few more things that make Cubase "unusable" for me in its current state:I mean it's a wonderful DAW, likely including 99% of the features one might want and probably few dozens more you had no idea you might want, but it's so damn inconsistent with old - and sometimes genuinely ancient - stuff poking through everywhere. Trying Cubase gives me new appreciation for Live or Reason, that both have been on the market for 20 years but feel much more consistent and coherent, most likely because they refused to add each & every possible feature that people wanted.
- modal keyboard shortcuts - don't get me wrong, lots of things can be set up but there's very few modal ones, so you can e.g. show automation and hide automatio, zoom to selection and zoom out but they have to be SEPARATE keys
- tool shortcuts - draw tool is 3rd on the list, but it's under key 7 or 8? very intuitive
- default modifiers - I think it's the only DAW where Ctrl momentarily disables snap when moving clips or notes? Everywhere else it's Shift, because one wants to ...shift things a bit; and surprisingly it's the only one that can't be changed
- automating VSTs - the fact you need to go & find your parameter for automation from huge drop-down list is a huge turn off; I know I can record a small bit and then use that, but that's not helpful
- using MIDI controllers to control VST parameters - good luck if the VST doesn't have MIDI learn (many don't, especially FX); I watched 10+ videos, read through the user manual and asked around and still have no clue how to map Massive X's macro knobs, which is 1-2 clicks in Live, Bitwig, Studio One or ...Reason
- VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2
- Sampler Track - can anyone explain to me what's the difference between this and a Sampler device in any other DAW? I don't really understand why I have to plan ahead to use a special type of track, when I want sampler?
- Updates - it's not really updated beyond the annual pay time x.5 / x.0 cycle, is it? At least since 9.5 it's been like that, I think? If you compare that to say Studio One that releases paid upgrade every 2 years but in the meantile gives at least 5 or 6 "free" substantial updates with genuinely new stuff & improvements, then it's hard to justify it owning Cubase
See you at v12, I guess![]()
Long version:
By buying Cubase you have paid for functionalities like classic multitrack recording with classic mixer approach, you paid for (lacking) features for multimedia sound designers and composers, you paid for VR production capabilities... Will, you ever use any of that?
Believe me, Cubase 12 will not change much (especially by looking at how the latest versions brought not much to the table), you'll just waste your money again. Most of the issues you mentioned are in Cubase for more than a decade and nothing was done to improve that. Forget about any improvements in that matter in v12, v13, or v14, etc.
Damn, even FruityLoops 3, around 15 years ago, had a better plugin automation system than Cubase today.
Seriously I'm using Cubase for long years and I love it but I can't recommend it to music makers (especially electronic music). Cubase is great but for music makers, 'beatmakers', etc. there are better alternatives.
Also:
Honestly, I can give you one solution: instead of buying every single DAW on the market, use one that you like, stick to it, and start making music. I can bet that you didn't finish more than 1 track in years
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Why you bother yourself with how I spend my time & money?pixel85 wrote: Fri Dec 25, 2020 11:43 amHonestly, I can give you one solution: instead of buying every single DAW on the market, use one that you like, stick to it, and start making music. I can bet that you didn't finish more than 1 track in years![]()
Cubase Pro 11 was a cheap upgrade from Elements that I got with my audio interface, so I thought why the hell not? Now I know - hell no!
But it's true - considering it's the end of 2020 and I came back to music "making" in early 2017 I only finished 2 tracks in that time, although nearly finished probably 10x as many. I just enjoy trying & learning new DAWs more than finishing music, I guess.
-
ReleaseCandidate ReleaseCandidate https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=476930
- KVRian
- 620 posts since 19 Oct, 2020
Well, because the specs are from Steinberg, Cubase is the only DAW that I know of in which you can't change them.mladi wrote: Fri Dec 25, 2020 8:21 amThat are VST3 specifications & has nothing to do with a certain Sequencer:VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
No, not really. VST3 spec has a mandatory place for the plug-ins to be installed (contrary to what happened with VST2). If you install them in other places (most of the installers don't even allow to), you are asking for trouble.ReleaseCandidate wrote: Fri Dec 25, 2020 3:38 pmWell, because the specs are from Steinberg, Cubase is the only DAW that I know of in which you can't change them.mladi wrote: Fri Dec 25, 2020 8:21 amThat are VST3 specifications & has nothing to do with a certain Sequencer:VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2
Fernando (FMR)
-
ReleaseCandidate ReleaseCandidate https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=476930
- KVRian
- 620 posts since 19 Oct, 2020
Yes, I know. But because the VST3 specs are from Steinberg, their DAWs are the only ones that I know of that do not allow for other directories to search for VST3 too. Yes, I firmly believe that Cubase would have additional search paths if the VST3 definitions were made by e.g. Ableton.fmr wrote: Fri Dec 25, 2020 4:07 pmNo, not really. VST3 spec has a mandatory place for the plug-ins to be installed (contrary to what happened with VST2).ReleaseCandidate wrote: Fri Dec 25, 2020 3:38 pmWell, because the specs are from Steinberg, Cubase is the only DAW that I know of in which you can't change them.mladi wrote: Fri Dec 25, 2020 8:21 amThat are VST3 specifications & has nothing to do with a certain Sequencer:VST3 handling - for some reason one can't change the path for where VST3 are installed (it expects the default C/Program Files/Common/VST3 on PC) so in my case where I keep all VST formats in one custom folder tree I only had access to VST2
-
- KVRAF
- 1863 posts since 11 Apr, 2008
It's Christmas time, we should care about each other
But yeah, I shouldn't care about anything but myself. It's not safe especially on music production forums full of GAS victims