Unable to save raw conversion

Why did I get this message:
Unable to save raw conversion settings. There was an error parsing the files.

Cs5 - Bridge. Files are stored on "My Book" exterior hard drive
It's not a new image; I was working on an image that's been there
for a while.
Judith Stockman
Urban Archaeology
Sent from iPhone

Similar Messages

Unable to save raw conversion settings

CS5 user.I 've been using Bridge for a while and never had this problem before. Why am I getting the following message. "Unable to save raw conversion settings. There was an error parsing the files."

Storing on external drive will not corrupt them.
However, it can cause permission problems in writing data. A workaround is the right click on Bridge Icon and choose "Run as Administrator"
Also, if you access files on network there can be permission problems.

"Unable to save the raw conversion settings. There was a write permission error."

I just built a new workstation for processing photos using PS CS5. I use external drives to store my images as I find it easier for backing up as well as for when I want use my laptop for sorting, etc.. I copied over all my old "Collection" files, and of course, had to "fix" them once on the new machine. Once pointed in the right direction, the collections all fill out correctly.
When I go to process a collection though, I encounter an odd problem I can't seem to sort out. I can delete files, rename files, copy/paste to the external drives, etc.. What I can't seem to do is add Labels, Ratings, or modify RAW settings. I mean, I can use ACR to make adjustments, I just can't seem to save them.
The system just ignores label, rating commands completely. When I try to save an ACR adjustment I get this error. "Unable to save the raw conversion settings. There was a write permission error."
The files are NOT write protected. I'm set up as the owner of my workstation, with complete control of the system. I can't seem to find any useful information about this error because the "write permission error" seems to only be happening on installs, so that's all I can find help for.
My system:
Intel Core i7 970@ 3.20GHZ
24.0 GB RAM
64-bit OS - Windows 7 Pro
DX58S02 Motherboard
NVIDIA GeForce GTX 580

Thanks for replying. I've been going crazy trying to fix this.
To answer your first question; I use sidecar XMP files. If everything from my archive was shot in RAW I'd try converting to DNG and see if embedding the changes directly in a file worked. Unfortunately, a lot of my old stuff was shot in JPG, so sidecars seems to be the best choice.
When I add labels, ratings, as well as change RAW settings on files I place on my workstations HD everything works. It's only when I try to do these things with the same files on removable drives that I run into trouble. The drives I use are Transcend 640GB StoreJet 25ms connected via USB.
I don't think it's a UAC problem. At least, to my understanding, doesn't that control how your machine alerts you to program changes? I looked into how to change ownership, and did so, but that didn't work. Here's a link to what I mean: http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/
I'm stumped. I also hate the idea that I'll have to go through various folders to find images from already created collections, copy them to a new folder on my HD and then work on them. Then I'll have to put them all back... ugghhhh

Unable to covert raw files to dng?

using photo cs 3 ,unable to convert raw files to dng?

Make sure you have the latest version of ACR for CS3 installed. I seem to remember it was something like ACR 4.6. Check and see if it can save DGN conversions. I don't use DNG format for its not as well supported as manufactures raw formats.
You can always download the latest DNG converter or a version 4 DNG converter http://www.adobe.com/support/downloads/product.jsp?product=106&platform=Windows

Exported Raw Conversion Image Resolution and Assigning a Color Profile, etc

In Aperture 1.1, although I set the exported Raw conversion image resolution to 300 dpi in the preferences, it continues to come out at 72 dpi which is something of an inconvenience. Also, is it possible to assign a color profile to the "exported version" so that it is congruent to my PS CS2 color workspace (if that is what its called). Is this program capable of carrying out a conversion as a background operation? Finally, can the layout windows be configured so that they remember how they have been used in the past? Thanks.

