Camera Image Format

What are the image formats taken by the blackberry camera?

I believe it's just .jpeg.
I hope that helps you.
- If my response has helped you, please click "Options" beside my post and mark it as solved. Clicking the "thumbs up" icon near the bottom of my response would also be appreciated.

Similar Messages

Unsupported Image Format when inporting from my new Canon 400D (KISS X) CAM

Could someone please tell me why Apeture is giving me the Unsupported Image Format notice when trying to view and import Raw images from my new Canon 400D camera? I can view the photos on my Canon software. Is it possible that just becase the file is 10.1 MP on my new cam instead of the 8mp that my rebel XT (350D) was that Apeture can not use the format? If in fact this is the case, what can i do to get the 300 plus photos that I just shot at a paid photo shoot into Apertue and still be able to work with them raw?
I would be grateful for any help I can get.
Thank you.
Stan

Two problems with this workflow:
1) A 16 bit TIFF file is 52 megabytes. Ouch. Reading them bogs down my little MacBook like you wouldn't believe. I may have to work with JPEG or, god forbid, use Photoshop until Apple's devs can get support for the XTi
2) Aperture seems unable to figure out the colour balance of the TIFF files. I added a bit of saturation and colour correction (working in the Adobe RGB space) in Canon DPP, but Aperture seems to totally screw up on these files. http://images.dasmegabyte.org/wine_tour/large-37.html almost no detail at all in those bins (plenty in the RAW) and I had to boost the gamma on the web gallery by 1.2x so they didn't look fire engine red.
MacBook Pro Mac OS X (10.4.8)

Camera RAW support 2.2 update and Nikon .NEF unsupported image format

Hi,
I Use a Nikon D2x and only take raw images (.NEF file)
After I update from RAW support 2.1.1 update to RAW support 2.2 update, all my raw image file (.NEF file) taken before 13th September 2006 ! would not display - In the Aperture program, if i navigate to a project / folder and clicked on a thumb nail in the browser, I get a magenta / cyan screen showing in the main viewer panel with unsupported image format. ?
This is my worst-case scenario ! - I have entrusted Aperture with all my digital images (all raw .NEF) images taken before 13th September 2006 are un accessible with camera RAW support 2.2 update installed !
I have deleted (the 2.2 update) “from” System/Library/CoreServices/RawCamera.bundle and reinstall the RAW support 2.1.1 update.
* NOW I can now see all my raw Nikon .NEF images and they are now all fully functional again *.
Their is a problem with the Apple digital camera RAW support 2.2 update, it rendered the Aperture program useless to me for my older .NEF image/files (as above).
This requires a fix ASAP
Martin

Thankfully, I wasn't affected by the issue given I'm currently with Canon. There have been Canon woes in the past though.
On a side note, I never update anything until it has been out for a few weeks just to be sure. Because Aperture is such an integral component of my studio and business, I make sure everything always works before making any updates or changes - including upgrading cameras.
I'm sure the next update will fix the magenta issues.
Best,
CD

"Unsupported Image Format" all of a sudden, with previously workable files

