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.

Similar Messages

HT201071 Please add support for Hasselblad CFV-50

I just replaced my Hasselblad CFV-16 with the CFV-50, and now I have bad redish view only of my files both in Preview and Aperture.
Please add support for the file format from CFV-50, it's not a all new Digital Back (it's out since severals years now).
We can still convert files into DNG using Hasseblad tools and made the DNG file reconized by Preview and Aperture, but would like to be able to manage my original RAW files from Hasselblad in Aperture like I was used to do

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

Can you please add support for Gmail's archive feature?

Can you please add support for Gmail's archive feature? I would like to be able to "archive" emails using the menu when I'm accessing my gmail account, reading and browsing emails. I would also like "archived" emails to be removed from the email listing once I tap the refresh option on the menu. Could you tell Blackberry to implement these features on the next update?

hello, you can do this in current versions already :))
for detail please see [[How to clear the Firefox cache]]

Pse 13 support for camera raw 8.6

Does pse 13 support camera raw 8.6 for lumix dmc fz1000?

Hi
Thank you for posting to forums.
Yes, it should support the lumix dmc fz1000.
You can check the list of supported camera for Camera RAW plugin from the below link
Camera Raw plug-in | Supported cameras
Thanks
Parth Vyas

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

Lack of support for Camera Raw plugin for Mac 10.6.8

I'm hoping to find some solutions to the road block I've run into.    I'd been using Photoshop CS6 with Mac OS 10.6.8 without any problems.
Then I got a new camera this week, and that's when the problems began.....
I wanted to edit the raw files (R2W format) from the Panasonic GH4, and needed to install the proper Camera Raw plugin.   I installed version 8.6, and not only did Photoshop refuse to acknowledge the installed plugin, but it was no long able to open ANY digital photograph.
I tried installing version 8.5, as well as removing various preference files, repairing permissions, rebuilding volumes (via DIsc Warrior + Drive Geinus) and all sorts of other suggestions I found online.   I was really hoping that a manual drag + drop of the plugin to the Library/Application Support/Adobe/Plug-Ins/CC/File Formats folder would do the trick, but NOTHING seemed to work for me. I spent most of the day on Thursday trying to figure a solution, and wound up going back to my original Camera Raw plugin (version 8.3) just to be able to use Photoshop again.
I would have liked to have used the DNG Converter, but it doesn't work with Mac OS 10.6.8 either.
There's various reasons why I continue to use 10.6.8 as my primary OS - so many of my OTHER favorite softwares were radically changed or eliminated with the so-called "upgrades" and I really hate the way so many things were altered in what should be simple navigation in the Finder. I do have OS 10.8 installed on a backup hard drive, but I really don't want to use this as my primary OS.... at least not at this point in time.
So here's my plea ...
Adobe -
PLEASE give me an updated version of the Camera Raw plugin that I can use with Photoshop CS6 under Mac OS 10.6.8.
PLEASE provide a version of DNG Converter that will also work with that particular set-up.
.... or help me find a solution so I can install these plugins without the massive headaches.

You can hook up the external 10.8 drive, boot into it, run the DNG 8.5 converter there pointing it to your raw files folder, boot back to the 10.6.8 system and you should have DNGs that will open in ACR 8.3
Gene

Please add support for Lumix DMC-LX1

I've had this excellent camera for a few months and am frustrated I can't use its RAW files with Aperture.
At least I can use it with Lightroom and Photoshop CS2, but I want to use Aperture. I sincerely hope cameras are added to Aperture at least as quickly as Adobe can add them.

I doubt you will have much luck here. I wish support for my Konica Minolta A200 would be added but there is little hope now Konica Minolta have left the market.
One of Apple's main shortcomings in this area is their lack of RAW support. This will probally lead Adobe to have the upper hand with RAW processing as they support 100s more cameras than Apple do!

Please add support for Tiles

