# Keyboard appears to be drifting off screen!

**URL:** <https://forums.allen-heath.com/t/keyboard-appears-to-be-drifting-off-screen/6694>\
**Category:** dLive Troubleshooting\
**Created:** [13 February 2018 19:25 UTC](https://forums.allen-heath.com/t/keyboard-appears-to-be-drifting-off-screen/6694 "2018-02-13T19:25:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![richardbarley](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/richardbarley/32/824_2.png) [@richardbarley](https://forums.allen-heath.com/u/richardbarley)\
**Post date:** [13 February 2018 19:25 UTC](https://forums.allen-heath.com/t/keyboard-appears-to-be-drifting-off-screen/6694/1 "2018-02-13T19:25:29Z")

</div>

Woah, so this is a new one: I’m using a usb keyboard as I often do when I have to input a lot of text for scenes and such… today, however, the on-screen keyboard appears to be drifting lower and lower every time I open a dialogue to name scenes. Firmware 1.62, and _only_ in the scene manager. Strip naming appears normal. Any thoughts on what might cause this?

---

<div class="post-metadata">

**Author:** ![richardbarley](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/richardbarley/32/824_2.png) [@richardbarley](https://forums.allen-heath.com/u/richardbarley)\
**Post date:** [13 February 2018 19:27 UTC](https://forums.allen-heath.com/t/keyboard-appears-to-be-drifting-off-screen/6694/2 "2018-02-13T19:27:17Z")

</div>

oops, too large, here’s what it looks like.

 ![IMG_20180213_111719.jpg](https://us1.discourse-cdn.com/flex002/uploads/allenheathdigitalcommunity/original/2X/e/e44576c9edbd45e267e64760f839a4037ca2ff94.jpeg)

---

<div class="post-metadata">

**Author:** ![Lunatoon](https://avatars.discourse-cdn.com/v4/letter/l/aca169/32.png) [@Lunatoon](https://forums.allen-heath.com/u/Lunatoon)\
**Post date:** [8 November 2025 21:04 UTC](https://forums.allen-heath.com/t/keyboard-appears-to-be-drifting-off-screen/6694/3 "2025-11-08T21:04:00Z")

</div>

I had the same thing happen and had to restart the board.
