Will Adobe ever add support for JPEG-XR?

There's been quite a bit of work done on the Flash Player to display and export JPEG-XR files. During the Flash CS6 prerelease, the Flash team talked about additional JPEG-XR support for things like spritesheet creation.
I know there's an ancient Photoshop plug-in for JPEG-XR, but does Adobe have any plans to make JPEG-XR a first-class citizen in Photoshop? Considering the numerous benefits the format offers, I'm puzzled as to why this hasn't been added.
Either way, it would be helpful to get the scoop. If there are no plans to support it then I'll buy a product that does, but I'd prefer Photoshop.

I've been using XnConvert to convert uncompressed files to JPEG-XR. It's a free, cross-platform, batch file converter:
http://www.xnconvert.com/
XnConvert doesn't have as much control over compression settings as I would like, but the JPEG-XR files it creates are 30% – 50% smaller than comparable JPEG files saved using Photoshop's "Save for Web".

Similar Messages

How can I add support for JPEG 2000 to Final Cut Express?

How can I add support for JPEG 2000 to Final Cut Express 4? I need to export an .mov file in the JPEG2000 format but it is not available as a quicktime export option. Is this something that I can add via a quicktime .component? Would appreciate any insight anyone might have... Thank you.

I believe you need to purchase the QuickTime Pro key ($29.99 USD). Once you enter the registration number in System Preferences for QuickTime Player 7, it 'unlocks' several export features, including JPEG2000.
See:
http://support.apple.com/kb/SP521
http://support.apple.com/kb/HT3820
http://support.apple.com/kb/HT2240
http://store.apple.com/us/product/D3380Z/A/quicktime-7-pro-for-mac-os-x?fnode=62
-DH

Please add support for JPEG Exchangeable Image File Format (EXIF)

It seems that now Adobe® Illustrator® can export only to the JPEG File Interchange Format (JFIF). We should have an option to produce the JPEG Exchangeable image file format (EXIF) as well (just like Photoshop does!). Why this is so important to me? I generally work under Illustrator and I often post my work on Behence. I work with 'sRGB IEC61966-2.1' color profile. When publishing I use *.jpg with embedded ICC Color Profile. But it looks like Behence doesn’t fully support the JPEG JFIF – for example it cannot read its icc data correctly. The effect is that my work looses its quality! The only option to produce the JPEG EXIF I have now is to: Export *.ai file to JPEG (under Adobe Illustrator) > go to Photoshop > Create new project > Paste the *.jpg > and Sava As JPEG with icc embedded. This guarantees my files are being processed correctly.
(JPEG) Formally, the EXIF and JFIF standards are incompatible. This is because both specify that their particular application segment (APP0 for JFIF, APP1 for Exif) must be the first in the image file. In practice, many programs and digital cameras produce files with both application segments included. This will not affect the image decoding for most decoders, but poorly designed JFIF or Exif parsers may not recognize the file properly. ( http://en.wikipedia.org/wiki/JPEG_File_Interchange_Format#Exif_comparison )
I’ve analyzed my files using JPEGsnoop 1.6.1 (an app by Calvin Hass, http://www.impulseadventure.com/photo/) and here is the result:
A) an *.jpg file produced with Adobe Illustrator > File > Export > JPEG > ICC profile embedded:
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP0 (xFFE0) ***
OFFSET: 0x00000002
length     = 16
identifier = [JFIF]
version    = [1.2]
density    = 72 x 72 DPI (dots per inch)
thumbnail = 0 x 0
B) an *.jpg file produced with Adobe Illustrator > File > Save For Web > JPEG > ICC profile embedded:
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP0 (xFFE0) ***
OFFSET: 0x00000002
length     = 16
identifier = [JFIF]
version    = [1.2]
density    = 100 x 100 (aspect ratio)
thumbnail = 0 x 0
C) an *.jpg file produced with Adobe Photoshop > File > Save As > JPEG > ICC Profile embedded
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP1 (xFFE1) ***
OFFSET: 0x00000002
length          = 1320
Identifier      = [Exif]
Identifier TIFF = 0x[4D4D002A 00000008]
Endian          = Motorola (big)
TAG Mark x002A = 0x002A
EXIF IFD0 @ Absolute 0x00000014
Dir Length = 0x0007
[Orientation ] = Row 0: top, Col 0: left
[XResolution ] = 720000/10000
[YResolution ] = 720000/10000
[ResolutionUnit ] = Inch
[Software ] = "Adobe Photoshop CC 2014 (Windows)"
[DateTime ] = "2014:08:02 17:21:15"
[ExifOffset ] = @ 0x00A8
Offset to Next IFD = 0x000000D4
EXIF IFD1 @ Absolute 0x000000E0
Dir Length = 0x0006
[Compression ] = JPEG
[XResolution ] = 72/1
[YResolution ] = 72/1
[ResolutionUnit ] = Inch
[JpegIFOffset ] = @ +0x0132 = @ 0x013E
[JpegIFByteCount ] = 1006
Offset to Next IFD = 0x00000000
EXIF SubIFD @ Absolute 0x000000B4
Dir Length = 0x0003
[ColorSpace ] = sRGB
[ExifImageWidth ] = 200
[ExifImageHeight ] = 200
Regards,
Pawel Kuc

