When I open a video in replay, the image is distorted and pixelated. Thankfully when I published the video as an MP4, it's fine. But I can't see anything when looking in Replay. I have uninstalled and reinstalled Replay and that seems to have worked in the short term (about 2 weeks ago). But opening Replay today is showing the same issue. I don't want to have to keep uninstalling and reinstalling Replay. I have attached an image for reference.
I have the same issue - we import videos recorded in MS Teams and then edit them with Replay. First time imported into Replay, the video looks perfect. When I save and close the project, then reopen, the video is completely pixilated, making it impossible for me to do my edits.
Try the suggested workarounds in the post. After you open Replay and see the pixelization, minimize it and then maximize it. This worked for me. Just really annoying. I also found the first suggestion worked... click record for a second and then stop.
This issue was first reported back in 2022 and the workarounds were documented by other users over a year ago (See Page 1 of this issue). Any idea when this will be fixed?
30 Replies
I have the same issue - we import videos recorded in MS Teams and then edit them with Replay. First time imported into Replay, the video looks perfect. When I save and close the project, then reopen, the video is completely pixilated, making it impossible for me to do my edits.
Enid,
Try the suggested workarounds in the post. After you open Replay and see the pixelization, minimize it and then maximize it. This worked for me. Just really annoying. I also found the first suggestion worked... click record for a second and then stop.
This issue just started happening to me in the last week. I used Jeanne's tip above and it worked perfect! Thank you so much!
Hi Amy!
So glad to hear Jeanne's post helped solve your issue! If you run into any setbacks moving forward, please let us know.
Have a great rest of your week!
This post was removed by the author
Steven,
This issue was first reported back in 2022 and the workarounds were documented by other users over a year ago (See Page 1 of this issue). Any idea when this will be fixed?
Thank you.