Folks,
I've got an issue that seems very strange indeed.
Months ago, I bought a Pentax K20D. I also bought a 17" MacBook Pro and Aperture. Camera and Aperture played well together.
I encountered the known issue with white spots on the image when using the 2-second timer for long exposures. I read about how the Pentax firmware update 1.01 changed the EXIF Make information, causing Aperture to be unable to read the K20D PEF RAWs. So I waited.
When Aperture 2.1.1 was released (and I think the Apple RAW update), I installed both of those. When I heard through this forum that the updates fixed the problem, I also updated my camera's firmware and confirmed that it worked.
So smooth sailing for a few months on Aperture 2.1.1, OS 10.5.3 (or .4, I forget), and K20D firmware 1.01.
Then I bought a Mac Pro 8-Core with 10.5.4 on it. I sold the 17" MacBook Pro. I used the Migration Wizard to move my user account from one machine to the other, but did a fresh install of all applications. (I've been an Apple tech for the past 7 years, and have various certifications. I know the user transfer process isn't perfect, but it should have the following results... read on)
Now, in Aperture 2.1.1 on 10.5.4 with all updates, PEF RAWs taken with K20D firmware 1.01 that were previously edited, manipulated, etc just fine on my MacBook Pro say "Unsupported Image Format" in a big reddish-black box when I try to view the master. If I switch to Quick Preview, it displays just fine, but is un-adjustable. Additionally, any NEW images I copy from my K20D show in the Import window as being 0x0 pixels (or occasionally 160x120 pixels) and will only show a tiny preview or "Unsupported Image Format." All PEF RAWs taken with K20D firmware 1.0 are just fine.
So here's what I've done:
1) Tested a fresh install of 10.5.4 on another HD in the Mac Pro. Installed Aperture 2.1, updated to 2.1.1. This should be perfectly clean. It gives the "Unsupported Image Format" error with any new images from my K20D. Copying the library from my other partition gives the same problems as described earlier.
2) Tested a fresh install of 10.5.3 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. Applied the Apple RAW update and iLife enhancements. It gives the same errors as before.
3) Tested a fresh install of 10.4.11 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. This worked perfectly for all PEFs and DNGs.
4) Took a month-old backup (from when everything was working just fine) of my Aperture Library and loaded it into all of the above configurations. Same results!
So what is the deal here? Aperture all of a sudden can't read images that it itself was able to edit a month ago? How come it works just fine in 10.4.11? This seems really messy. I have essentially lost a lot of the work I've put in.
I can use DNGs moving forward, but my past work is now messed up, and the DNGs are almost 75% bigger than the PEFs!
Anyone have any ideas for resolution or should I just call Apple?
Message was edited by: MonsieurBon

If it's any consolation, I had the EXACT same problem today; just opened Aperture 2 and my entire library of images shows "unsupported image format' -- the thumbnails are still intact but clicking on any image suddenly shows the red screen.
Same situation, these images were previously editable and accessible. We had a power outage an hour ago and initially I thought my library had crashed, but I was not actually using Aperture 2 at the time of the outage so I don't think that's the case.
Given the relatively sparse attention Apple gives to these forums, I don't expect there will be a quick response.
I have Leopard 10.5.4 installed, I don't have access to another version of the OS to see if I can get it work. If I'm not mistaken, wasn't there a series of Software Updates recently? I click on these without really checking the apps that are affected; could Aperture have been one of the apps 'revised' by the recent update?

PDF image format?

From what I understand, the PDF file format can contain text, vector graphics and raster graphics in many different formats. When I print to a PDF (via Save as PDF... in the print dialog box), what type of image format is actually used inside the PDF (which I assume is just a container format, really)?
Say I come across a full quality RAW file from a 10-megapixel camera. If I open that image in an image editor and then print it as a PDF, what ends up in the PDF file? Is it a JPEG? A PNG? Some type of otherwise unknown lossless format?
I assume the screenshot mechanism in OS X that saves to PDF uses similar technology. In that case, is a screenshot saved as a PDF better or worse quality than a PNG or JPEG (using a utility like TinkerTool to change the default screenshot format)?

Actually, it doesn't matter what you set on a folio level. The article settings override the folio settings. The folio settings are supposed to appear as the default when you create articles, but it doesn't work that way at this time.

Canon EOS 350D .CR2 pics still 'unsupported image format'?

I was releaved to see updates in Mac OS X (10.4.8) and Aperture 1.5 the other week, hoping it would solve my problem, being able to finally work with my RAW files (.cr2) from the Canon EOS 350D (yes, being in Europe these days).
I followed the posts on the forum throughout the summer, which recommended waiting for the next OS X update (which should support the camera in that raw definition file) and I didn't want to use the workaround, which clearly had problems with the colors on the pics.
After all the updates the other week, nothing has changed on my MBP. Still the 'Unsupported Image Format' on my RAW files. On the other hand, I don't see any posts on problems with the 350D camera anymore as well (only on CR2 files in general).
Am I missing something really basic here (tried rebuild library)? Or, have all the CR2 formats gone down the drain on Aperture 1.5?
Any help is appreciated, as I have already looked into Adobe Lightroom Beta and although I don't want to switch, the files seem to work there...

