Image format compilation options

The Pixel Bender spec (included with the toolkit) states:
"Depending on compilation options, pixel channels may
actually be 8-bit integers, 16-bit integers, or 32-bit
floating-point values."
However, I couldn't find any discussion on how to set such
compilation options. Is this currently possible? I'm interested in
creating a 32-bit floating point output image.

Hi Joe,
That bit of the spec. is misleading and should be changed in
the next version. Assuming you're writing a Pixel Bender kernel for
Flash your image data will always be 32 bit floating point.

Similar Messages

Questions related to Disk Images - Image Format Options

Can anyone tell me a more about using Disc Images? I am with a group of new Mac Users and we're focusing on Disc Images at the moment. Want to create a Keynote Presentation for the group when finished.
I have found already a few answers here, if someone could help me on the rest?
In this Thread I focus on the Image Format.
Disc Utility (using OS 10.5.7) offers the following options when creating a Disc Image:
sparse Disk Image
sparse bundle Disk Image
Unanswered Question:
1) What is the difference between sparse Disk Image and sparse bundle Disk Image?
Answered Question (if you have ad-on Informations for the answered Questions feel free to jump in):
Question: What is sparse disk Image for?
Answer: "Choose an image format. You can use "sparse disk image" for a disk image that only uses as much space as it needs, rather than a set amount of space. If you're not sure, use "read/write disk image" choice." (Source: How to create a password-protected (encrypted) disk image in Mac OS X 10.3 or later: http://support.apple.com/kb/HT1578)
Thanks in advance
Rama

Thank you both for your Infos so far. In the meantime I've created some Disk Images. What I noticed is, when I choose a small Image Size like 10 MB, then it changes from "Single Partition Map" to "No Partition Map". When I go bigger to 500 MB it changes to "Hard Disk".
It was already helpful to read the Manual to understand the Single Partition Maps, but what I still don't understand is the difference between using "no partitions map" at all and the other options such as "Hard Disk", "CD/DVD" or "CD/DVD with ISO Data".

Explain Image Format options in disk utility

I have a DVD full of jpeg files. I want to make an exact replica. I've read the explanation of how to do this in the Disk Utility help section. There are four options under the Image Format dropdown menu. Presumably there are advantages and disadvantages to each of those options. Where do I find an explanation of those choices? What is my best choice for making an exact replica that can be read by any other DVD drive?

Finally stumbled across the explanation buried in DU Help:
IMAGE FORMAT DESCRIPTION
read/write
Choose this if you want to continue adding files to the disk image after it’s created.
sparse bundle disk image
Choose this if you want to continue adding files to the image and want to conserve space. The disk image is just large enough to hold the files in it and expands to its maximum size as you add files to it. For example, if you create a 100MB sparse bundle disk image, its maximum size is 100MB.
read-only
Choose this If you don’t need to add more files to the disk image.
compressed
Choose this if you don’t need to add more files to the image and you want to conserve space. The data is compressed so the disk image is smaller than the original data.
CD/DVD master
Choose this if you want to use the disk image with a third-party application. The disk image contains a copy of all sectors of the disk, whether they’re used or not, and copies them to other CDs or DVDs bit for bit.

Options for image format and encryption when creating disk image?

I am trying to help someone via email, so I am not positive that he is doing everything I tell him .
He was having problems with creating a disk image of his project, but I thought he was getting it now until he sent me a message asking what settings I select when creating a disk image. He included a picture that has the options in drop-down bars. The first two are not a problem, but I don't know where the second two are coming from, as I have never gotten those:
+Save As: [Name of project]+
+Where: [Location]+
These two are what I see each time I do a 'Save as disk image' but he also has a block with these other two options, that I have never seen. I put his default selections in the brackets:
+Image Format [read-only]+
+Encryption: [none]+
I took a look at iDVD's options for archiving a project, thinking that he had done that, but I still do not get these options.
Any information appreciated.

Beverly Maneatis wrote:
... How do I get a screenshot into these replies?
send me an email, Bev, I'm shy to publish here that simple html code.. (picture has to be on some webspace...) .. I want to avoid, some 'beginner' posting here 10Mpixel vacation pics....

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

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.

Convert PDF Page to Image format

Is there any way to convert PDF page to Image formats (like JPG, GIF...)?
I am looking in iTextSharp. If there are other options also, please let me know.

There is a sample included with the Acrobat SDK that shows how to perform conversions of PDFs to other formats. There are also other options available to plug-ins such as PDPageDrawContentsToMemory() and then using an image library of your choice to save the bitmap data into various image formats.
> I am looking in iTextSharp
This is the Acrobat SDK forum - for questions regarding coding using the Acrobat SDK. Have you considered asking this in an iTextSharp forum if you are limiting yourself to that product?

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.

Unsupported Image Format After External Editor

I have Aperture set up with Photoshop Elements 6 for MAC as the external editor. I have PSD(16bit) 300 dpi. I have used this external editor several times in the last two days. The most recent time I had a problem. It started PSE 6 as requested and displayed the picture with a *.pdf filename. I used the filter option I wanted and was satisfied with the result in PSE 6. I saved the file and quit PSE. It came back to Aperture and displayed two images: the original on the left and the edited on the right. After one or two seconds the image on the right (the result of the edit) was replaced by a dark red background with the black text Unsupported Image Format displayed. If I click on the right image, the edited image appears briefly and then reverts back to the error display.
As I said, I used this only the night before several times with no problems and I have not changed my Aperture preferences since then. The master file is a Canon cr2 file and I did some Aperture corrections before I decided I needed to run a filter in PSE 6.
Thanks,
Bruce

I'm having a similar problem with unsupported images. The problem has occurred when I use an external program to create an image. I've tried creating them as TIFF and JPEG. If I use the Sony Image Data Converter (v2 or v3) I get the unsupported image format.
Last night I was scanning film with Silverfast, creating TIFF files and using them in Aperture 2 as referenced files. Everything was fine. This morning I did the same thing and got the red Unsupported Image Format screen from the same original image.
I have found if I import the unsupported image into the Aperture library instead of using it as a referenced file it usually works. I don't like this solution because it messes with my work flow and I'm trying to keep the size of my Aperture Library under control.

Unsupported Image Format - Please Help

Since upgrading Aperture to 1.5 all my RAW images (.CRW & .CR2) from my Canon 300D and 20D, initially show when I click them and then very quickly turn to a maron coloured box with the words 'Unsupported Image Format'. I am really worried about this as it's not just 1 or 2, but all my RAW images which is about 80% of my library. All JPG images are fine.
I would be very greatful to hear some work arounds to this.
Thanks

Hello,
It's not your RAM. Folks on quite a few forums have been reporting similar problems. As well there have been several threads on this forum of a similar nature.
I've a similar, but different "Unsupported Image Format" error.
I shoot Canon's 1Dsmk2 and 5D cameras, both of which put out .CR2 files, and both of which are supported by Aperture.
So far Aperture has been able to open all of these.
However, I converted quite a few of them to DNG files with the last version (Adobe DNG converter 3.4 I think - 3.5 is the current version so I'm guessing the last one was 3.4)
Aperture is unable to open any of these DNG files. I get that same 1/2 second preview flash and then the error.
All of these DNG files open fine with PS CS2, Bridge, Lightroom. They also appear correctly with other Apple Products - Preview and iPhoto [ 6.0.5 (316) ].
So the problem seems to be Aperture specific.
I've done some tests with the latest Adobe DNG converter (version 3.5). There are basically 4 settings that one can alter. Embed original, size of preview, compression, and to store the file as a mosaic or linear. If the "linear" option is selected, alone or in combination with any of the other options, then Aperture cannot open the file.
If linear (in version 3.5) is not selected then Aperature seems to be able to open the files converted with all of the other options, either selected alone or in combinations.
None of my DNG's converted with the last converter (3.4) had the "linear" option selected.
Also, I've tried running a DNG created with v3.4 through the v3.5 converter to see if it would then open in Aperture, but this didn't work.
I've tried rebuilding the library and the other fixes mentioned by others here - every other program except Aperture seems to be able to open these files.
So, I'm hoping that there is a v1.5.1 out pretty quickly whicch addresses these image compatibility errors.
Steve

'Unsupported Image Format' after migrating project

I finally when to an Apple store and purchased version 2.
But I have a major issue with one project I just migrated to RAW 2.0.
Lots of the images are now saying 'Unsupported Image Format', these images are from the same Nikon D80 camera using the same RAW settings that I have used for sometime. I have also successfully migrated other projects already with no problems.
This is very strange as Aperture reprocessed all the thumbnail images just fine.

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

"Unsupported image format"- Has nothing to do with RAW images-

I have a very weird problem with one of my Aperture 3 libraries. This only seems to apply to one library, all the others I tested seem to work just fine.
This library was created on my MBA and transfered to my iMac when I returned from my trip. It worked fine until yesterday.
When I open an image (thumbnail looks just fine) the photo briefly shows the large view with the "Loading" indicator at the top. When the loading indicator goes away the photo is replaced with the "Unsupported image format" display. After that the thumbnail is gone too. This happens for most, but not all images in this gallery. I can restore the thumbnail and other previews from the raw NEF photos by choosing "Reprocess Original".
I have already tried all the options the Aperture debug menu offers (start with Option-Command), this didn't help…
When I open the library in the Finder (Show package contents) I can drill down to the "Previews" folder and see the photos that Aperture wont display. They seem jsut fine and all file permissions seem to be set correctly…
Has anyone ever experienced this problem? I really don't know what else i could try, short of deleting this library and importing all the images into a new one, losing all my edits, of course… Super annoying…
Thanks and kind regards, Hans
Edit: The raw photos are from my Nikon D700, which has been supported by the RAW importer since forever. i dont think that has anything to do with the original files, especially since Aperture can recreate the previews from the raws…

There has been problems with the last Raw update released a few days ago especially with Nikon cameras.
Have you updated your system software in the last day or so? Is it possible you updated on one system but not another.
And for what its worth norbertmuc's question was valid from a troubleshooting standpoint. If something worked at one point and stop working at a second point it is fair to ask what happened between those two points. He might have been a bit brusque but I don;t think he was accusing you of anything.
And of course there are many things you can do to a library to break it.

Aperture gets "Unsupported Image Format" on some JPG images

I'm using Aperture 1.5.2 "trial" on PB 15" with OSX 10.4.9. I am getting "Unsupported Image Format" on about half of the 15,000 JPG images that I have on my HDD. But not all of them - even though all images come originally from my D100 camera and are JPEG images. These are all JPEG images with extensions JPG, jpg and jpeg. No RAW or TIFF.
My images are currently catalogued in iVew MediaPro [IVMP] and I'm interested in switching to Aperture. So I've gotta find a way to import those photos.
Here's a clue: When I put the CF card from my camera into the computer yesterday and tried to add the images to Aperture it reported that all the images on the CF chip were "Unsupported Image Format." I was not copying the images - just leaving them im place. As a test, I then used IVMP to import from the CF card onto the HDD, into a directory. Afterward, I fired up Aperture and it could properly index and display the files. I noticed that the pre-existing images that are viewable in Aperture all have previews when viewed in the Finder. Also, they've all been imported from CF to HDD using IVMP, so there may be some processing going on there. I also tried reading files into Photoshop and rewriting them with previews, which I verified in the Finder, and those files also can not be viewed in Aperture. So it is not just a question of having a preview - it's something else about the files.
Another clue - when I shoot more than one CF of photos in a day, I use IVMP to import the first CF batch, and those are always visible in Aperture - but IVMP doesn't let you import two batches on the same date (pretty goofy huh?) - so to import an additional batch I have to (Finder drag-drop) copy from the CF to the HDD into a directory - and those files have no previews, have not been imported thru IVMP, and interestingly are not viewable in Aperture.
So I'd have to conclude that iView MediaPro is doing something to "tame" the files' format that makes them acceptable to Aperture. But I want to dump IVMP, so there has to be some other way to make these D100 files acceptable to Aperture.
I either need to "fool" Aperture into reading the files or find a way to tweak 'em and make 'em acceptable to Aperture. Any ideas from other iView/Aperture users out there?
PB 15" Mac OS X (10.4.9)

Good idea, but I checked it... I mentioned reading right from the card in order to illustrate that the JPG files are "unsupported image format" even *right from the camera*. *In fact* the CF is not the differentiating factor between renderable and non-renderable. The real factor is whether the files went thru iView Media Pro or not. Files that were drag-dropped from the CF into a folder are not renderable by Aperture and files that were imported first (from the CF or from another folder) thru IVMP into a folder are renderable.
Yesterday I confirmed again that GraphicConverterX does not fix the files if I import and then rewrite with additional options turned on. It also sees the same IPTC data and EXIF on both a "good" file and a "bad" file. Identical. I also fixed the OS9 creator and filetypes so they're <none> and that didn't fix anything - some good files and some bad files have this configuration.
Ah another COOL THING - I just loaded a CF card into the computer and brought up Aperture - it immediately recognized the card and showed me two previews - one for a NEF (Nikon RAW) and one for a JPG. The previews looked fine. I clicked to have it import the photos. Once imported, the NEF looked OK, but the JPG had a grey preview and then "Unsupported Image Format" on the large version. I think this confirms the file format is a problem, but then why was Aperture able to gen a preview when the file was on the CF chip but not after it was copied to the HDD?
I double-checked this by copying in Finder drag-drop from the CF card to the HDD and then importing the same two photos (NEF and JPG) from the HDD, and indeed the NEF was renderable and the JPG was not. For me this confirms that there's something about the file format that Aperture can't deal with.
I then imported the same two files using IVMP (Media Pro) and as expected, both files could then be "imported" and rendered by Aperture. So IVMP is doing something that makes Aperture really happy.
In case someone can actually compare the two files - I have put up a "bad" and a "good" JPG - it's the same image from a Nikon D100, but one of them (bad) is right from the camera and the other (good) was imported by IVMP and somehow is acceptable to Aperture. Any intelligence that anyone can add based on these files would be useful.
http://fire.red7.com/aperture-tests/DSC_0070-good.JPG
http://fire.red7.com/aperture-tests/DSC_0070-bad.JPG
PB G4 15" Mac OS X (10.4.9)

Image format compilation options

Similar Messages

Maybe you are looking for