Image format

Recently I've been getting a "unsupported image format" while downloading images from my Canon 1D. About 6 images will transfer but then I get that dialogue and a blank space where the image should be. This used to be bullet proof but now I spend more time than usual.
I have to turn off the camera, quit Aperture and restart the computer in order to resume work. I am still able to transfer images to my laptop. Does anyone have an answer for this?
Thanks,
Steve

Thanks.
It works fine without a serious performance penalty on the process. But I have found a another problem. In my application I have to download thousands of images from the server to store them in my hard drive, this means that I have to execute this piece of code thousand of following times, one for each image I want to download, in my case, if the image is "jpeg", I download it. When I execute the code several following times, the execution gets stuck when reading the image and I even lose the internet connection of the equipment. If I remove the piece of code which checks the format, everything works fine and I can download as many images as I want. Any idea of what is happening?
while (tilesIdToProcess.size()>0)
String quadKey = (String)tilesIdToProcess.remove(0);
url_request = String.format(REQUEST, args[3], args[4], quadKey, args[5]);
URL url = new URL(url_request);
//Check image format
ImageInputStream iis = ImageIO.createImageInputStream(url.openStream());
Iterator<ImageReader> readers = ImageIO.getImageReaders(iis);
String format = "";
while (readers.hasNext()) {
ImageReader read = readers.next();
format = read.getFormatName();
iis.close();
//Download and save image if "jpeg"
if (format.equals("JPEG"))
Image image = ImageIO.read(url);      //Image is downloaded, after several loops, the execution gets stuck here.
String dstPath = dst + type + "/" + layer + "/" + projection + "/" + getPathFromQuadKey(quadKey);
File folder;
folder = new File( dstPath.substring(0, dstPath.lastIndexOf("/") + 1));
if (!folder.exists())
folder.mkdirs();
File file = new File(dstPath);
ImageIO.write((RenderedImage) image, "jpeg", file );
}

