{ "attachments": [], "comments_archived": true, "date": "2003-09-19T18:28:23.000Z", "layout": "post", "title": "Flash MX Hates Progressive JPEGs", "wordpress_id": 480, "wordpress_slug": "flash-hates-progressive-jpeg", "wordpress_url": "http://www.decafbad.com/blog/?p=480", "year": "2003", "month": "09", "day": "19", "isDir": false, "slug": "flash-hates-progressive-jpeg", "type": "entry", "postName": "2003-09-19-flash-hates-progressive-jpeg", "html": "

\nOkay, I may be the last person fiddling with Flash to\ndiscover this, but here's what I've learned today:\n

\n

\nFlash MX hates progressive JPEGs.\n

\n

\nFrom the above: \"The Macromedia Flash Player does not have a\ndecompressor for progressive JPEG images, therefore files of this type\ncannot be loaded dynamically and will not display when using the\nloadMovie action.\"\n

\n

\nThis would have been nice to know, hours ago. Or maybe fixed in\nthe past year or so since the above linked tech note. See, although\nI'm a Jack of a lot of Trades, I don't really pay attention much\nto things like JPEGs and their progressive natures. It wasn't\nuntil I finally started randomly clicking buttons on and off in\nMacromedia Fireworks while exporting a test JPEG that I finally\nnarrowed down the problem.\n

\n

\nThis was after a day worth of examining ActionScript, XML data,\nHTTP headers, and a mess of other random dead ends. And a lot of\nlast-ditch random and exhaustive twiddling of checkboxes and\noptions.\n

\n

\nThen, once I had the words I\nwouldn't have had unless I already knew what my problem was, a Google search for\n\"flash progressive jpeg\"\ngot me all kinds of info.\n

\n

\nProblem is, the JPEGs supplied to the particular Flash app on which\nI'm hacking come from a random assortment of people working through\na content management system on the backend. They upload them\nwith a form in their browser, and this Flash app gets a URL to the\nimage via an XML doc it loads. Me, I'm probably in bed when this\nhappens. I'd love to have tested every one... er, rather, no I\nwouldn't.\n

\n

\nSo... Now I just have to figure out how to get all these people\nto start making sure that their JPEGs aren't progressive. Hmph.\n

\n

\nI can only hope that this message gets indexed and maybe provides\nmore triangulation for some other poor sucker in the future.\n

\n\n\n\n\n\n

shortname=flash_hates_progressive_jpeg

\n

Archived Comments

\n\n\n\n
\n\n\n", "body": "

\r\nOkay, I may be the last person fiddling with Flash to\r\ndiscover this, but here's what I've learned today:\r\n

\r\n

\r\nFlash MX hates progressive JPEGs.\r\n

\r\n

\r\nFrom the above: \"The Macromedia Flash Player does not have a\r\ndecompressor for progressive JPEG images, therefore files of this type\r\ncannot be loaded dynamically and will not display when using the\r\nloadMovie action.\"\r\n

\r\n

\r\nThis would have been nice to know, hours ago. Or maybe fixed in\r\nthe past year or so since the above linked tech note. See, although\r\nI'm a Jack of a lot of Trades, I don't really pay attention much\r\nto things like JPEGs and their progressive natures. It wasn't\r\nuntil I finally started randomly clicking buttons on and off in\r\nMacromedia Fireworks while exporting a test JPEG that I finally\r\nnarrowed down the problem.\r\n

\r\n

\r\nThis was after a day worth of examining ActionScript, XML data,\r\nHTTP headers, and a mess of other random dead ends. And a lot of\r\nlast-ditch random and exhaustive twiddling of checkboxes and\r\noptions.\r\n

\r\n

\r\nThen, once I had the words I\r\nwouldn't have had unless I already knew what my problem was, a Google search for\r\n\"flash progressive jpeg\"\r\ngot me all kinds of info.\r\n

\r\n

\r\nProblem is, the JPEGs supplied to the particular Flash app on which\r\nI'm hacking come from a random assortment of people working through\r\na content management system on the backend. They upload them\r\nwith a form in their browser, and this Flash app gets a URL to the\r\nimage via an XML doc it loads. Me, I'm probably in bed when this\r\nhappens. I'd love to have tested every one... er, rather, no I\r\nwouldn't.\r\n

\r\n

\r\nSo... Now I just have to figure out how to get all these people\r\nto start making sure that their JPEGs aren't progressive. Hmph.\r\n

\r\n

\r\nI can only hope that this message gets indexed and maybe provides\r\nmore triangulation for some other poor sucker in the future.\r\n

\r\n\r\nshortname=flash_hates_progressive_jpeg\r\n\r\n
\r\n

Archived Comments

\r\n \r\n \r\n \r\n
\r\n ", "parentPath": "./content/posts/archives/2003", "path": "2003/09/19/flash-hates-progressive-jpeg", "summary": "Okay, I may be the last person fiddling with Flash to\ndiscover this, but here's what I've learned today:\n\n\nFlash MX hates progressive JPEGs.\n\n\nFrom the above: \"The Macromedia Flash Player does not have a\ndecompressor for progressive JPEG images, therefore files of this type\ncannot be loaded dynamically and will not display when using the\nloadMovie action.\"\n\n\nThis would have been nice to know, hours ago. Or maybe fixed in\nthe past year or so since the above linked tech note. See, although\nI'm a Jack of a lot of Trades, I don't really pay attention much\nto things like JPEGs and their progressive natures. It wasn't\nuntil I finally started randomly clicking buttons on and off in\nMacromedia Fireworks while exporting a test JPEG that I finally\nnarrowed down the problem.\n\n\nThis was after a day worth of examining ActionScript, XML data,\nHTTP headers, and a mess of other random dead ends. And a lot of\nlast-ditch random and exhaustive twiddling of checkboxes and\noptions.\n\n\nThen, once I had the words I\nwouldn't have had unless I already knew what my problem was, a Google search for\n\"flash progressive jpeg\"\ngot me all kinds of info.\n\n\nProblem is, the JPEGs supplied to the particular Flash app on which\nI'm hacking come from a random assortment of people working through\na content management system on the backend. They upload them\nwith a form in their browser, and this Flash app gets a URL to the\nimage via an XML doc it loads. Me, I'm probably in bed when this\nhappens. I'd love to have tested every one... er, rather, no I\nwouldn't.\n\n\nSo... Now I just have to figure out how to get all these people\nto start making sure that their JPEGs aren't progressive. Hmph.\n\n\nI can only hope that this message gets indexed and maybe provides\nmore triangulation for some other poor sucker in the future.", "needsBuild": true, "prevPostPath": "2003/09/12/dont-copy-software", "prevPostTitle": "Don't copy that floppy, or cracked software strikes back", "nextPostPath": "2003/09/21/rss-feedback", "nextPostTitle": "Feedback loops and syndication" }