Iatrogenic huh! Cool!
Anyway, I'm not real clear on what it is you are trying to accomplish. Despite your obvious vocabulary skills, there seems to be some disconnect relative to what you are trying to accomplish. You are right that "exporting a version" in Aperture is roughly equivalent to what happens in ACR when you "Open" a RAW image into Photoshop. In both cases you have, hopefully, already done the adjusting of parameters you want prior to "exporting", or "opening". When you "open" or "export" you wind up with an "image" composed of pixels, whereas in the RAW adjustment phase you are just working with a temporary thumbnail and a set of mathematical instructions. Big difference, I suppose is that when you "open" and image from ACR into CS2, the resulting image is truly just pixels and has not had a "file type" applied to the file yet, until you "save" it, while in Aperture, if you "export" a file to CS2, or to the desktop, you end up with the file type already applied. Presuming you "export" a 16 bit TIFF or PSD, there is no operational difference.
I could be wrong, but with the new Bayer Demosaicing algorithms in Aperture 1.1, and the Camera RAW adjustments, you should be able to come up with an adjusted image that is VERY close if not identical to one done in ACR, with the possible exception of lens abberation adjustment. I was very critical of the RAW adjustments in 1.0.1, but I am very happy with the capabilites in 1.1. That said, I think there is still some room for improvement in user friendliness of some of the adjustments such as Levels.

Preflight keeps saying "Unable to save the PDF File after post processing"

I'm at a loss how to overcome this. Spent almost a whole day, together with another person, trying to fix it with no success!
I use Adobe pro CC on a PC
I usually receive pdf files from this one client who edits and formats a book in Mac Pages. Up until a few days ago I had no problems converting the client's pdfs into pdf/x3, but the last three versions of the latest file have stumped me.
Just to test, I first just tried to convert the file (33MB), unchanged, to pdf/x3 using the save as other option - message reads "the document has been saved, however, it could not be converted according to the selected standard profile: convert to PDF/X. Please use preflight with the profile "Convert to PDF/X" in order to identify those properties of the document which prevent it from being compliant to this profile"
if I then choose under Profiles - convert to PDF/X3 - it says no problems found, and appears to have saved the file. If I try to save again as a pdf/x3, just to make sure, it then tells me it's not pdf/x3 compliant
OK - so then I go back to preflight - and choose the standards function - then pdf/x3, then continue with the default colour profile. About halfway through the conversion, at the point of saving the file, I get the message "unable to save the pdf file after post processing"
So far I've had no luck figuring out what this is.
I then choose the option of "verify compliance of ppdf/x3" - message reads "pdf/x3 version key (GTS_PDFXVersion) missing", and "Trapped key not true or false"
Help!! How can I be sure the file converted / or not?
kim

Yes I was/am aware of Preflight's inability to play nicely over cloud technologies in certain cases, especially wrt Standards technologies, this will be partially addressed in an upcoming version of Preflight without saying too much. But the same thing could theoretically have happened if the file was also located on another local network client or server. Leaving aside the argument that this may violate the Acrobat User Agreement - since purchasing the software, the user agrees to employ its functionality on a single host system and precludes host-client-based scenarios - this simply is not a supported use, meaning the user may not have expectations that it will work at all, if the applications requirements are not observed. There do exist server-solutions for Preflight files within networks, but Acrobat and by extension Acrobat Preflight is not one of those solutions, and (still) belongs in the single host-based desktop environment.
However most (99.9%) functions within Acrobat <-> acrobat.com file exchange are supported, file syncing across multiple devices will soon be supported, but Standards compliance is still admittedly a problem at this point. Some testing has been done using 3rd party cloud technologies starting with enterprise-based solutions, such as Office 365, and this will continue to ramp up to include other 3rd party products.
As for the second point, Preflight will usually change the PDF version to be complaint, are you saying that it was unable to do so in this case? It seems that this error should have popped up during the normal Preflight conversion attempt. Personally I think solving a workflow problem using the print path is a little bit of a heavy-handed approach, but if helped and the results are acceptable, then that is good. Since that path is non-existent on a Mac, as one needs to Save as Adobe PDF from the Print dialog's PDF drop-down menu, I am assuming your workflow involved file creation on a Mac, then further processing on Windows using the PDF printer. I am wondering if a simple resave/Save As... to PDF with overwrite on a Mac, or Preflighting the file using a PDF version compatibility profile before the PDF/X conversion would have helped. Since there are such a multitude of methods that a PDF can be created, there are also many ways within Acrobat that a user can shape the file to be compatible with the expected workflow, ie, 'many ways to skin a cat', without being morbid.

Unable to save exported Aperture TIFFs as jegs when opened in Photoshop

