Would you be able to share a screenshot of the bluriness compared to how it looks before being published? Also, what browser did you use to test the published file once it was uploaded to your LMS? Finally, you mentioned that you're using the "lock at optimal size setting" which will definitely help in preventing bluriness, but are you also using the 100% output slide size?
I can't send a slide since it includes proprietary content. We primarily test with IE and Chrome. The blurriness was seen prior to deploying to the actual LMS (just opening the published file in IE/Chrome for initial QC). We have been using the default "fixed width of 720 pixels" but will begin using the "100% output slide size. Thank you for pointing that out.
Thanks, Robin. Let me know if using "100% output slide size" makes a difference. Also, you'll likely see an improvement after uploading the content into your LMS since viewing published content locally can cause issues due to security restrictions on your local hard drive.
I wonder if this is connected to the blurry-preview issue I've noted a couple times. When you preview a slide it knocks down the resolution just enough to make it difficult to read, maybe 25% degradation.
It could be - what is the overall size you've been using? I've also seen some similar inconsistencies in Storyline based on scaling the screen resolution and how that impacts the DPI scaling of Studio and Storyline.
Thanks for pointing this out. Robin is seeing bluriness after publishing, so I'm not sure at this point if it could be related to the issue on our radar about bluriness in Preview, but it's definitely something we can look into if she doesn't see an improvement after changing the output slide size and testing the content within the LMS.
6 Replies
Hi Robin!
Would you be able to share a screenshot of the bluriness compared to how it looks before being published? Also, what browser did you use to test the published file once it was uploaded to your LMS? Finally, you mentioned that you're using the "lock at optimal size setting" which will definitely help in preventing bluriness, but are you also using the 100% output slide size?
I can't send a slide since it includes proprietary content. We primarily test with IE and Chrome. The blurriness was seen prior to deploying to the actual LMS (just opening the published file in IE/Chrome for initial QC). We have been using the default "fixed width of 720 pixels" but will begin using the "100% output slide size. Thank you for pointing that out.
Thanks, Robin. Let me know if using "100% output slide size" makes a difference. Also, you'll likely see an improvement after uploading the content into your LMS since viewing published content locally can cause issues due to security restrictions on your local hard drive.
I wonder if this is connected to the blurry-preview issue I've noted a couple times. When you preview a slide it knocks down the resolution just enough to make it difficult to read, maybe 25% degradation.
Hi Jim,
It could be - what is the overall size you've been using? I've also seen some similar inconsistencies in Storyline based on scaling the screen resolution and how that impacts the DPI scaling of Studio and Storyline.
Hey Jim,
Thanks for pointing this out. Robin is seeing bluriness after publishing, so I'm not sure at this point if it could be related to the issue on our radar about bluriness in Preview, but it's definitely something we can look into if she doesn't see an improvement after changing the output slide size and testing the content within the LMS.
This discussion is closed. You can start a new discussion or contact Articulate Support.