Similar Messages

  • How to change the bar chart rendering image format in SSRS

    Hello all,
    I am working with SQL Server 2008 R2 and I have a SSRS bar chart report, when the report got rendered over online or if the take Export (PDF and PPT), the image is in png format always, which is taking too much of time to execute the report in case of large
    data.
    Can, It be possible that the rendered image is in jpeg format instead of png.
    If Yes, please share the appropriate steps to follow:
    Thanks in advance
    Pankaj Kumar Yadav-

    Hi Pankaj067,
    According to your description, you want to change the bar chart rendering image format as JPEG format when previewing the report or exporting to a PDF file .
    In Reporting Services, the chart rendering image format is PNG by default. It’s a by-design behavior. And it doesn’t open any API for us to change the image type when exporting a chart to a format. So in your scenario, your requirement can’t be achieved
    in Reporting Services currently. I would recommend you submit a feature request to Microsoft at this site:
    https://connect.microsoft.com/SQLServer. So that we can try to modify and expand the product features based on your needs.
    If you have any question, please feel free to ask.
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • "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?

  • Firefox for Mac preferences shows .qif file format for quicken as "quicktime image format"-wrong application and won't let me select anything else

    Post to Firefox forum; Oct.2011
    Re: Quicken 2007; Mac OS 10.5
    Problem: can’t import or download Qif format files into quicken from bofa or Chase. Mac can’t recognize; how do I set preferences in Firefox (or Safari).
    https://support.mozilla.com/en-US/questions/new?product=desktop&category=d1&search=Firefox+for+Mac+preferences+shows+.qif+file+format+for+quicken+as+%22quicktime+image+format%22-wrong+application+and+won%27t+let+me+select+anything+else&showform=1
    Hello,
    I previously used Firefox on my old Mac G4 with OS 10.3.9; the above issue existed with that system and Firefox 2.00.2 (or similar). I then "tried" to move to a G5 Mac with OS 10.5, hoping that an updated Mac Operating system and updating Firefox would solve that problem.
    I'm now working on my son's MacBook Pro, OS 10.5.8, 2.4 ghz Intel Core 2 Duo; 2gb Memory; 2 gb 667 Mhz DDR2 SDRAM.
    I still have a problem in Firefox Preferences trying to download .qif files. BofA Mortgage accounts only allow downloading of .qif files. My .qfx download works fine, but the error message is as follows:
    The error message is that this is a corrupted file or one that Preview doesn't recognize.
    and it is still a problem when trying to download Quicken .qif format files for our B of A mortgage.
    The preferences for Firefox under File Helpers won't let me name the extension I want; instead, it CONFUSES .qif (Quicken Interchange Format) with .qtif (Quicktime Image Format) for Mac.
    Therefore, when I download .qif files and try to import them to Quicken, I get a message that this is a corrupted file:
    thanks for any help.
    Val in Seattle

    Well, in the end, I just gave up and deleted the photos, in the hope that it was something to do with them. Took some more photos and they seem to have imported without any problems at all.
    Given that the same irksome photos loaded on the wife's macbook without so much as a murmur, how weird is that?
    Still- all's well that ends well. Thanks for the suggestions- much appreciated.
    Matt

  • 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.

  • Mapviewer performance problem using image format FORMAT_RAW_COMPRESSED

    I am using the MapViewer.FORMAT_RAW_COMPRESSED map image in my (java) map application because some features must be clickable and as far as I can work out, this is the only way to achieve this in a Java client. On my local system, running the map server in an oc4j container, this works about as fast as using FORMAT_GIF_URL and loading the image from this url. There also doesn't seem to be much difference in memory and cpu usage.
    When I direct the request to a map server running on a remote Application Server the rendering time grows exponentially. The same maprequest using FORMAT_GIF_URL runs as fast as it does in my local OC4J container. The problem seems to be in "packing time" in RealWorker:
    Remote AS:
    Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...
    Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 99ms
    Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 5560ms
    Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 142605ms
    Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 148264ms
    Local OC4J:
    Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...
    Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 540ms
    Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 2490ms
    Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 120ms
    Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 3150
    The test server is smaller than my local system and more applications are running on the AS, generating the map takes all the available memory and cpu, but the difference between the time it takes generating a GIF image and generating a Java image of almost a factor 50 is puzzling.
    What could cause this enormous difference? Any idea's about how we can analyze or solve this? What could RealWorker be doing in this packing time? Any hints would be greatly appreciated.
    Many thanks,
    Ida

    Thanks for the replies!
    1. Which AS version are you using? -> 10.1.2
    2. Just as a test, if you restart AS (if possible) do you still get the same values? -> yes, we restarted the AS and the results are the same.
    The server is indeed running low in memory. It is a 512MB machine, just big enough to run the AS. The production server will have some more, but not very much. Could I estimate how much extra memory it will need to keep a good performance when generating maps with live features? And maybe I'm wrong, but shouldn't the extra load for the java image only be on the client, since that's where the image is made? On the server it's just the image data, isn't it?
    I tried removing the basemap, but that reduces the loading time just with a few seconds. The live themes are jdbc themes and result in only some 20 to 30 geofeatures. Removing them from the request so only an empty image with a title is retrieved still takes about 117 seconds. Reducing the device size does reduce the loading time, so it does seem to have something to do with the amount of pixels in the image space, not with the data. Could it be that in the "packing" of the image something happens that takes a lot of memory, related to the amount of pixels?
    In my situation it would be handy if the live features were also returned when the image format is not set to FORMAT_RAW_COMPRESSED, it is also possible to draw shapes onto an existing image and this would bypass the memory problems.
    Thanks for any further help.
    Ida

  • 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

  • Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

    I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
    This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
    I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
    Please help.
    William

    Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

  • Unsupported image format after moving from one project to another

    I scanned several thousands of images to my Aperture library. Went thru all of them providing adjustments to many of them, keywords to all of them and adjust date/time to all of them. All of the pics were visible, format is jpeg.
    This is a managed library (all pics within Aperture db).
    This morning started to restructure the project files (had three of them). After moving couple of hundred images to newly created project file I started seeing "unsupported image format" red screen after clicking the jpeg. 20-30% of the pictures clicked showed on viewer "unsupported image format".
    Tried regenerating the previews. Tried command-option start with first fix the preferences option. Then with rebuild option.
    Tried moving the pictures back to their original project file.
    No joy... Still 20-30% of the pictures show the "unsupported image format".
    Aperture 2.1.
    Amy other tricks I could try?
    Reported this to Apple aperture feedback of course.
    --h

    Link the two Macs together: there are several ways to do this: Wireless Network, Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
    But however you do choose to link the two machines...
    Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
    Then launch iPhoto. That's it.
    This moves photos, events, albums, books, keywords, slideshows and everything else.
    +Note: there is no importing involved+
    The thumbs appear, but the images are added 2 or 3 times each and the events are all messed up.
    This happens when you import one Library to another, which you've done by drag and drop:
    Creating a black library and over writing the new with the old.
    Your problem is arising because of the Network Share. iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.
    Regards
    TD

  • Unsupported Image Format after opening a file in Photoshop.

    As from today,I am getting an unsupported Image Format after opening a file in Photoshop. I have made nothing more than as crop on the image. Why?

    Ernie, I misread your post indeed. I never saw a option to send RAW files to an external editor. All I can see is the option to chose what editor and then specify if PSD or TIFF is used. I always use PSD, usually 16bit and in one other installation in 8bit (due to RAM restrictions there).
    So Aperture creates the PSD version and PS edits that very version and saves it back into aperture. This is where I sometimes () get that "unsupported image" problem.
    I think this also is what Mike does: select a RAW master, use an external editor -> Aperture creates a PSD or TIFF. I haven't tried the TIFF option , though.
    My main point was: it all worked for a very long time and with the latest updates it is broken.
    have a good day.
    Roland

  • My FaceTime seemed not working and keep  telling me The document "IMG_3054.JPG" could not be opened. FaceTime cannot open files in the "JPEG image" format.  I clicked OK but it pop-up again.  So that I can't turn off my computer at all.

    When I tried to restart my computer, FaceTime will pop-up and a warning message The document “IMG_3054.JPG” could not be opened. FaceTime cannot open files in the “JPEG image” format.  I tried to clike OK but this worning message keeping pop-up and I can not quit FaceTime.  So that I can't turnoff or restart my computer.
    Can someone help?

    The next time that happens, try this keyboard shortcut.
    Command + Option + Esc
    That way you can "force quit" the Facetime App.

  • Image formats that can be used directly in PDF

    Hi,
    after severel hours of searching google, discussion boards and the PDF reference, I could not find an answer, so hopefully you guys can help me .
    I have written my own little PDF exporter and want to include images. I figured out to include jpegs directly, with the DCTDecode filter.
    Are there other image formats, which can be included in PDF directly?
    I read somewhere, that GIFs - for example - has to be parsed to get the pixel data and than must be compressed again to be inserted in the PDF file. Therefore it would be easier for me to convert GIF to JPEG with an external program and then insert the JPEG into the PDF. Or is there an advantage, to include the GIF like described above?
    What about BMP, TIFF and other image formats?
    Is it possible to insert image files lossless into PDF?
    I know, lots of questions but i would be really glad if someone can help me .
    Thanks in advance,
    Regards, Maecky

    Hi,
    thanks for your answer.
    What exactly do you mean with "unwrap"? Should i just get the data without header of the image file and put it into the pdf stream? Otherwise i would have to decompress the format, or am I wrong?
    Thanks,
    kind regards, maecky

  • Loading custom image formats

    Hello all.
    I am wanting to load a custom image format into my Java application, and am wondering how to do that. I have a few ideas to try but I figure if there is a site out there (or someone with the knowledge), there is no need for me to re-invent the wheel. So hopefully, someone might be able to expedite my learning. :)
    The image format I want to read actually contains multiple images, with 1 color palette at the end of the file. I'd like to create a series of (I assume) BufferedImages for all the images contained within the file.
    Are there any sites out there that can send me through a quick tutorial on rolling my own images, or can anyone give me a short function to do so?
    Thanks so much!

    Okay... I failed. I could really use some help in getting this work. Please.
    I have a file, which contains 1 or more compressed bitmap images and a palette. I have a small Perl script that will convert the images in the file into multiple bitmap image files, so I know where the data is and I know I have the data locations right. :)
    To create a BITMAP, I must reverse the order of the palette (perl function):
    sub reversePalette() {
      my $output = "";
      for (my $i=0; $i < length($_[0]); $i=$i+4) {
        $output = $output . substr($_[0], $i+2, 1) . substr($_[0], $i+1, 1) . substr($_[0], $i+0, 1) . chr(0);
      return $output;
    }For the image data itself, it uses a simple RLE encoding. If I see a 0, I check the next number and "uncompress" the data by adding that many 0's to the output file.
    So, what I would like to do is convert my Perl script into a Java class that will take this sprite file and return an array of BufferedImages, which can then be used for whatever.
    Any help in this would be greatly appreciated! I can't even figure out how to properly load a valid BMP file manually using WritableRaster and ColorModel. I'm so lost. :(

  • 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.

  • In the image format...

    hi. I am making a little image 100 x 100 and it sayes in the
    middle "Ian Carry" then it bounces of the sides slowly...like one
    of thows screen savers. anyway, I went to publish settings a
    checked the .GIF and the .JPEG and I tested them both. none of then
    animate! they only show the first frame, thats all. how do I get a
    image format to move?
    thanks.

    Jpg is not an anition format. Gif can be if you selected
    "animation" when you exported.
    --> Adobe Certified Expert *ACE*
    --> www.mudbubble.com
    --> www.keyframer.com
    mybluehair wrote:
    > hi. I am making a little image 100 x 100 and it sayes in
    the middle "Ian Carry"
    > then it bounces of the sides slowly...like one of thows
    screen savers. anyway,
    > I went to publish settings a checked the .GIF and the
    .JPEG and I tested them
    > both. none of then animate! they only show the first
    frame, thats all. how do I
    > get a image format to move?
    >
    > thanks.
    >

Maybe you are looking for