PS CS3 crashes at "Save as" after editing Hasselblad DNG file

Hi,
Soliciting some net wisdom on this one.
Went mad an got myself a H2D-39. Am now experiencing intermittent crashes when saving files from Photoshop.
I import the H2D files as DNG using the latest version of FlexColor 4.8.6, then select image in Bridge, do raw conversion in Bridge and send to PS for final edit. When I try to save the file (Save As), PS crashes roughly every second time before the File menu opens, crash info:
Problem signature:Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 10.0.1.0
Application Timestamp: 470fd6cb
Fault Module Name: Photoshop.exe
Fault Module Version: 10.0.1.0
Fault Module Timestamp: 470fd6cb
Exception Code: c00000fd
Exception Offset: 00b37f90
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 1035
Additional Information 1: 5e09
Additional Information 2: d7242649f4a55a851fcce331718e8c37
Additional Information 3: 373d
Additional Information 4: 7d7265066cfe4fecec0e1f61b91a462e
Running Vista SP1, all latest Updates, 4GB machine, (still) plenty of disk. No problems when working on smaller files (from my 10Mpix camera). Tried as best I can all means of saving and optimizing memory use as suggested in KB etc. Any suggestions?
Thanks, Håkan

I think my problem may be solved. Yesterday I installed the latest driver for my elderly Epson 3200 scanner, and now PS seems to be working again. I just read another thread about PS3 crashes where Chris Cox said "(buggy drivers are why we no longer install the TWAIN plugin by default -- too many bad drivers, and no way for Photoshop to know until they crash)".
Replacing the TWAIN that came with the old scanner driver which may have not been compatible with Leopard may have been the solution...at least I hope so.

Similar Messages

Users are not able to save pdfs after editing - Adobe XI. They do not use the Win7 explorer preview pane. If they completely close the Win7 explorer window, they can save - Adobe XI thinks the preview pane is open when it is not.

Users are not able to save pdfs after editing. Product is Adobe XI, OS is Win7 64-bit. When saving, an error pops up that the file cannot be saved, it is in use. If they save as a different name, it works. Found several forums/blogs/etc that suggest the problem can be solved by closing the Window7 explorer preview pane. They don't use the preview pane. I figured out that if they completely close the explorer window, they can save. But this means they have to open and close explorer for each file.