This is a user-to-user forum and is not monitored by Apple for feedback purposes. You can give feedback to Apple here: Apple - Mac OS X - Feedback

Please add support for MXF files created by Blackmagic Hyperdeck Studio

We have a Hyperdeck Studio that records DNxHD220 files in a MXF wrapper. Right now it is not possible to import them into Premiere CS5.5.
It would be great if Adobe would add support for those files.
Regards
NFact

It's mostly users here in the forums. Here's how to get Adobe to listen.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Will there ever be support in Lightroom 4 for Olympus raw files

Will there ever be support in Lightroom 4 for Olympus raw files?

Which camera exactly?
Support varies camera by camera.
Supported cameras
Camera Raw plug-in | Supported cameras
Compatible Adobe software
Camera Raw-compatible Adobe applications

Could Adobe please advise if they will be adding tethering support for Nikon D600

Could Adobe please advise if they will be adding tethering support for Nikon D600 as it is instrumental to our decison regarding purchase.
Many thanks

ssprengel wrote:
Nobody is happy with the answer about old software not getting updated with new cameras, but if you look into it, Adobe had to lay off about half their employees over the past few years to keep the company viable in the declining economy, so they don’t have extra people to update and test plug-ins for non-current versions, and if they did, then some people wouldn’t buy the newer version and they’d have even less money.
Adobe has only just gotten the D600 supported for raw format in their current beta version of LR, which affects everyone with a D600, and if they had to wait for Nikon for supply and SDK and also have to prioritize their work to keep things on schedule, tethering is likely to lag behind raw-file support for any particular camera. Apple controls their entire computer environment, hardware and software, so it’s not surprising they can implement tethered capture from day one, but Adobe must figure things out for OSes they don’t own, both Mac and PC, so they rely on waiting for Nikon to do things for them, and then figuring out how to get it to work.
Well boo hoo for Adobe ... life sure is tough for them ... if they can't handle the load maybe they should get out of the business of software development ... They can't be all that worried about revenue to support Lightroom development or they wouldn't have reduced the price of the full version by 50% and the upgrade price by 20% ... it was a less than smart move considering they have been bragging for the past couple of years about how many more folks use Lightroom vs. other competitive options ...
Aperture 3, Capture One both have tether support for the D600 ... and many more cameras than are supported by Lightroom ... those developers are working and engineering solutions in the very same economy as Adobe (and C1 supports both platforms as well, costs much more than Lr and employs far fewer engineers) ... why aren't they suffering from the same lack of support? ... or using the camera makers to deflect blame for the lack of results?
Excuses are not solutions ...

[svn:fx-4.x] 14985: Add support for mirroring for both error tips and tool tips in positionTip ().

