By David Stephens
On November 13, 2013

The release of Adobe Muse CC 7.0, which was announced on November 13th, includes many features and improvements. This article describes some of the output improvements, which continue the trend described in Muse 5 Code Improvements and IE7,  Code Improvements in Muse 4, and earlier posts.  Adobe Muse CC 7.0 includes improvements to images, changes to produce consistent leading across browsers, and a mechanism for developers to build and share their own service based widgets that inject code into the website. These widgets are built using the MuCow (Muse Configurable Options Widget) SDK and were the foundation for the social widgets shipped with Adobe Muse CC version 7.

Image Resampling

Adobe Muse CC 7.0 uses a Bicubic Sharper algorithm to produce higher quality images when resampling is required due to resizing an image smaller. Earlier versions used a more generic Bicubic algorithm. The difference between the two algorithms can be seen in the following images exported from different versions of Adobe Muse CC.

Bicubic

Adobe Muse CC 6.0 Output: Bicubic resampling of an image reduced in size by a factor of 6.

Bicubic Sharper

Adobe Muse CC 7.0 Output: Bicubic sharper resampling of an image reduced by a factor of 6.

New Site Properties

Adobe Muse CC 7.0 includes two new site properties: one for controlling whether it automatically converts images imported as PNG to JPEG if the image does not contain transparency; one for improving the consistency of leading across browsers.

Adobe Muse CC 7.0 Site Preferences

New site preferences for image encoding and line spacing.

 

Image Encoding

Two popular formats for image encoding are JPEG and PNG. PNG images support transparency and are typically significantly larger (typically somewhere between 2 and 10 times larger) on disk than JPEG compressed images. Therefore, if the image does not include any native transparency, load performance may be significantly improved by using JPEG instead of PNG.

Consistent Leading Across Browsers

The new site property ‘Round Leading to a Whole Number’ has been added to improve the consistency of leading across browsers. With this feature when line-height is specified as a percentage of font size (e.g., 120% of 14px), the calculated value (e.g., 16.8px) will now be rounded to a whole number (e.g., 17px).  Leading and text frame height are more consistent across browsers when line-height is rounded.

Consistent leading with rounded line-spacing

Leading is consistent across browsers, Firefox on the left and Chrome on the right, when line-height is rounded.

Result of unrounded line-spacing in Firefox and Chrome

Leading is inconsistent across browsers, Firefox on the left and Chrome on the right, when line-height is not rounded.

 

Internet Explorer 7 and 64-bit Muse

In order to provide the highest quality output for modern browsers, Adobe Muse CC 7 is the last release that will support IE 7. The most notable impact of this change will be the 100% elements that are currently supported via JavaScript but will be replaced with a CSS-based approach.
Adobe Muse CC is also in the process of transitioning from an AIR runtime to a 64-bit native application allowing for improved performance and user interface. The native version of Muse is expected to release in the first half of 2014 and will require 64-bit hardware to run.

COMMENTS

  • By Jason - 10:13 AM on November 14, 2013  

    Will the out put improvements address tablet sites built with Muse not displaying correctly on Android tablets?

    • By David Stephens - 4:19 PM on November 14, 2013  

      Jason, we’d certainly be interested in hearing more details of any problems you are having. We routinely run thousands of tests on multiple devices every day. If you can point us at a site you’ve built which currently displays a problem, we’d be happy to take a look.

  • By Uri Kirstein - 2:50 PM on November 18, 2013  

    Related: Is there a way to avoid ANY image resampling for JPGs etc. ? This is my number 1 requested feature!

  • By Uri Kirstein - 6:30 AM on November 20, 2013  

    Hi – Loving all the new features. Still wondering if Adobe is sharing their approach on offering an option to disable resampling/recompressing our inserted JPGs on resize in Muse. I understand offering resampling as an option but forcing this seems strange and out of line with the great user-centerness of this App. However knowing Adobe I would think this is in the works. As I have seen, folks have most complained when a tool takes away your control changing our handwritten code or in this case, changing our carefully precompressed images. Just wondering if you had anything to share on the topic, thank you!

  • By David Stephens - 1:07 PM on November 25, 2013  

    Uri, it would be interesting to know your use case. The primary use cases I’m aware of are full screen slideshows and viewing on retina displays.

    We definitely have plans to add support for retina quality images in a future release. The trick is to support high quality images on retina displays without introducing a performance penalty for visitors who are viewing your site on a non-retina display over a slow network (e.g., cellular).

    Even for retina displays, some images are far too large for what can be rendered and have significant performance penalties. These images have to be downloaded to your visitors’ device before they can be rendered and the browser will still resample them if they are too large for the resolution of their display.

    Here are some interesting articles about how users will abandon your site if they have to wait longer than a few seconds.
    http://www.nytimes.com/2012/03/01/technology/impatient-web-users-flee-slow-loading-sites.html?pagewanted=all&_r=0
    http://www.strangeloopnetworks.com/resources/infographics/web-performance-and-user-expectations/website-abandonment-happens-after-3-seconds/
    http://blog.kissmetrics.com/loading-time/