I'm using the latest version of Aperture and need to do major retouching of the images I have edited using Aperture. When I "export versions" of the images, I normally choose "TIFF-50% of size" or "TIFF - fit within 1024x1024", but when I open them with Photoshop, after I worked on them I am unable to save them as a jpeg. The option just doesn't come up.
The only save options I am offered are - SAVE AS - Photoshop, Cineon, Dicom, FXG, IFF Format, Large Document Format, Photoshop PDF, Photoshop Raw, PNG, Portable Bit Map or TIFF.
Any idea why this is happening and how I can rectify? I need to use photoshop for my retouching and I don't want to have to export RAW files from Aperture, it's much simpler exporting a TIFF.

The tiff is a 16 bit file. Go to images/on the photoshop menu and convert to 8 bit. then the jpeg option will show up.
Cheers

Fuji Raw Conversion Software as External Editor in Lightroom

Anyone know whether Fuji's Hyper Utility RAW conversion software (if I remember the name correctly) will work as an External Editor in Lightroom. (Just read an article by a Nikon photographer who uses Capture NX this way in Lightroom and wonder whether the same is possible for Fuji.)

Thanks; I guess my question (which I did not state clearly) is whether if, at the end of processing in HV-S3 and "Save" the saved file (likely a TIFF) will automatically appear in the Lightroom Library associated with the original RAW file; this would be the chief advantage over just opening the folder with the file in HV-S3 to begin with, but it occurs to me that this may be a dumb question (as I've just downloaded and begun to use Lightroom and can't experiment with HV-S3 yet as it has not yet been released, but will be shortly). Thanks again.

Elements 11 "Unable to save because write access was not granted."

I previously organized and tagged a batch of raw photos using viewNX on my PC. The PC crashed and I am now trying to edit that same batch of photos with Elements 11 on my iMac. I am able to access the photos, but when I try to save my edits I receive the message, "Unable to save because write access was not granted." I am not on a networked computer, no one else has access to the photos, and the photos are not open in any other program. Forgive the ingorance, but the the iMac and Elements 11 are new to me; can anyone help me troubleshoot?
Thank you,
Heidi

You are wonderful!!! You nailed it:) I need to reformat my hard drive for my Mac and meanwhile save my edited photos elsewhere. I can't tell you how grateful I am for your input...I have over 200 portraits to edit for a non-profit fundraiser in two weeks. Thank you!!!

RAW conversion with Aperture

Has anyone compared the quality of RAW conversion of Aperture vs. Nikon Capture as well as other converters?
I really like the quality of nikon capture and would not want to purchase aperture unless the conversion was at least equivalent.
Thanks for any input.
mark
G4 17" Laptop Mac OS X (10.4.3)

I've compared Aperture's conversion side by side with Adobe Camera Raw's. My method was to do some conversions with Camera Raw and save the result along with the RAW file. Then, in the Apple Store, I performed the conversions using Aperture.
The results from Aperture are not good. They look okay at reduced size, but if you look more closely, the de-mosaicing Aperture performs is quite bad. On some images it is only "somewhat" worse than Camera Raw; on others it is so bad as to be unusable. Shadow detail suffers the most, but highlights are not immune. Some images showed color fringing that was not present in the Camera Raw conversion, even with all chromatic aberration adjustments set to zero in Camera Raw.
I ignored differences in color and tonal rendering because I did not have enough time with Aperture to learn to get the best results out of it in terms of color. It takes a while to figure out how to get good color out of a RAW converter.
In no case was Aperture as good as Adobe Camera Raw in terms of image quality. The difference was immediately obvious at 100% magnification.
I would not use Aperture for RAW conversion.
EDIT: I forgot to mention, in case it matters, my camera is a Nikon D2X.

RAW conversion, iPhoto vs Aperture

I currently shoot in RAW, save the folder to my desktop, convert files in ACR and import into Photoshop for edits; I then create a master edited TIFF for each saved image a, plus make 3-5 variations (composites, B&W, etc) of every master image . When all that is in the (renamed) desktop folder, I then import that folder into iPhoto where finished files are routed to Smart Folders.
For added security I routinely backup all the RAW files using Export to an external HD.
The ideal workflow (for me) however, would be to use Nikon's free NX2 software to convert the RAW files into TIFF, do basic editing and import both the RAW and TIFF conversions directly into iPhoto. So far, I can't get that to work without going through the extra step of NX2>Desktop>iPhoto.
Am I missing something in iPhoto, or maybe it can't handle that?
Would Aperture allow that direct NX2 > Aperture import? I'm a little unclear on the Aperture RAW conversion process, so could I import RAW files folder into Aperture and then convert those RAW files to TIFF and edit them within Aperture? That way the only time I'd have to go outside Aperture would be to do something in PS that Aperture can't handle.
Brian

