# Locators Covering Measures in Key Editor

**URL:** <https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019>\
**Category:** Cubase\
**Tags:** cubase-9\
**Created:** [March 9, 2018, 2:23pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019 "2018-03-09T14:23:23Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 2:23pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/1 "2018-03-09T14:23:23Z")

</div>

I have an issue that may be by design, user error, or configuration. in the Key editor, when I set my left or right locator positions where I am working, it covers the actual measures and measure numbers. See the attached screen shot (I set the left locator between measure 10 and 11 - past that, you cannot see the measures). If I am working in a large area, it makes it impossible for me to see what measure I am on. Can this behavior be changed?

This has occurred in 9.5, 9.5.1 and 9.5.2 Pro

![](https://i.imgur.com/ngpEo0C.jpg)

---

<div class="post-metadata">

**Author:** ![Romantique\_Tp](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/romantique_tp/32/267315_2.png) [@Romantique\_Tp](https://forums.steinberg.net/u/Romantique_Tp)\
**Post date:** [March 9, 2018, 2:45pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/2 "2018-03-09T14:45:33Z")

</div>

No issues here, I can always clearly see the bar numbers no matter what I do. Make sure that your GPU drivers are updated.

BTW, your signature doesn’t mention which OS you’re using.

---

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 2:50pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/3 "2018-03-09T14:50:45Z")

</div>

Windows 10 1709. Fully updated drivers on everything.

---

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 2:51pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/4 "2018-03-09T14:51:22Z")

</div>

FWIW, this also happens on my Cubase Elements 9.5 that I run on my Microsoft Surface.

---

<div class="post-metadata">

**Author:** ![steve](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/steve/32/193789_2.png) [@steve](https://forums.steinberg.net/u/steve)\
**Post date:** [March 9, 2018, 3:27pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/5 "2018-03-09T15:27:05Z")

</div>

I think this is a prefs corruption in the colors setup. If you select a different color scheme from the User Interface-color schemes prefs page does it fix that?

What I did to fix various color scheme probs was to just restore a recent backup of my Cubase prefs folder (using Windows File History, Apple Time Machine can do the same of course.)

I can’t find a way to reproduce it though.

---

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 4:04pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/6 "2018-03-09T16:04:00Z")

</div>

Just tried to change color schemes. Unfortunately, it did not fix the issue.

---

<div class="post-metadata">

**Author:** ![steve](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/steve/32/193789_2.png) [@steve](https://forums.steinberg.net/u/steve)\
**Post date:** [March 9, 2018, 4:29pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/7 "2018-03-09T16:29:51Z")

</div>

In that case, I would bet the prefs are corrupted. So try a [Cubase Safe Start](https://www.google.com/search?q=Cubase+Safe+Start&oq=Cubase+Safe+Start&aqs=chrome..69i57j0.303j0j1&sourceid=chrome&ie=UTF-8).

---

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 4:52pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/8 "2018-03-09T16:52:07Z")

</div>

Thank you for your suggestion. I did try blow the preferences away, but the problem still remains. ☹

It must be graphics driver related. My Surface is fully up to date, but let me try the Intel version of the graphics driver, instead of the Gigabyte version.

---

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 5:05pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/9 "2018-03-09T17:05:37Z")

</div>

Update - I went directly to the Intel site and downloaded the latest Graphics driver for the video - still no joy. ☹

---

<div class="post-metadata">

**Author:** ![husker](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/husker/32/2034_2.png) [@husker](https://forums.steinberg.net/u/husker)\
**Post date:** [March 9, 2018, 5:41pm UTC](https://forums.steinberg.net/t/locators-covering-measures-in-key-editor/106019/10 "2018-03-09T17:41:42Z")

</div>

I just opened a ticket via chat with Steinberg. I showed him a picture and a quick video, and he thought the issue was odd. Gave me an immediate ticket.

Coming from Sonar, that is good support.