I have been looking on other lists and sites and this seems to be a big missing piece of both JSC and JSF -> the ability to template the layout of pages.
As a Struts developer, I find creating page templates in Tiles, them being able to reuse, inhertit from and tweak with only a few lines of XML in the tiles-def.xml and incredibly powerful and time saving tool. Yet apart form some clever us of prelude and coda in a few demo apps (Bookstore6 from the J2EE14 Tutorial), ther seems to be little support for this in either the IDE or the spec.
I realize that JSF is about components, but layout is just as important.
Any kind of page layout templating support would be appreciated - it doesn't have to be Tiles but it would be nice.
In the mean time, has anyone come up with workarounds for this?
M

JSF does support the use of Struts-Tiles, but Sun Java Studio Creator does not. I've tried using Tiles within Creator, but it will not allow me to modify the included JSP pages properly. For example, when I remove the html, body, and f:view tags from the page to be included, Creator automatically re-adds them, resulting in broken functionality.
The lack of templating support is rather distressing and is one reason I am holding off on using Creator to create production code. For now, it's more of a play thing.
Templating support is a must!

Cover.jpg - *PLEASE* add support for it!

I know importation of album art has been covered many times so please accept my apologies for starting yet another thread however there seems to be little discussion of the "cover.jpg" method for associating album tracks with the associated cover art imagery.
Placing a file called "cover.jpg" in each album directory is fairly common practice with many (most?) media servers and works perfectly well, consequently I have no intention of adding embedded cover art jpg's to every track in my library (10,000+ tracks) just so that my N85 can show me an album cover.
It would be so much easier for us users (you know, Nokia customers) if the S60 media player could identify the cover.jpg file that sits in every album directory I have so far synced over to my N85, and then import those cover.jpg files as the album art for each album. Also, the cover.jpg files should then NOT appear in my photo gallery.
Is this really so difficult to make happen??? Not supporting this feature seems to be the cause of so much aggravation for Nokia customers when transferring files to Nokia devices.
BTW, I'm not suggesting that embedded cover art should be ignored - if it's there then use it but when it's not present then also look for the cover.jpg file as an alternative source...

05-Jan-2009 11:47 AM
shayesta wrote:
nokia are not going to bother with cover.jpg that can be loaded from each folder depending on what track you play. only SE do support that. i think embedded album art is waybetter than seperate jpgs in each folder.
The trouble is some people already have music collections with thousands of songs, and don't want to add a 30KB image to each song just because Nokia are too stupid/too lazy/too arrogant to implement a simple solution to what is very obviously a common problem. SE implemented the solution because it's not difficult and it's what their users want - why can't Nokia give users what they want for goodness sake?
I can put over 1500 tracks or ~150 albums on my N85, and if I add a 30-35KB jpg image to each and every track that's 52MB wasted rather than the 5MB it would take to store one album cover image with every album directory. It's not rocket science.
I don't disagree that supporting embedded album art is a handy feature, but it's embedded album art is certainly not common with those who have music collections dating back more than a few years, nor is it desirable for many people. Adding album art retrospectively to an entire music collection in order to view a picture on a Nokia ain't going to happen either - I'd rather buy a consumer-friendly SE phone next time.

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 using Slim Server with ITunes

I just purchased a SqueezeBox and it awesome! However, it uses Slim Server to stream music to it, and all the cool songs I purchased on Itunes are not available due to the DRM (I hate DRM!). I purchased these songs, they live on the Mac, and all I want to do is stream them to this slim device and listen to them. This should be allowed.
Thank you.
Mac OS X (10.4.6)

Apple has not to date licensed their DRM to anyone other than Morotola (for inclusion in a couple of phones), so it's not likely to happen anytime soon, if ever.
BTW, we're just your fellow users here. Feedback to Apple is best submitted through the feedback pages. For feedback on iTunes itself, use the Mac OS X feedback; the iTunes feedback is just at this point for suggesting new content to the iTunes Music Store.

Aperture support for unsupported raw formats

