Page 1 of 2

Annual Request: Equal height vertical spacing in Key Editor

Posted: Sun Dec 10, 2017 8:16 am
by N_K
Currently in Key Editor, there is extra vertical space between B and C, as well as E and F.
This might be handy for some workflows, but it breaks visual recognition of chords because the spaces between pitches do not correspond to semitones.

In equally spaced piano roll, where each semitone has same height as others, a chord will always have same amount of empty vertical space between its notes, no matter which key it is played from. This makes it easy to recognize chords based on their vertical pattern.

In Key Editor as it is now, a major chord has a visual pattern like augmented chord when in C, F, F#, G, or like a minor chord with fifth in bass when in C#, D, D#, E, G#, A, or like a major chord with fifth in bass when in A# and B. Attached is a screenshot to illustrate this.
Cubase-8-vs-Live-9-piano-roll.jpg
(342.84 KiB) Not downloaded yet

If any of developers see this, please consider adding the option to remove empty vertical space between B and C and E and F in Key Editor.
Equal vertical spacing corresponds to what is actually heard in 12TET and is more convenient for people coming to Cubase from other DAWs.

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Dec 16, 2017 3:25 am
by benjaminfrog
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Dec 16, 2017 6:59 am
by OxygenBeats
Wow, for some reason I've never even thought about that. But it would make a lot of sense and would be nice, and how hard could that be to implement? They could even make it optional in preferences if for some reason some people wanted to keep the extra space.

+1 from me!

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Dec 16, 2017 3:28 pm
by fbeauvaisc
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Dec 16, 2017 4:28 pm
by ANeeman
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Dec 16, 2017 6:17 pm
by Evertone
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Dec 16, 2017 8:50 pm
by dmbaer
+1.

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Tue Dec 19, 2017 1:55 am
by Starsprinkler
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Tue Dec 19, 2017 10:39 am
by liljefelt
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Tue Dec 19, 2017 5:37 pm
by Romantique Tp
Only if they make this a setting. The extra space makes the octaves and half steps clearer, specially when the editor is zoomed out.

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Thu Dec 21, 2017 1:43 am
by ANeeman
@Romantique Tp, yes, if all composers are programmers and doing their job by moving boxes in key editor. They always start their songs from one note (first after space) - it's easiest to find it at night :)

But I think that many proffesionals need to read scales as visual pictures, hieroglyphs as well. Therefore spaces are disturbing.

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Fri Dec 22, 2017 4:50 pm
by PeteL
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Tue Jan 09, 2018 10:30 am
by Yadihinz
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Tue Jan 09, 2018 5:15 pm
by In_Stereo
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Jul 21, 2018 5:10 pm
by kpmuzik
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Fri Sep 28, 2018 9:13 pm
by ninjaottermusic
+1

I'm in a chat server with several composers and we're all gawking over how annoying this is, even if several of us have gotten used to it.

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Sep 29, 2018 10:28 am
by Winter Rat
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Sep 29, 2018 4:10 pm
by arieln
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sun Oct 07, 2018 4:28 am
by Stephen57
N_K wrote:
Sun Dec 10, 2017 8:16 am
Currently in Key Editor, there is extra vertical space between B and C, as well as E and F.
This might be handy for some workflows, but it breaks visual recognition of chords because the spaces between pitches do not correspond to semitones.

If any of developers see this, please consider adding the option to remove empty vertical space between B and C and E and F in Key Editor.
Equal vertical spacing corresponds to what is actually heard in 12TET and is more convenient for people coming to Cubase from other DAWs.
+1

This would be a useful, meaningful improvement for musicians working in MIDI. Eminently logical, please implement if possible. Thanks.

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Mar 30, 2019 9:53 pm
by knechtodawas
+1
In Cubasis for iOS the spacing is equal, so I assume Steinberg is open minded regarding this issue ;).

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Jul 06, 2019 6:24 pm
by DRDRDR
+1
(the lines between B and C, E and F could be dashed)

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Wed Jul 17, 2019 10:25 am
by take3
+1

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sat Jul 20, 2019 6:05 pm
by Zoberflote
+1
This is a great suggestion! Please Steinberg, make this an option!

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Tue Nov 19, 2019 11:54 pm
by Starsprinkler
Giving this a bump so it's not forgotten.

In addition to better visual recognition of chords, it also saves valuable vertical screen space for the key editor.

Even if there are a bunch of things that have higher priority, I guess it's not a massive task to set all keys to have equal height.
(And really no need for optional preference as some suggested).

Re: Annual Request: Equal height vertical spacing in Key Editor

Posted: Sun Nov 24, 2019 3:31 pm
by ANeeman
+1 but it seems to be already forgotten :(