No
You simply have to set your editing program as the external editor for iPhoto - in the iPhoto preferences you can choose to send RAW to the external editor or not - if you do then once you edit the photo you must save it to the desktop and import the modified photo into iPhoto creating a new photo - if you do not pass it as RAW then you save in the editor and it is returned to iPhoto and the database properly updated
As to the process iPhoto uses - all originals are saved unmodified - RAW , TIFF or JPEG. as they are imported a small JPEG preview is generated for quick access by iPhoto and other programs - with RAW an additional large JPEG preview is saved -- when you edit in iPhoto the edit steps are saved and applied to the preview and to the thumbnail - future edits steps are also saved so you always start yoru edit with the unedited original and add edits so you never are but one step form the original eliminating the multiple editing losses that cause some people to use TIFF rather than JPEG -- hence my comment
Both can import and convert your RAW photos and both provide lossless editing so using giant TIFFs would not be necessagy
and
Unless you have very unusual requirements your work flow seems uncessary and overly complicated to me
as to
but if I want to see the original RAW file, and the edited versions stored within iPhoto
If you want to see both then they both have to be there - since iPhoto always keeps the original and while editing in iPhoto you can view it at any time by depressing the shift key most people prefer to simply their work flow and save the disk space and let iPhoto handle this
It really sounds like you do not want iPhoto and yoru best choice is to shoose a different photo manager that works like you want - or learn and understand iPhoto (and most if not all Digital Asset managers - DAMs - which work much like iPhoto) and use it the way it works
You can use what you please and do what you please, but if you use iPhoto you are making life very difficult by going against its standard procedures
LN

Aperture 3 Raw conversion from Nikon D700 - Bad results - Anyone?

I recently upgraded to a Nikon D700 and have noticed I am getting some really bad conversion results from my raw files which involve my having to do a lot of work to get decent images. Most images are too dark and with strong orange cast... Any ideas? I thought it might be the camera, so I tried another computer with photoshop raw converter and images are fine. I have noticed the original import settings are strange on Aperture but cannot seem to change them, they always revert back to maximum hue boost and max boost ect... Any help would be great! thanx!

I have a Nikon D700 and have just tried the Aperture demo- same results as you guys, disappointing RAW conversion. Contrast and sharpness quite poor and blues are 'off'
I currently use Capture NX and was looking for something a little less 'clunky'. Though it may not be as slick as Aperture, its RAW conversion is spot on (as you would expect from a Nikon sponsored app)
It's easy to compare the differences- open an unedited RAW file in Capture NX and save as an uncompressed, 16 bit TIFF. Import this and the original RAW file into Aperture. Prepare for disappointment :-/

A novel idea regarding RAW conversion

With the much debate about Aperture and ACR and RAW conversion, I had this thought: RAW conversion is really part of the image editing process, not part of cataloguing, selection, organization, or required for producing thumbnails.
I'm not exactly sure when the RAW conversion takes place, but I'm guessing on import, so that images can be immediately edited. Why can't thumbnails and organization take place in Aperture without converting from RAW? Adobe Bridge seems to manage this just fine. It would seem like the logical place to put RAW conversion is as a precursor to image editing in Aperture. For example, when you click the adjustment button, the conversion takes place. This would seem like a logical way to incorporate a RAW Converter plugin.
Why does the Aperture RAW conversion have to take place at all (except when a user demands it) ? Seems like this follows workflow more logically...
Brad

