Ideal/Best Resolution of Photographic Characters?

Couple discussions on the internets about this ...

72 or 96 dpi?

Say No to 72 dpi

... still learning

Hey Ryan - just following up with you on this to let you know we're looking at it. I should know more later this week, but wanted to make sure you knew we saw your question.

Thanks David.

Waiting for direction and a tad surprised image optimization for the web is a curveball question ... ?

For clarity (I hope), my question again:

I assume Articulate went to great lengths to choose their character pack ... from what I see, these are huge images scaled down ... should we do the same? Don't use Photoshop for our scaling - Articulate will handle that?

Is it better to import an image twice (three times) as big as we need it - scaling it down? Also,...

Here's where it gets interesting: Display at users current browsers size. If I choose this option does it make any difference at all? Or do I just throw in my images sized for my Player, let the browser size scale said Player, and hope for the best???

Be good to know how best Articulate optimizes media.

Hey Ryan - 

The devs are looking into the resizing issue (save image from SL and re-insert = resized image).

From an output perspective:

You can work with high resolution images and let Storyline compress the images for you. Storyline will resize and optimize based on the image size you set on the slide level.

From an authoring perspective:

If I'm working with images created in an external graphics program, I would save them at the target size before importing into Storyline. No use lugging high res images around the slide level they're resized at a smaller size on the slide. A project full of high res images just your .story size larger.

Thanks David. Any and all direction/clarification is helpful.

I have a project coming up that's custom graphics (expensive). I want to be very sure I'm making the most of them and optimizing them accordingly.

Cheers.

Would look at the dimensions over the dpi. Dpi is really helpful when working on print targets (inDesign, MSWord) but seems pretty useless for screen targets.

As far as importing images, try to import them as close to the target size as you can get them. Storyline rescales on export but you'll probably see performance issues when authoring a slide with a giant image. The .story size will also balloon. 

If you import at the largest size you'll use in the story, you can copy and paste into other slides and it'll use the same file across slides. If you rescale your image to a smaller size, the exporter will generate another image. 

Thanks Steve!

Your copy and paste point is VERY good to know. That's the kind of stuff that needs to be shared & curated. Load time is insanely important to me, even if I think I'm "engaging", I want to respect the learners time.

That said, it looks like we are out of luck with browser scaling - After the exporter scales the image we're left to the mercy of the browser. No?

If you're looking to scale your project with the user's browser, your best option would be to increase image publish quality.

There will always be some level of image distortion when you scale images larger than their original size. Publishing at a higher quality ensures the images contain more detail when scaled. Have you tried a few different quality settings?

David, nope never thought about the image quality settings ... but will now!

Great advice!