Yes, the import thumbnail is as you describe, the low res. JPG that is embedded in the RAW wrapper.
10.4.8 needs to be installed prior to Aperture 1.5 .... from a functionality point of view. I am not aware of a dependence that says AP 1.5 has to be uninstalled before a 10.4.8 upgrade or any such, not that AP 1.5 should need re-installing after a 10.4.8 upgrade .... assuming it was working correctly beforehand.
But to this last point, since you have an issue which may be related to AP or OS X, it is likely worthwhile updating both and in order.
Final thought. do you import directly from the CF card / camera vs. using an intermediary tool such as ImageBrowser or DP Professional? I am wondering if Aperture is very OCD aboout the image format wrapper and chokes at the least excuse that other apps. and tools ignore.
G.

Image cannot be rendered because Aperture does not support image format

Dear all,
I have installed apple Aperture 3.03 and the complete Nick software plug-in selection:
• Dfine 2.0 for Aperture
• Color Efex Pro 3.0 Complete for Aperture
• Silver Efex Pro for Aperture
• Sharpener Pro 3.0 for Aperture
• Viveza 2 for Aperture
History
Until a few days ago the system was running ok / no notable issues on performance. / all pug in seem to run good / no issues. Also
• I Run OSX10.4/ Aperture 3.03 ( 32Bit mode)
• My library contains just over 10000 images / approximately 140GB
• I have recently updated the OSX software update including the security update 2010-005
• as well as the Snow leopard graphic update 1.0
• As far as I am aware all updates where automatically recommended by OSX Software update ( no manual intervention).
• As far as I remember after update the system still was running ok but honestly I can not tell you how many times the Nick Plug in started out of Aperture.
After all, Several times I continued using the system / still no noticeable problem until the following was happening:
Problem:
After creating with "PT gui" a panoramic image File type: "TIF" Pixel size: 5112 × 2556 (13,1 MP) I imputed this file in to Aperture (drag and drop). During the attempt to eddied this file with "Nick Define 2.0" the system was hamming up No response for several minutes from Dfine 2.0 / Aperture" At the end I had to "force quit" the applications.
After the consequential reopening of Aperture I tried again to eddied images with any Nick software Plug-In but each time Aperture prepares any image previously stored in my Library ti open the Pug in the following Error message appears:
*"This image cannot be rendered for editing because Aperture does not support the image format"*
Currently non of my previously in the library safed images can be opened in a Nick software Plug-In this applies to all file types I have tied " Raw, tif, jpg"
• I am still able to eddied normally with Aperture ( so far I do not find any other issue)
• A newly imported Raw image after being taken with my EOS 5D can be edited in the completed Nick software Plug-In selection ( so far I do not find any other issue)
The following actions have been taken to overcome the issue (all not successful):
• I restored my Library out of my back Up ( to previous time of event ( no Time machine back up)
• Uninstallation of all Nick software Plug-In selection
• Uninstallation Aperture Reinstallation Aperture / Nick software Plug-In selection
• Repairing the library ( all three possibilities)
• installation of latest EOS utilitys
Questions
• Can you support me to overcome this issue?
• Have you heard similar issues of Nick user Running the Aperture plug-ins?
For me it is really strange that even after replacing the the library in my normally not connect back up the problem still exists (this should be not affected by the event as the back up was not done any more) / new imported images are editable with the Plug-In.
I would be happy if you could support me in this issue.
Best regards,
Matthias
PS: I have reported this issue to Apple (via Aperture feedback) as well as contacted the Nick software support and currently waiting for feedback.
Harware:
Modellname: MacBook Pro
Modell-Identifizierung: MacBookPro5,1
Prozessortyp: Intel Core 2 Duo
Prozessorgeschwindigkeit: 2,66 GHz
Anzahl der Prozessoren: 1
Gesamtzahl der Kerne: 2
L2-Cache: 6 MB
Speicher: 4 GB
Busgeschwindigkeit: 1,07 GHz
Boot-ROM-Version: MBP51.007E.B05
SMC-Version (System): 1.41f2

Dear Ma-Le / All
I have just had the same problem
I use
• Aperture 3.03 with a iMac 2.8 Intel Core 2 Duo with all files on external hard disks (mac extended fomat as apple suggests) with referenced masters.
• Camera Nikon D300, with probably 75,000+ images on 2 hard drives
• Photoshop CS2 with PhotoTools 2.5 plugin
This has been working perfectly until yesterday when the system froze when I was using PhotoTools 2.5 with Photoshop CS2 - as a result of which I resorted to a force quit.
Since then on most of my files it has not been possible to use an external editor.
A message appears saying: *Editing Error - This image cannot be rendered for editing because Aperture does not support image format*.
The problem seems to apply to the attempted use of any external editor (including Noise Ninja)
The following have each been tried, all unsuccessfully:
- Using each of Aperture's library 3 first aid options
- Rebuilding directory using Diskwarrior
- Checking for virus using Virus Barrier X4
- Defragmenting library hard disk using TechTool pro
- Changing permissions settings
- Using Disk Utility first aid to repair permissions and checking main disk
- Removing some plist elements when open 'show package contents' of library
- Setting up a(n almost clean) new system, with newly loaded version of Aperture, with a new library from a vault saved prior to the crash when the problem first occured
Several things seem to me to be totally bizarre:
1 - The problem is the same on the other library hard disk which was not in use at the time
2 - The problem still occurs when a back up vault saved prior to this problem is loaded - using a new hard disk with a new system and a newly reloaded and upgraded Aperture software
3- The problem seems inconsistent. It appears to affect some photos but not all. Even from the same shoot, some photos can be edited using an external editor, whilst others cannot (but as far as i can tell most of the photos in a particular album seem to be consistently affected)
4- The only way around it seems to be if I import a new (copy image) from the original master. Then everything works ok, and I can successfully edit that copy image in photoshop / phototools plug-in.
I am beginning to wonder whether what has been corrupted is Aperture's ability to make copies from the master file which it then uses with the external editor (I have no real idea whether this is correct)
Does anyone have any ideas or solutions - or has anyone else been suffering a similar problem?
Eric
PS: As a professional photographer this problem is a really serious issue for me - and I really don't really want to go to Lightroom or Capture One

Reading Camera Raw Format

I'm a user of Lightroom 5 and Photoshop CS6 runiing the current version of each. I signed up for Creative Cloud and have downloaded and installed Photoshop CC. I have not downloaded and installed Lightroom from CC as I understand it is the exact same product as the standalone version.
My question is - everytime I take a photo (DNG) from Lightroom and click to edit it in Photoshop CC - Photoshop CC opens a dialog box that says 'Reading Camera Raw Format' That didn't happen when I opened images in CS6. What causes this and how do I fix it?
I have checked with a friend who also converted to Photoshop CC and he does not get that dialog (he is running Windows and I'm on a Mac)?

Since you say you are up-to-date with LR an PS, this suggests you are using LR 5.2 and PS-CC/ACR 8.2.
Whenever the versions of LR and ACR are compatible, then LR tells PS to open the raw file using LR’s settings, and PS uses the ACR plug-in to open the raw file with those settings.
The message occurs when the time it takes to render the raw file on the way into PS longer than a certain amount of time.
If your LR and CS6-ACR were up-to-date and you weren’t seeing the message, then perhaps something was slightly faster with those two products, and the message wasn’t displayed, or perhaps PS-CC’s time-limit for showing that message was made a shorter amount of time.
If your LR and CS6-ACR weren’t synchronized in their versions (e.g. LR 5.2 and CS6-ACF 7.1) then LR could have been rendering the file as a TIF or PSD so PS isn’t using ACR to render the file.
As far as LR-non-CC and LR-CC being the same. They operate on images files the same, the real difference will occur with LR 6, which you won’t have to pay extra for if you’re using the CC version.
There isn’t any reason to download and install LR-CC 5.2 when you already have the regular LR 5.2, but once LR 5.3 comes out, you might as well let CC download and install it, so you won’t have to worry about it, later. It may be that you’ll have to uninstall LR non-CC 5.2, but perhaps that has been changed in recent updates of the CC Manager app or will be when LR 5.3 is release in the next few weeks.

Aperture 3 and DNGs from LX5 raw files: unsupported image format

My LX5 arrived, and I tried converting a raw file to DNG with Adobe DNG Converter 6.2.0.21 beta and importing it into Aperture. No luck: Aperture says it's an unsupported image format. I tried setting the compatibility as far back as possible in the preferences, and still no luck. Any idea why this doesn't work? I used Adobe DNG Converter multiple times to work with raw files from unsupported cameras, so it's a real surprise to get the unsupported image file message.
—Andreas

Unfortunately, this is more about Apple dragging its feet than a cutting edge issue. I got an LX3 and upgraded to Aperture 3 in February of this year. RW2s straight out of the camera always imported just fine. However, I've never been able to get a DNG generated from an RW2 with Adobe DNG converter to work. Interestingly, DNGs from another file format I use (PEF) work fine in Aperture.
I submitted a issue report to Apple about the RW2 to DNG problem back in March, and like so many other suggestions to them, it seems to have vanished into the ether.

10.5.2; Canon 1DsM3 Raw Files = "Unsupported Image Format" in Aperture

Just did the update and pointed Aperture to a folder of Canon 1Ds Mark III raw files (standard raw files, no sRaw or anything like that). Thumbnail previews are grey and Viewer says, "Unsupported Image Format".
Tried rebooting and verifying/fixing permissions. No help. No thumbnails, no images in Aperture.
Canon 1Ds Mark III raw files do show fine in the finder and in Quick Look.
Message was edited by: Jon Roemer

I have the same exact issue.
I do get the same error with 1Ds MIII raws.
Also the G9 raws are not working.
Finally after 3 months it's still not working
I could imagine that there is the need to edit some property file (like I have read before in the forum somewere) to add the new cameras to the list of supported cameras.
Are the D3, D300 raws working?

HT4007 I Just updated Apeture to 3.3.2 Now there are some photos that I receive a message..."Unsupported Image Format" Are there lost? can I retrieve them? can I change the format? Help...?!?

I just updates Apeture to version 3.3.2 after installing Mountain Lion. There are some photos in Apeture that now say, "Umsupported Image Format". Are these lost? Can I retrieve them...how? Can I change the format so that I can see them again? Help?!?

Are these images "Raw" images? What is the make of your camera?
Check the version of the Digital Camera RAW Compatibility Update that is installed. The version of the raw support is shown in the About panel: from the main menu bar:
Aperture > About Aperture
Download the latest Raw Update from here:
Digital Camera RAW Compatibility Update 3.14
If you have the latest raw support installed, but Aperture does not recognize the format, try to register the raw support for your camera with the launch services db, see this post by Alan Roseman:
Re: Aperture 3 preview of raw file greenish
But also read the following post, that explain how this is supposed to work and to correct the typo in the command
In short: Quit Aperture, open the terminal, paste the follwing text in (all in one single line) and hit return; then reboot the system.
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
Regards
Leonie

Unsupported Image Format RAW (NEF) Nikon d7000 in Aperture 3, why?

I just bought a Nikon D7000. According to the Aperture 3 specs, it supports RAW (NEF) format from this camera. However, I get the message that the image format, which loads as thumbnails in the viewer, is not supported. I just downloaded the trial version of Aperture 3 (I'm not going to upgrade from my current version if it actually does NOT support this format).
I'm running OS X 10.5.8 witn 2.4G Intel Core 2 Duo 4G DDR3 memory Macbook Pro.
What other info do I need to provide to diagnose this?

Technically, you should only need to verify that you have at least the RAW Compatibility Update 3.6:
http://support.apple.com/kb/DL1357
Current version is 3.7 which can be found here:
http://support.apple.com/kb/DL1386
Note - I assume that the 3.7 would include 3.6, but am not sure.
If you already have the correct RAW support for OS X and are importing new images into a new or trial library, you might try running the 'Repair Database' option found here:
http://support.apple.com/kb/HT3805
Good luck.

HowTO: convert Image- byte[] when don't know image format?

I have byte[] field in my DB. Images have been stored there.
Images can be jpg/gif/png.
My task is to scale them and save back (to another field)
I have such code:
I know, that getScaledInstance is bad, but please, don't pay attention. This operation +(massive image resizing will be performed once a year at night)+
public class ImageResizer {
     private static byte[] resizeImage(byte[] sourceImg, int newWidth){
          byte[] result = null;
          Image resizedImage = null;     //output image
          ImageIcon imageIcon = new ImageIcon(sourceImg);     //source image
          Image imageSource = imageIcon.getImage();
          int imageSourceWidth = imageSource.getWidth(null);
          int imageSourceHeight = imageSource.getHeight(null);
          if(imageSourceWidth > newWidth){
               float scaleFactor = newWidth/imageSourceWidth;
               int newHeight = Math.round(imageSourceHeight*scaleFactor);
             resizedImage = imageSource.getScaledInstance(newWidth, newHeight,Image.SCALE_SMOOTH);
             Image temp = new ImageIcon(resizedImage).getImage();// This code ensures that all the pixels in the image are loaded.
             // Create the buffered image.
             BufferedImage bufferedImage = new BufferedImage(temp.getWidth(null), temp.getHeight(null),BufferedImage.TYPE_INT_RGB);
             /**And what next?*/
          }else{
               result = sourceImg;
          return result;
     public static byte[] scaleToSmall(byte[] sourceImg){
          return resizeImage(sourceImg, 42);
     public static byte[] scaleToBig(byte[] sourceImg){
          return resizeImage(sourceImg, 150);
     public static byte[] serializeObjectToBytearray(Object o) {
         byte[] array;
         try {
           ByteArrayOutputStream baos = new ByteArrayOutputStream();
           ObjectOutputStream oos = new ObjectOutputStream(baos);
           oos.writeObject(o);
           array = baos.toByteArray();
         catch (IOException ioe) {
           ioe.printStackTrace();
           return null;
         return array;
}On this forum I've found many solutions, but approximately all of them suppose that I know file format (PixelGrabber, ImageIO, e.t.c). But I don't know it. I know, that it can be jpeg/gif/png.
What can I do?
I've found that simple serialization can help me (+public static byte[] serializeObjectToBytearray(Object o)+), but seems like it doesn't work.
Edited by: Holod on 01.11.2008 10:18

Here I came up with one possible solution using some more functionality of ImageIO.
public class ImageResizer {
    private static byte[] resizeImage(byte[] sourceBytes, int newWidth) throws Exception {
        byte[] scaledBytes;
        // ImageIO works with Files or Streams, so convert byte[] to stream
        ByteArrayInputStream byteArrayInputStream = new ByteArrayInputStream(sourceBytes);
        // Why not just use ImageIO.read(inputStream)? - Because there would be
        // no way to know the original image format (I am assuming here that
        // you need to write back the image in the same format as the original)
        ImageInputStream imageInputStream = ImageIO.createImageInputStream(byteArrayInputStream);
        // assuming there is at least one ImageReader able to read the image
        ImageReader imageReader = ImageIO.getImageReaders(imageInputStream).next();
        // save image format name so we can write it back in the same format
        String formatName = imageReader.getFormatName();
        imageReader.setInput(imageInputStream);
        BufferedImage sourceImage = imageReader.read(0);
        int imageSourceWidth = sourceImage.getWidth();
        int imageSourceHeight = sourceImage.getHeight();
        if (imageSourceWidth > newWidth) {
            // be careful with integer divisions ( 500 / 1000 = 0!)
            double scaleFactor = (double) newWidth / (double) imageSourceWidth;
            int newHeight = (int) Math.round(imageSourceHeight * scaleFactor);
            System.out.println("newWidth=" + newWidth + ", newHeight=" + newHeight + ", formatName=" + formatName);
            // getScaledInstance provides the best downscaling quality but is
            // orders of magnitude slower than the alternatives
            // since you're saying performance is not issue, I leave it as is
            Image scaledImage = sourceImage.getScaledInstance(newWidth, newHeight, Image.SCALE_SMOOTH);
            // Unfortunately we need a RenderedImage to use ImageIO.write.
            // So the next lines convert whatever type of Image was returned
            // by getScaledImage into a BufferedImage.
            // Using TYPE_INT_ARGB so potential alpha channels are preserved
            BufferedImage scaledBufferedImage = new BufferedImage(newWidth, newHeight, BufferedImage.TYPE_INT_ARGB);
            Graphics2D g2 = scaledBufferedImage.createGraphics();
            g2.drawImage(scaledImage, 0, 0, null);
            g2.dispose();
            // Now use ImageIO.write to encode the image back into a byte[],
            // using the same image format
            ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream();
            ImageIO.write(scaledBufferedImage, formatName, byteArrayOutputStream);
            scaledBytes = byteArrayOutputStream.toByteArray();
        } else {
            // if not scaling happened, just return the original byte[]
            scaledBytes = sourceBytes;
        return scaledBytes;
    public static void main(String[] args) throws Exception {
        // this is just for my own local testing
        // simulate byte[] input from database
        BufferedImage image = ImageIO.read(new File("input.jpg"));
        ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream();
        ImageIO.write(image, "PNG", byteArrayOutputStream);
        byte[] sourceBytes = byteArrayOutputStream.toByteArray();
        byte[] scaledBytes = resizeImage(sourceBytes, 640);
        // write out again to check result
        ByteArrayInputStream byteArrayInputStream = new ByteArrayInputStream(scaledBytes);
        image = ImageIO.read(byteArrayInputStream);
        ImageIO.write(image, "PNG", new File("output.jpg"));
}

HT3946 Unsupported image format

I've been getting a message "This photo was adjusted using an earlier version of APPLE RAW processing" unsupported image format and it's been doing this to photos I took today and my older one's any advice on how to fix this?

What is the make of your camera? This problem has occured recently mostly for Lumix and Nikon cameras:
First try, if reprocessing the images will help:
See this section of the user manual on how to do this for selected images:
Reprocessing Images from Previous Versions of Aperture
If this does not help, you may need to register your camera with the the launch service database again, see this post by Alan Roseman:, Re: Aperture 3 preview of raw file greenish
There is a "typo" in the command given in the link above, so read also the following posts on how to correctly enter the command and how the fix is supposed to work
Regards
Léonie

Why do G3 raw files show as "Unsupported Image Format" in Aperture?

I am moving towards shooting in raw, and as an experiment I imported some sample raw files from the publicly available text images on the Photography Blog. When I try to look at these images, I get a black screen with a warning triangle and the message "Unsupported Image Format". This happens for all the different raws, including some G3 raw files (.rw2). Oddly, it can read the EXIF metadata and has all the information about shooting settings etc. If I import the same files into iPhoto, it displays the images properly and allows editing, etc.
I have a workaround, which I've also tried with my Fuji X10 raws (still not supported on MacOSX), of running them through the Adobe DNG converter, and then looking at the dng files which seem to work fine. But it's a pain.
This has to be one of those simple "D'oh" things, but I can't see what I'm doing wrong!

Thanks Leonie, the second part revealed that I have been an idiot, although the behaviour is still surprising. The folder has a mix of DMC-G3 raws, Fuji X10 raws, and DNG files produced from both. For the Fuji X10 files, the DNGs produce images and the raws produce the "Unsupported file format" message. The latter is not surprising, the former a little surprising (as I've heard that DNGs only work when the associated raw works). The last two remarks don't directly address my problem (or perceived problem), but they perhaps set the frame for my expectations.
For the G3 files, when I look at it more closely, the G3 raws DO display correctly, while the G3 DNGs give "Unsupported file format". I had managed to fool myself into thinking it was the other way round (Aperture does rather hide the full file name).
So I was completely wrong, Aperture does support DMC-G3 raw, it's just it's DNG support that's a bit weird. However, it's on my side if I need to use X10 raws (via the DNG step). In fact so far I've given up the latter, as the noise levels are so much greater than in Fuji's in-camera JPEG conversion.
So, thanks very much for your help. Now I remember the first rule of system support: never trust what the customer tells you! (I know you're not really customer support, but I guess the same rule applies.) Thanks again

Camera Image Format

Similar Messages

Maybe you are looking for