Interesting. Well this is confusing then -- why in
the world is Aperture not sending a RAW file to
Photoshop when you configure Aperture to use
Photoshop as its external editor?
It seems from my observations that this was a design choice on the part of Apple. This is going to get a bit technical...
When you choose to open in an external editor, Aperture automatically converts any 'master' file (tagged as 'isExternallyEditable' = false and 'isOriginalFile' = true in the XML file) to a 16-bit TIFF or PSD file, adds that as a new file stacked with the original RAW and opens the new file in the external editor. That new file is not really a 'version' in terms of it just being an adjustment recipe, but is a whole new file which is linked in the database to the RAW, just like a stack.
Once that new file is made, it's 'isExternallyEditable' tag changes to true and from then on Aperture passes the file directly to the editor. This state is shown by the target icon. This repeats until you make image adjustments to that image within Aperture, leading to your earlier problems with repeated editing of the same file in PS. If you DO make adjustments to it within Aperture it then becomes a new 'sub'-master with it's own versions.
Playing devil's advocate, there is actually a valid reason for doing things this way - pass the original RAW file to ACR, and how does PS know where to save the resulting file so that it goes back into Aperture, or which RAW master to associate it with?
A possible solution with Aperture 1.0?
The manual workaround at the moment which would give a reasonable amount of play back-and-forth would be to set up two hot folders using folder actions. One automatically opens any files dropped into it in PS. The other automatically imports any files into Aperture.
So, do all your choice editing until you just have final picks, not bothering with any image adjustments, then:
1) Go through the final picks, Apple-Shift-S (export master), saving them into the PS hot folder. They automatically open up in ACR, probably one at a time.
2) Do your RAW conversion with the superior toolset available.
3) Save into the Aperture hot folder and watch them be automatically imported.
4) Now the more manual bit - drag that converted file into the stack with it's RAW original.
You now have the original and it's converted file linked together in Aperture, although keywords etc. will be separate. Once the hot folders are set up it should be relatively straightforward. Not nearly as straightforward as it could be, but hopefully manageable.
Ian

Raw conversion to JPG better with DPP than ARC 5.X

I started testing conversion from raw to jpg with Canon's Digital Photo Professional and ARC 5.x (CS4) and noticed a much better conversion with DPP. At low ISOs does I don't see much difference, however at 800+ it is very noticeable. I hate to give up the work flow of Bridge and ACR and go back to using DPP. Is there anything that can be done to improve this?

Quoting from an old post of mine, with apologies to all who have read it before:
This has been covered ad nauseam here. Please do a forum search for more details.
Camera manufacturers, Canon and Nikon in particular, perform in-camera RAW to JPEG conversions designed to generate the over-saturated, over-contrasty and over-sharpened images that appeal to most amateurs.
Their stand-alone RAW conversion software also performs the same conversion to your RAW images.
Noise is also hidden by compressing the shadows so you don't see much of the noise inherent in the image.
Adobe Camera Raw, ACR, on the other hand, comes with default settings designed to give you the most detail possible
(even if this sometimes means revealing some of the noise hidden by the camera manufacturers in their RAW conversion software), as well as the most natural images.
That being said, you can calibrate your camera to ACR and come up with your own settings to produce exactly what you want, including the JPEG-look of the camera manufacturer, and save that as your profile.
The key is to learn how to use ACR properly and to calibrate your camera to ACR.
The camera calibration refines the settings by letting you adjust for the exact sensor response of your individual camera unit rather than the average of a sampling of such unites provided by Adobe.
The ACR defaults are nothing more than a suggested starting point.
The color temperature won't necessarily match either.

I am unable to open raw files from my Canon T1i in Adobe Camera Raw of my version CS3 of Photoshop. I have tried to update my ACR by downloading version 4.6 from the Adobe website but I am still unable to open raw files, just JPEG. Is there a way to use

I am unable to open raw files taken on my Canon Rebel T1i in my version of Photoshop CS3. When I import raw files into Bridge they come up as patches with CR2 on them and when clicked on, a notice comes up stating that Photoshop does not recognize these files. I tried to update my Adobe Camera Raw by downloading version 4.6 from the Adobe Website, but when I clicked on the plus-in, I got another message that Photoshop does not recognize this file. I spoke with a representative from Canon who said that I could not update CS3 and that I should subscribe to the Cloud. I would prefer to use my CS3, if possible. Can anyone advise me what to do?

The T1i was first supported by Camera Raw 5.4 which is only compatible with CS4 and later
Camera Raw plug-in | Supported cameras
Camera Raw-compatible Adobe applications
Some options:
Upgrade to CS6
Join the Cloud
Download the free Adobe DNG converter, convert all T1i Raw files to DNGs then edit the DNGs in CS3
Camera raw, DNG | Adobe Photoshop CC

Unable to save raw conversion

Similar Messages

Maybe you are looking for