I apologize is this is covered elsewhere, but I didn't see it if it is. I have dual monitors because I find it easier to develop that way (pull up material in Word on one screen, copy into Storyline on the other). The Peek screen recorder seems to be a bit confused by that. When I try to record something, the \"window\" that shows up is about four inches from the screen I choose.
\n
For example, if I choose \"full screen\" of the monitor on my left, it puts the red box mostly in the middle of the two monitors instead of fully over the left side. I am posting a screen shot of where the window goes on this page for an example (attached). The weird thing is that it will record the screen as if it is in the proper place (though does record the line of record box itself). If I move it with the move crosshairs to cover the window fully over the where I want it, it does not record correctly (it acts offcenter). I've tried playing with various things in Properties to see if it is a \"compatability\" thing, but haven't found an answer yet. Anyone have any ideas?
I apologize is this is covered elsewhere, but I didn't see it if it is. I have dual monitors because I find it easier to develop that way (pull up material in Word on one screen, copy into Storyline on the other). The Peek screen recorder seems to be a bit confused by that. When I try to record something, the \"window\" that shows up is about four inches from the screen I choose.
\n
For example, if I choose \"full screen\" of the monitor on my left, it puts the red box mostly in the middle of the two monitors instead of fully over the left side. I am posting a screen shot of where the window goes on this page for an example (attached). The weird thing is that it will record the screen as if it is in the proper place (though does record the line of record box itself). If I move it with the move crosshairs to cover the window fully over the where I want it, it does not record correctly (it acts offcenter). I've tried playing with various things in Properties to see if it is a \"compatability\" thing, but haven't found an answer yet. Anyone have any ideas?
Welcome, Michael! Thanks for letting us know what you’ve tried so far, and I'm so sorry to hear you're still running into this issue.
\n
We definitely don't want you jumping through hoops if we can avoid it, so I've shared your latest update with my colleague, Rowie–who is assigned to your case. We'll do a deep dive to see if there's anything else we can recommend. I'll follow along and will certainly keep this discussion updated once we get to the root!
Welcome, Michael! Thanks for letting us know what you’ve tried so far, and I'm so sorry to hear you're still running into this issue.
\n
We definitely don't want you jumping through hoops if we can avoid it, so I've shared your latest update with my colleague, Rowie–who is assigned to your case. We'll do a deep dive to see if there's anything else we can recommend. I'll follow along and will certainly keep this discussion updated once we get to the root!