Hi, I would like to chime in and say that this problem has not yet been resolved. It is extremely annoying when all I do is highlight a document in the file explorer and I get 5 errors (evenly spaced out about 20 seconds apart telling me that "Microsoft
Word Cannot Start (24)". These errors persist even after windows explorer and word are closed. And I don't want to start terminating processes just to make them stop every time.
I'm a little frustrated with this problem and the other problems I've encountered with MS Office 2013 with file corruption, crashing, 2010 compatibility issues, and the whole host of errors when trying to actually do WORK with Word.
I do work with long, complex reports in Word because that's the best way available for myself (and my coworkers) to use. However, I sincerely regret upgrading to Office 2013 because of it. I love it, all of its features, and its interface, but I simply cannot
use it without problems.
Submitting an official complaint whenever the phone reps start up again in the morning.

Just downloaded LR3 trial - how do I save changes after editing?

Can't see any ref to it.
Thanks, ot

clvrmnky wrote:
areohbee wrote:
I lock my photos after editing is complete ...
The beauty of non-destructive editing and snapshots (and, now, publish services) is that, just like negatives of old, your editing never has to be "complete."
When I say "complete", I dont mean "finished forever", I mean "finished for now".
I dont know how I do it, but sometimes I end up with AutoSync turned on by accident - last time it happened I hadnt even used AutoSync recently, it turned on by itself, upon restart after a crash I think. Even if my analysis is wrong and its entirely due to operator error - the result is the same: massive inadvertent edits until I detect the condition.
Also, I make another mistake sometimes (I think its me): when fast typing, I end up normalizing exposure across a whole sh-load of photos... - still havent figured out how I do that since I dont even see a shortcut for that. Sometimes I catch it right away, sometimes not until much later.
Another frequent mistake made by newbies a lot and seasoned users upon occasion: forgetting when edits will target multiple photos vs. just one.
I could go on and on... - I love that I can tweak edit settings on a whim, non-destructively, but I dont love it when changes are made inadvertently. Locking does not keep you from editing, just reminds you that it had previously been considered "finished for now" - you can proceed to edit if you wish, or revert to locked state after viewing a detalied list of changes. "Save Metadata" has now become obsolete for me, replaced by "Snapshot & Lock". I dont know about you, but my workflow is:
- After import, spend a good while editing, until done for now (at which point I snapshot & lock), then optionally at some point in the future:
- Revisit for re-editing until done for now... If thats just one change: say Exposure +.1, and it was intended, I confirm intention then move on. If I plan to make a few more changes, I unlock until I'm done with it, then relock).
To each their own, but ChangeManager has become my all-time favorite plugin. - Gives me a very warm and fuzzy feeling knowing that my photos will never be changed inadvertently - only intended changes... - I hope Adobe builds this into Lightroom proper in Lr4, but even if they dont, I'm covered. I never realized how much stress it was trying to be ultra-careful all of the time when using Lightroom, to not make inadvertent changes, until that stress was gone...

Photoshop CS3 crashes on "save as" command

Hi all,
I'm running Photoshop CS 3 edition on Leopard. Photoshop crashes every time I try to "save as". Has anyone else experienced this issue? I have 2 gigs of ram on a new iMac.
Thanks,
John

I too am having the same issue with Photoshop CS3 crashing everytime I SAVE or SAVE AS, and when I choose File>open while the programs is running.
I am running
Mac OS X 10.4.11
Mac Book Pro 2.33 GHz Intel Core 2 Duo
2GB RAM
I had been running the program successfully for over six months until a couple days ago.
I have verified/repaired permissions, reinstalled the entire Creative Suite, trashed preferences and reduced memory usage all with no luck.

Illustrator (CS3) crashes on save

My marketing guy called me this morning to request my help in diagnosing a problem with his Illustrator. He says he can do his work and get all the way through till he's done with whatever he's working on, and then when he goes to save it, he tells it where he wants it saved (local HDD) and then hits "save." After that, Illustrator acts like it's saving to a temp file, and crashes. This is on a Dell Precision workstation running Windows XP Pro SP3, 32-bit.
I understand from a little bit of research that CS likes to have a dedicated "temporary" partition. We do not have that set up at this time. We did make sure that the progam was fully updated by running the updater. Unfortunately there were no updates available. Any idea what might be causing this? He did say he'd been having some issues with his primary (network) printer earlier, but I printed off a test page this morning with no problems.
Any suggestions?
Thanks!

I understand from a little bit of research that CS likes to have a dedicated "temporary" partition.
It doesn't. AI always uses the system temp folder and that's what FUBARd here. Read this (disk health). Applies even to non-installer stuff.
Mylenium

I can open RAW files from my camera in photoshop cs5, but they dont save properly after editing

I can open RAW files from my camera in photoshop, but then after I have edited, i save as .raw, and open up the newly saved file and it just comes up as a grey messed up picture. What am I doing wrong?

r_r_a_a wrote:
I thought that it was preferrable to do editing on RAW files rather than TIFF for highest image quality.
Yes, it is preferable to do as much editing on the raw files as you can including global and local tone & color correction in Camera Raw...but there is a limit to the work you can do and sometimes you must go ahead and render the raw file into Photoshop for additional work. Then you'll be needing layers and other functionality that can't be done on a raw file. At that point you'll need to save as a TIFF or PSD. If you work in 16 bit and a large enough color space, the TIFF or PSDs will still be capable of the highest quality...as others have indicated, the Photoshop .raw file format ain't for photography per se.

Photoshop CS3 crashing on Save for Web & Devices

I'm having a problem with Photoshop CS3 crashing every time I use the "Save for Web & Devices" option. It allows me to open the dialog box and configure my file, but as soon as I click Save, it crashes. Has anyone else had this issue and if so, how did you resolve it?

Then manually remove the prefs by reading this:
http://forums.adobe.com/thread/375776?tstart=0

CS3 Crashes on "Save As" in Windows XP

Anyone come accross this and have a solution. I can't use the "Save As" command as CS3 crashes as soon as I try to alter the save destination.
Thanks

That is most likely unrelated to PS itself. More of an issue with your user permissions that do not allow you to peek outside the default user directory. Check your user status and promote yourself to Power User at least (XP Professional). Assuming you are on XP Home, simply create a new user account. It's easier than trying to clean up the tainted old account. Use the migration tool in yourt Accessories program group to transfer settings...
Mylenium

Indesign CS3 crashing on save HELP!!

Hi My indesign CS3 has started constantly crashing on save, save as or export. I have dumped my prefs dumped the library folder and reinstalled indesign, is there anything else I can try?
help!!!
Jezz
Mac OS 10.4.11 G5

Seem to have fixed it using this patch
in case anyone else has the same trouble
http://www.adobe.com/go/kb402521
Jezz

InDesign CS3 crashes without error when opening any 2nd InDesign file

Issue: InDesign CS3 crashes without error and remains resident in memory if we have an InDesign file open and attempt to open a second InDesign file.
OS: Win XP SP2
InDesign Version: 5.0.2
Hardware: Dell Precision WorkStation T3400, 4 gigabytes of memory, Intel Core2 Quad processor Q6600
Details: No messages in the event viewer about the problem. We renamed the InDesign Defaults and the InDesign Saved Data file. We removed Creative Suite, restarted and then reinstalled Creative Suite (I could not remove and reinstall InDesign individually). We have created a new Windows profile for this user. I have one computer having the trouble. Other InDesign installations are working fine. This computer has 559 files in C:\windows\fonts. Other people that are not having the problem have a larger number of fonts installed.
The issue is not file specific. We are not running out of memory as I checked the task manager after the first InDesign document is open.
Why is opening a second document different than opening the first document?

Hello Peter and Josh,
I'd just like to assert that I am having the exact same problem as Josh. I've spent the time to go through the steps listed above and have found the same results.
The issue as we see it multiple times daily is as follows:
(1) User opens File1 (everything works fine)
(2) User goes to open File2 (via explorer or via file->open) or print File1
(3) The User Interface for ID disappears (InDesign.exe still appears in Task Manager and is NOT listed as "Not Responding", ID does not appear in the Task Bar)
(4) The only way to continue work is to End Task/End Process InDesign.exe and relaunch.
No error messages appear, no error logs are created(that I can find). Non-related concerns caused us to upgrade this users PC. With a completely new install we are still having the problems. The systems are listed as follows:
OS: Win XP SP2 (fully updated minus SP3)
InDesign Version: 5.0.2
Newest Hardware: Custom Built Computer, 4GB RAM installed (3.24 recognized by windows), Intel Core2 Quad processor Q6600 @ 2.4Ghz
OS: Win XP SP2 (fully updated minus SP3)
InDesign Version: 5.0.2
Older Hardware: Custom Built Computer, Intel D945GTP Motherboard, 2GB RAM installed, Intel Pentium D processor @ 2.8Ghz
Troubleshooting:
(1) Alt+Space and M then using arrow keys moves every other window the user had opened other than In-Design. The user has two monitors. (a) 1280x1024 and (b) 1200x1600 (yes she uses the monitor rotated 90 degrees
(2) Log files - Non exist in the C:\Program Files\Adobe\Adobe InDesign CS3 folder. I've also done a search across the entire hard drive for any "*.log" files, none of which were adobe related.
(3) Default Printer - Changing the default printer to Adobe PDF is not really an option. I was able to convince the user to temporarily switch to a different networked printer and await the results (most likely today or tomorrow it should recreate)
(4) /3GB switch - Getting that last 700 something MB of memory isn't an issue. I've run MemTest.exe on all the available system memory overnight in a "burn in" test. The system ran fine the sticks were nice and warm when I got in from all the hard work :)
(5) Order of Opening - The problem repeates regardless of order. The trick seems to be opening File2 or printing File1 (I had the user only work on one file at a time (required her to close any open files before opening the next, that wasn't fun for my user but the system didn't crash on opening in this scenario, just on printing. Obviously not a permanent work around)
Any help here would be much appreciated as this has been plaguing us for months now.

Using Aperture 3.51 I am having frequent crashes and freez ups when editing Canon raw files?

HI,
I have an IMac with 4 G of Ram and am using Apeture 3.51. When trying to edit CS2 raw files I experience frequent crashes and freez ups of the whole computer. Any suggestions?

You didn't mention any color calibration being done on your monitor. This is an essential part of any color-correct workflow. What are you using to calibrate your monitor (and your printer)?
Print profiles (for soft-proofing as well as printing) are for specific combinations of paper & printer. The nine you have are each, most likely, for a common paper (perhaps mfr'd by Canon) to be used with your printer.
I don't know what you mean when you say "I choose a high standard print option".
Have you read the User Manual chapter on printing?
Printing Your Images
There is also a good appendix on calibration:
Calibrating Your Aperture System

How do I save Lightroom image edits in source file?

My experience with the trial version of lightroom is very positive in terms of the convenient and powerful capabilities for editing images and the associated metadata. But I can't find a way to save the "develop" edits to images into the source file for the photo I am working with. So far, I am able to save the metadata into the file but not the image editing. From what I read, I fear this is not possible without silly round about exporting to new files then copying / moving multiple copies around, etc. Without this ability, I am pretty sure I will not purchase lightroom and will miss out on all the powerful features. Without an OPTION that turns on the equivalent of a SAVE button, managing my photos collection would be a nightmare.
So my question is: How do I save the edited (i.e., developed) version of a photo back into the same file where the original photo was stored?
Please, please spare me all the reponses telling me how stupid I am for wanting to do this and that the cognisenti and professionals would NEVER do this. But please just tell me there is a secret place to turn on this option in lightroom.
Thanks in advance.

I had the same requirement to save in JPEGs files all non-metadata edits performed in Lightroom, in order to share modified pictures without duplicating files. By the way, I think it’s going to be more and more required by casual Lightroom users, as people get used to instant photo sharing in many situations where quantity matters more than quality
Here’s a nearly automatic (at least, scalable) solution that works, although it slightly lowers the quality by re-compressing the original pictures.
Once for all:
Download and install the wonderful Lightroom plugin “jf Run Any Command”, provided as donationware by Jeffrey Friedl here: http://regex.info/blog/lightroom-goodies/run-any-command. This “export filter” plugin allows you to run a command of your choice with each exported file, as part of the export while it’s going on. (You may also browse Jeffrey’s blog to find many other useful and beautiful things.)
In Lightroom, pre-define an export settings as follows:
Export to the hard drive, to the original picture folder, without adding the exported file to the catalog
Name the exported file “EXPORTED-{Filename}” (or anything different from the original file name)
JPEG format, 76% quality (see An Analysis of Lightroom JPEG Export Quality Settings at http://regex.info/blog/lightroom-goodies/jpeg-quality)
Keep all metadata
Here’s the interesting part, the Run Any Command settings:
Command to execute for each exported picture: copy "{FILE}" "{Path}\{LIBRARYFILENAME}" (this replaces the original file with a copy of the exported file)
Command to execute upon export completion: del {FILES} (this deletes all exported files).
NB: One could wonder why not directly export with the original file name and silently replace the original files (I believe Lightroom would allow this). It’s just a matter of error handling: in case the export goes wrong, no original file is changed at all.
The easy part: each time you want to save edits:
In Lightroom, select the pictures to save, and export them with the pre-defined settings. You're almost done. The JPEG files are ok, but inside Lightroom you see the modification effects doubled, as their specifications remain in the catalog database and they apply on modified JPEG instead of the original files.
While the entire set of "saved" pictures is still selected, in the Develop module switch Autosync on and click Reinit to erase all modification specifications from the catalog for all pictures, then press CTRL-S to write down to disk any metadata updated by Lightroom -and accept if required to confirm that Lightroom values should replace externally set values.
Stephane
PS: Papa Ben, I'm curious about the decision you finally made

Editing a DNG file and saving it again as DNG using Photoshop

Hi everyone,
I have a set of .dng raw images which I would like to edit using Photoshop and save back out as .dng files. It sounds like a very simple task, but I have been struggling with this for half a day.
To give a concrete example, I have two dng images from the same camera. I want to copy an object from one image and paste it to the other, and then save out the output as a .dng file. This should take me like 2 minutes in Photoshop, right?
Well, when I open the files, it first brings up the Adobe Camera Raw tool, but this only lets me do very basic edits (I can't figure out how to copy an object from one image to another, let alone perform the necessary edits to blend them seamlessly.).
So I click "Open Image" to get them into Photoshop, where I can do all of my necessary edits (copy and paste, brushes, etc.). However, after I am finished and I try to save my edits, Photoshop only lets me save the output in .psd (along with other formats) but not dng. I need to save it back out as .dng, as the next program in our workflow pipeline requires .dng files as input. So how do I do this simple task?
Why can't I save my resulting image back out as a .dng file? I tried saving as .psd and then using Adobe DNG converter to turn it into a dng, but it doesn't seem to be able to do that. I also tried saving as Photoshop RAW, but for some reason the converter can't convert from Photoshop RAW to DNG. It doesn't make any sense to me.
I know that Photoshop knows my camera parameters because it was able to read the original dng files properly in the first place. So why can't I read in the .dng image make some edits and then save it? How are people editing dng files?
Thanks for your help.

Also, there is no way to turn an image back into raw image data after it has been edited in Photoshop. It would be as difficult as uncooking an egg.
I understand that this is difficult if I am doing arbitrary image editing operations, since those operations may not be properly defined in the RAW space. But in this case I am cloning pixels from one .dng image to another. Shouldn't this be possible?
For example, assume we have 2 dng images and we want to take the left half of one and paste it in the same position over the other. I am not familiar with the dng spec, but at some level it should encode the values at each pixel (perhaps with the appropriate camera curve). So I just simply want to overwrite the values of one .dng image with values at the same pixels of the other, and since it's the same camera with the same settings used for both this should be possible, right? In the worst case, I could write a program based on the DNG spec that parses the two dng files, overwrites the necessary pixel information simply using the second image's data, and then writes the dng back out. But this seems like a complicated way to do something that there should be an Adobe tool to do.
Perhaps it would help if I tell you exactly why I need this for. We are capturing raw video using the Blackmagic Cinema Camera which outputs a directory full of 2.5k dng images for each take. We were doing a take of a scene using a tripod, but an otherwise great take was ruined because at one point a crew member poked their head into frame. So I want to use information from the other dng frames to overwrite this portion of this image to hide this problem.
If these were regular images (.jpg, .tif, .exr) it would take us no time in Photoshop to use the information from the other "good" frames to fix this problem seamlessly. However, we would like to keep everything in dng format so that I can then read everything into DaVinci Resolve for color grading correctly. Any idea on how I can do this, if I can't use Photoshop?
Thank you in advance for your help!

Are edits in DNG files considered metadata

I just experienced an unusual occurrance. I am using lightroom 5.2 on windows 7. I have been using lightroom since the original beta.
I just finished hours of editing DNG files. I selected all the thumbnails and dragged them to a collection. I noticed that after dragging them down that all the thumbnails showed the icon that there was a conflict in metadata. I selected all the thumbnails and reset the metadata. I lost all my edits.
Unfortunately, I had not yet saved a new catelog.
Is there any way to recover my edits?
Jim :-(

James Palik wrote:
I exited LR without backing up thinking that I wanted to restore my catelog from yesterday without realizing that there was a history file.
All that history info is stored in the catalog, it's not a separate file.
James Palik wrote:
Needless to say, I just finished redoing my edits. Nothing lost but about four hours - so not that bad.
Who among us hasn't experienced that, at least once? But saving xmp between catalog backups can be your saving grace - regardless of file format.
James Palik wrote:
It was my understanding that one of the advantages of converting to DNG is that you no longer needed to depend on the XMP sidecar.
No, no, no, ... - xmp may be embedded or it may be in a separate sidecar file, but you need to save it if you want it saved. I prefer to control that, i.e. I only save (manually) when I have an "edit milestone", the other option is to enable auto-save in catalog settings (Lr preferences), but then it saves your negative mistakes as well as your posititive milestones...
James Palik wrote:
I knew that the data was written into the DNG
To be clear, it's written into whatever file you've edited (DNG, jpeg, raw, ... ) when metadata is saved, and not if metadata is not saved.. The only difference in raw and the other file types is whether it's embedded or contained in a separate "sidecar" file.
James Palik wrote:
Is it my understanding that the when the catelog is backed up that it also has a backup of the meta data that I inadvertantly deleted.
No, really: not. Your catalog backup is just the active catalog, backed up - nothing extra...
James Palik wrote:
I really need to understand the catelog and its contents better.
One way: Get an app like SQLSpy and open the catalog and inspect each table. Much will look like gobble-de-guk, but much of the data is recognizable as what you see in Lr UI. I realize this may not be appropriate for all persons, still... (I'm not aware of any "what exactly is in the catalog" document for non-techy types - maybe somebody else will have a good reference..).
Likewise, you can load xmp sidecar files into a text editor to see exactly what is there, and what is not, if you want to.
Rob

Is it possible to edit a DNG file in Photoshop and get back to Lightroom?

Hi,
The question title probably doesn't explain much what I'm looking for...
I shot in RAW and then converted to DNG, I like DNG and I can't understand what so many people have against it, anyway that's not the point...
I know have the DNG as my digital negative instead of the original RAW file and I start to do some editing in Lightroom. But then I realized that Lightroom is not enough for something I want to do. For instance, just today I had this picture I needed to remove some people and I had to use heal/clone but as you know, Lightroom's clone and heal features are not as flexible as Photoshop ones.
So now I needed to go into Photoshop, fix the photo and get back to Lightroom and continue my editing. However, I couldn't find a way to do it how I wanted to do... What I did was open the original (unedited) DNG in Photoshop, Adobe Camera Raw pops up and I ignore it, remove the people from the photo and save as TIFF. Then, back in Lightroom I open the new edited TIFF and copy Lightroom's settings from one photo (the DNG) to the other (the edited TIFF).
This workflow sucks and I know there are some options in Lightroom to automate it, but still, I don't think it would solve my problem. At least I couldn't find a way to do it...
What I wanted to do instead was to indeed remove that people from the photo with Photoshop but keep those changes in DNG. But take a note here that those changes could very much be destructive, I'm not talking about ACR or Lightroom's non-destructive editing, the removed people would be gone forever unless I draw some new ones. I really wanted to edit and save some changes on the DNG in Photoshop and keep editing the DNG in Lightroom without using a TIFF in between, do everything in the DNG.
Is this possible or not at all?

Ricardo.Amaral wrote:
What I wanted to do instead was to indeed remove that people from the photo with Photoshop but keep those changes in DNG.
sorry, no can do...ain't gonna happen.
What you've done is hit the wall on is the basic difference between lite duty spot healing and photo level tone and color correction (Lightroom and Camera Raw) and heavy duty pixel retouching in Photoshop.
When you need to substantially manipulate the "pixels" you need Photoshop and you'll be forced to render the raw file into a TIFF or PSD file either through Camera Raw or more better, via Lightroom.
You can do the basic tone and color correction directly in Lightroom and edit in Photoshop from Lightroom. But you will NEED to create and save out a "rendered" image that is no longer raw...then retouch to your heart's desire, save it and it'll be available in Lightroom along side your original raw if you choose.
But no, there's no way to open a raw in Photoshop, manipulate the heck out of it with massive retouching then save that back out as a raw file...ain't gonna happen.

PS CS3 crashes at "Save as" after editing Hasselblad DNG file

Similar Messages

Maybe you are looking for