Revision: 14985
Revision: 14985
Author:   [email protected]
Date:     2010-03-24 09:40:24 -0700 (Wed, 24 Mar 2010)
Log Message:
Add support for mirroring for both error tips and tool tips in positionTip(). The layoutDirection of the toolTip will be the same as the component it goes with, or LTR, if the component is not ILayoutDirectionElement.
QE notes:
Doc notes: None
Bugs: SDK-25821
Reviewed By: Jason
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-25821
Modified Paths:
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/managers/ToolTipManagerImpl.as
    flex/sdk/branches/4.x/tools/dependencychecker/frameworkSwcExceptionsList.txt

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn] 3203: Add support for inline two-way data binding (syntax is @{expr}) .

Revision: 3203 Author: [email protected] Date: 2008-09-14 05:11:47 -0700 (Sun, 14 Sep 2008) Log Message: ----------- Add support for inline two-way data binding (syntax is @{expr}). Also add support for two-way data binding via the <mx:Binding> tag and the new property twoWay=boolean (default is false). Code Reviewer: Paul QA: tests for this feature need to be added to the regression test suite Doc: new feature which needs to be documented Modified Paths: -------------- flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/analyzer/SyntaxAnalyzer.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AnonymousObjectGraph Builder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ModelBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ServiceRequestBuilde r.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/XMLBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/XMLListBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/BindingNode.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/TextParser.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/BindingExpression.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties

EvilDave UK wrote:
Surely there's a more practical way around this without having to reboot?
Before you go to the trouble of going through all those steps, be warned that attempting to use Dreamweaver CS4 with SVN could even cause Dreamweaver to crash after updating to SVN 1.6.2. I, too, have abandoned SVN integration with Dreamweaver until the problems are sorted out. I reported this problem to Adobe a couple of weeks ago, and spent a long time working with an Adobe engineer, who was able to reproduce the problem, but not offer a solution. Hopefully, the next version of Dreamweaver will have more robust support for Subversion.

Will Adobe Proto be released for Kindle Fire?

Will Adobe Proto be released for Kindle Fire?

Hi Jimboiphoto,
The Kindle Fire doesn't meet the minimum system requirements from what I can tell
http://www.adobe.com/products/proto/tech-specs.html
The Kindle Fire only comes with a 7" screen at 1280x600 resolution
Please add your vote here for consideration for add supporting for this kind of tablet
http://forums.adobe.com/ideas/1406
-Dave

IOS Newsstand app, add support for .folio files

Hello!
We have an iOS Newsstand app to provide our issues to our clients, and we use a PDF reader.
We would like to add support for .folio files in the app, by using a folio reader in our app.
Searching around, I've only found the specifications for the .folio files and the Adobe Content Viewer app.
Is it possible to have some more specific information on how we can make something like the Adobe Content Viewer app that we can integrate in our app?
For example how we would parse the xml files, what views/controls to use (eg. UIWebview?) etc.
Thank you very much!

Neil let clear something:
- After the .folio specification became public (with license off course) the "This really isn't possible to do" is not truth.
I believe that what people need to know is that: "Are we allowed to build a viewer?" / "Does Adobe allow programmers to give it a go?"
Before March this wasn't allowed but since the spec became public we all hope (and I believe Adobe too) that this format will have an industry standard acceptance - like the PDF. In this case many people will try to create viewers, software, builders etc.
The DPS is a great platform but VERY EXPENSIVE. Companies around the world have developed and are in a position to develop great experiences and great apps. Sharing the .folio is big and this is what we need to clear - and not the number of staff working on the DPS Viewer.
Thank you in advanced.

Will Adobe develop a patch for pixelated CS6 workspace on retina display?

Will Adobe develop a patch for pixelated CS6 workspace on retina display?