I was doing some tests with Aperture to see if it could fit my workflow. My concern was support of old files from a Nikon Coolpix 5400, raw (thanks to firmware update at the time) as well as a recent Nikon DSLR. No problem with the DSLR. 5400 was not supported. After some internet research I found out there is a pref file (Raw.plist in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources) that has info about all supported cameras. This add raw support for the cameras listed in the file for Preview, iPhoto, Aperture (system-wide). Same list that Apple provides as camera compatibility list.
In that list I chose to duplicate the NIKON-E8400 array and renamed it NIKON-E5400. Didn't change any value in the array. To my surprise, even without rebooting, this added support for the Nikon Coolpix 5400 images. The image looks pretty much the same with these default settings (when opened in Preview for example) than it does in ACR in CS2. The only odd difference is the image size loosing 10 vertical pixels (from 2592x1944 opened in ACR CS2 to 2592x1934). I have no idea why it does this but it is no big deal really as it is no scaling, just loss of pixels.
I am a bit concerned of course about the possibility to carry on this tweak in the next OS updates.
I guess any raw from any camera could have support this way.
Just need to name the array in Raw.plist properly. For mine I just opened a raw in text edit and saw first line the name of camera, was "NIKONE5400". I compared the format of this name to other names in the array and decided to add the "-" to look like others so "NIKON-E5400", and that was it. Now I was lucky the default setting for the 8400 I used as a base worked for the 5400, apparently. It could have not been the case and then I would have had to play with the values in the array. Quite a few so a long process I am afraid, but possible.
The deal would be to release a little utility software that would let us play with these values easily and see a result live on a sample image, and once satisfied it would modify this Raw.plist file. This way people could add support to their own raws.
If anyone in the know sees a big issue in doing what I did please tell.
Of course playing with this Raw.plist file is at your own risks so keep backup and bee careful.
The tweaking of this raw.plist file had been talked about in different forum in the past concerning the support of Canon 3xxD that had a different US name Rebel something. The change of name of the corresponding array added support before an OS update did it for everyone.

I also modified my Raw.plist file to import RAW files from my Olympus C-5050Z. But that doesn't make Aperture import a type of RAW file it didn't support before. It just turns out that your Nikon 5400 RAW files are the same format as the Nikon 8400 files except for size, just as my Olympus C-5050 files are substantially similar to the Olympus C-7070 files. I think the Raw.plist file used by ImageIO contains hints on how to treat the data and color in the images and as long as the cameras don't behave too differently, substituting one model with another will work.
The RAW.plist file is a standard plist file that can be examined and modified with the Property List Editor. What I would like to see is documentation of the parameters so that we can more easily add support for cameras that aren't supported out of the box.
MacBook Pro Mac OS X (10.4.7) 2.16GHz 2GB RAM 256VRAM

Add support for custom xmp panels

Please add support for custom xmp panels.
Thanks

I would strongly support that too!!!
Here is why: We have been working at an XMP implementation of the Darwin Core to support standardized metadata on biodiversity information. Have a look here. I would love to have an Panel in Lightroom to support the metadata that I am embedding with IDImager:
http://wiki.idimager.com/index.php?title=DarwinCoreXMP#.27.27.27Darwin_Core_XMP.27.27.27
Cheers,
Frank

Just got a Canon G7 x only to find that lightroom 5 and PS6 don't support the camera RAW that it produces. Tried the Camera raw 8.7 and that didn't help. Will there be an update that includes this camera?

Just got a Canon G7 x only to find that lightroom 5 and PS6 don't support the camera RAW that it produces. Tried the Camera raw 8.7 and that didn't help. Will there be an update that includes this camera?

I'm sure there will be support for the camera eventually. But Adobe never announces that information in advance. It's possible that it could be added to the 8.7 final release and to the next update of Lightroom. But that depends on the timeline and if the engineers were able to get the camera in time to create profiles. You'll just have to wait and see.

I'm trying to find the plugin for camera raw, but all I can find is the page with the cameras that are supported. But I don't find how to find and install the actual plugin. The end name is ARW

I'm trying to find the plugin for camera raw, but all I can find is the page with the cameras that are supported. But I don't find how to find and install the actual plugin. The end name is ARW, and all I need is to find WHERE I can download it. Thanks.

cr is installed by updating your app. use help>update, or update manually
pre cc updates: http://www.adobe.com/downloads/updates/
cc updates: http://prodesigntools.com/adobe-cc-updates-direct-links-windows.html
cc 2104 updates: http://prodesigntools.com/adobe-cc-2014-updates-links-windows.html

HT201071 Please add support for Camera RAW Canon PowerShot G2

Similar Messages

Maybe you are looking for