You can believe what you like, but it won't change the truth.
CS6 is a Cocoa application, and Retina support requires Carbon (or the other way around, I'm a Windows user). It's not a matter of adding a few lines of code to make the change, it required rewriting the entire program from the ground up.

[svn:bz-trunk] 20582: Add support for destination-include directory-path=" mydir"/ .

Revision: 20582
Revision: 20582
Author: [email protected]
Date: 2011-03-03 12:35:14 -0800 (Thu, 03 Mar 2011)
Log Message:
Add support for <destination-include directory-path="mydir"/>.
This will process each file ending in ".xml" as an individual <destination-include file-path=""/> element, allowing a web application to define a directory of destination configuration snippets.
Added a new API to ConfigurationFileResolver.java: getFiles(String dir).
This returns a list of XML files contained in this directory relative to the current configuration file.
Updated both the ServletResourceResolver and the LocalFileResolver with implementations.
Modified Paths:
 blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationConstants.java
 blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationFileResolver.java
 blazeds/trunk/modules/common/src/flex/messaging/config/LocalFileResolver.java
 blazeds/trunk/modules/core/src/flex/messaging/config/ServerConfigurationParser.java
 blazeds/trunk/modules/core/src/flex/messaging/config/ServletResourceResolver.java

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

10.4.7 Adds Support for Verizon/Sprint EVDO Cards

Mac OS X 10.4.7 Adds support for the following EVDO Cards:
- Novatel 620 (Verizon V620, Sprint S620)
- Sierra AirCard 580 (Verizon & Sprint)
- PC5220 (already was supported in 10.3.5, adds support for PC5220 new firmware)
Lots more information and screenshots at:
http://www.evdoinfo.com/TheNews/Latest_News/Apple_Adds_EVDO_Card_Support_in_10.4.720060627772/
G5 Dual 2.5 GHZ, PowerBook G4 15 inch Mac OS X (10.4.6)

If this is correct, then when I get my Merlin S620, all I need to do is pop it into my 17" Powerbook and I'm good to go??!?!?! If so, then WOOOOOOOOOOTTT! However, I am not getting an unlocked card...will I still need to go through a PC to unlock it? What are the steps?

HT201071 Please add support for Camera RAW Canon PowerShot G2

Please add support for Camera RAW Canon PowerShot G2,
it may be ancient, but there are still a lot of G2s out there, and it's annoying to have a different workflow for pictures from them...
best,
case

You are not writing to Apple here. This is a user to user help forum.
Instead, send your comments or suggestions directly to Apple via Mac OS X Feedback.
You are unlikely to get a direct response from your "Fedback", but you can be certain that the responsible Apple people will see your input for consideration in future product development.

To Bentley Wolfe, Adobe, re: Locked [ADOBE FYI] : Getting Support for Flash Player 10 and Issue Tracking post

Hi Bentley,
I wanted to tell you that an important link you posted does
not work and says "Sorry, this page is not available".
It is in your post entitled "Locked [ADOBE FYI] : Getting
Support for Flash Player 10 and Issue Tracking post", and is at
http://www.adobe.com/cfusion/webforums/forum/messageview.cfmforumid=44&catid=184&threadid= 1400586&enterthread=y.
The link that is non-functional is "If you have issues
installing Flash Player 10, first troubleshoot your issues using
http://www.adobe.com/support/flashplayer.
Read the technotes, do some testing.".
I just wanted you to know, since you have gone to all of the
effort of posting it. I apologize for having to start a new thread,
but I was unable to post to your thread, since it is locked and
read-only.
This is the issue I am dealing with myself, and desperately
need help with. :)
Thank you so very much,
Karen

Hi Bentley,
I just noticed something. The link that I pasted, to your
post, does not work either. I noticed why, however, and it seems to
be why the link in your original page does not work, and why the
link in my post that goes to your post does not work.
It seems to be that if a link has a period after it (i.e., if
it is at the end of a sentence), the period is incorrectly included
in the "real" link. Somehow, whatever mechanism that processes the
post has a mini bug in it.
If you go to the link that is results in "Sorry, this page is
not available", and look up into the browser address bar, you will
see the period there each time.
I just thought that I would point this out, too, so that the
web techs in charge of the workings of the forums could look into
it.
Here is the original link, without a period after it, to your
original page.
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=44&catid=184&threadid =1400586&enterthread=y
Thank you again,
Karen

Will Adobe ever add support for JPEG-XR?

Similar Messages

Maybe you are looking for