Hourglasses when saving in Elements 10

When I do file/'save as' for an edited photo, to rename it and convert it to a jpg file, and then close the photo in Editor, what shows up in Organizer is just the original unedited photo. The psd version and the edited version, which used to appear in Elements 5, are missing.
Or, if I switch from Editor to Organizer, the original and edited pictures appear as hourglasses. Double clicking on the hourglasses brings the two pictures up correctly.
This didn't happen when I first moved from Elements 5 to 10, it just suddenly began! Any thoughts, please?

Yes, Ken, the photos and the catalog are both on the network drive. I’ve now tried some things, which got rid of the hourglass, but produced another problem. I used File/catalog/repair, and said YES when it asked me if I wanted to remove the thumbnail cache. This resulted in removing the hourglasses and restoring most of the thumbnails, but a number now were daisy symbols. So I selected all photos, right clicked and chose update thumbnails. After a very long time it produced a list of ones which it couldn’t reconnect to missing files. I deleted these from the catalog, cheered – and started editing again.
Sadly, then I found that after converting a jpg to a PSD file in Editor, working on the photo, and saving it as a renamed.jpg, when I closed this and looked at Organizer, the new version didn’t appear. The file is on the hard drive, and can be retrieved by using File/get photos/from files. If I work on the jpg version in Editor, which I understand means resolution is lost, the edited version does appear in Organizer! Sorry it’s a long story – have you any ideas? (I couldn’t find anyone online mentioning that daisy symbol (attached). Patricia

Similar Messages

I have manipulated a photo using layers etc and then flattened it and saved it under a new name. When I use 'Preview' (mac) to view the finished photo it doesn't look right. It's as the layers have not flattened correctly. When viewed in Elements 12 it

I have manipulated a photo using layers etc and then flattened it and saved it under a new name. When I use 'Preview' (mac) to view the finished photo it doesn't look right. It's as the layers have not flattened correctly. When viewed in Elements 12 it looks OK. The photo looks incorrect in other software such as photo books.
Looking at the same photo before flattening, what is being shown is only the top layer.
How do I correct this?

STEVEN1A wrote:
I have manipulated a photo using layers etc and then flattened it and saved it under a new name. When I use 'Preview' (mac) to view the finished photo it doesn't look right. It's as the layers have not flattened correctly. When viewed in Elements 12 it looks OK. The photo looks incorrect in other software such as photo books.
Looking at the same photo before flattening, what is being shown is only the top layer.
How do I correct this?
The top layer is indeed the one that is visible, unless there is/are area(s) of translucency on that layer, so that you can visualize a portion of the subjacent layer.
the finished photo it doesn't look right. It's as the layers have not flattened correctly.
Are your settings targeted to have the printer manage colors, or, to have PSE manage colors?

Premiere elements 10 crashes when saving as DVD or DVD folder, etc.

Hi [me again!]
While awaiting resolution for PRE7 and PE7 'registered' licence 'not accepted' problems, my other Premiere elements 10 crashes when saving a Project as DVD 4.7Gb folder or direct to DVD or 'any other DVD way'.
The repeated windows error report I get is this:
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    Adobe Premiere Elements.exe
Application Version:    10.0.0.0
Application Timestamp:    4e791009
Fault Module Name:    wdmaud.drv
Fault Module Version:    6.1.7601.17514
Fault Module Timestamp:    4ce7c9f8
Exception Code:    c0000005
Exception Offset:    000000000000f827
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    2057
Additional Information 1:    c1eb
Additional Information 2:    c1eb94943c7b4efb7ee314d92a94924b
Additional Information 3:    7d3f
Additional Information 4:    7d3fe30533dcbba28d68d00b60422c7b
In the meantime I am evaluating the 'cheaper' and without installing / working / DVD problems and possibly send Adobe discs back for full refund.
My Laptop is fast enough and well kept - not other 'larger' programmes have any problems running or installing [Stenberg Cubase Pro, Flight Simulator X and so on] only Adobe programmes!
I am really getting tired now.
Regards
Mobon

Hello
All problems are carefully separated - not all together, since I am a tidy person by default.
It is very simple and not confusing.
I actually have one main issue with PE7 and PPE7 [which I hope they will care of] and a series of small teething problems as many in these forums have on Premiere 10 since installation because Adobe programmes have 'basic' problems even loading / reading/ converting its own created files.
I looked up for Premiere Elements problems on-line [on external forums] and I can see so many problems and people opting for alternative programmes or getting 2 or 3 different programmes to do the job faster and better - that confirms my thoughts.
I am not here to stir things up [if by any chance you are thinking that], but I am merely trying to use a PAID and SUPPOSED to be GREAT program and it is clearly not my friend.
But if I get pushed up around and treated like a non-in-the-computer-field-person, then I might 'need to' stir things up with 'proves'!
I have been working with computers Hardware and Software since 1975 with the Sir Sinclair Spectrum .
So, I do know one thing or two by working 'manually' and without the 'easy' mouse clicking [!] and my main job these days is to actually fix People's messed up computers, recover data, erase data, etc. and often I find either Apple's or Adobe's programmes not working properly [being the main problem on slower computers] and users tried to fix them and messed things up!
Mainly is Apple programmes [ iTunes is one!] on Windows environment - just pure mess.
In fact I do not keep ANY Apple Programs on ANY my computers any-more and by adding the blooming QuickTime - it actually adds 3 'mostly not needed' applications that must be run in the background only slowing down 'most standard' computers and 'mostly' for no apparent reason but needed by Premiere Elements 10.
Adobe Acrobat Reader too is a kind of an offender in that sense, which I do not use any-more in favour of an alternative and very light program that does not invade your computer.
I could be talking about the above for days ...
The fact I do not know Premiere 10 very well and I am having some teething problems with 'Adobe Premiere Elements 10' does not make me a lower being or anything to the like or even put me aside the forums for being realistic and a human being most of all.
I simply am an Intermediate / Advanced / Professional Computer User / Repairer [depending on which subject] trying to fix this non-working-properly Adobe's program and get on with his life.
You as an employee perfectly know what I am talking about, the Adobe numerous problems with Elements and pro and the clever Marketing and money making tool Adobe has created around it and I do understand you must keep Adobe's side - of course and that is not a problem at all.
BACK TO THE ONLY PROBLEM THIS THREAD IS OPEN FOR:
Having said that, in the meantime I seem to have solved it myself [as I do most of the time], at least for now.
I am sure many other problems will arise.
My Solution that worked:
I simply clicked on the time-line [bottom] and then clicked on top menu TIME-LINE [if I am not wrong, it was late night and I might be wrong - do not crucify me please!] and MERGE CLIP and then I let the program do the job I purchased for.
Days ago using the Trial Version [before I purchased Premiere 10] I already read that Premiere does not like either large gaps [I did not have] or even simple clip cuts not merged and it did have 'loads' of problems, but most of them were solved by 'users' mostly.
Anyway, that seems to have done the trick, even thou it did take around 4/5 ours to do 3Gb ! Why?
My computer is fast.
But I have not checked or burned the files yet - so, I do not know100% - just yet, I will check later on today.
I believe Adobe must prepare a Service Pack with 'Loads' of fixing, there is no place to hide and that may convince users to even 'spend' and buy the PRO version - the ball is in your court now.
I cannot believe Premiere is having so many small teething problems and I am only doing a BASIC test and I can see the vast majority of users of Elements Programs going literally insane and only us, the more Techy ones coping.
Regards
M
PS the fact you see an avalanche of problems with my installation is actually normal.
That is because I am a 'fast' and organised Computer Technician which gets on with things and I usually do this with all new programmes to get rid of the possible initial several small hiccups, that other Companies usually fix with Patches - not Adobe, it seems - at least with Premiere elements.
In the last few years are mainly with Adobe Programmes. It is the only way to get the 'basic' program problems fixed straight away, so I do know the next time I run it actually works!
ADDITION:
IT WORKS!
Message was edited by: mobon

Adobe Elements 9 not responding when saving changes

Adobe Elements 9 says not responding when I save image changes. I does eventually save the image changes but takes awhile. Is this normal? My computer is rinning Windows 7 and I have 8GB of ram so I don't think that ram memory is the problem. Thanks

In other versions of photoshop elements, you don't get the not responding
thing at the top of the screen when saving png files, but it still takes a noticeable
amount of time to save png's in other versions of photoshop elements and the full
photoshop version.
I haven't been able to find it yet, but there is a post somewhere in the photoshop forums
where an adobe photoshop engineer explained why png's take longer to save than most
other file formats, but ssprengel said something about the compression of png's which
sounds like the gist of the post.
There have been more than a few complaints about the not responding messages in pse 9
on windows machines for various operations, but as far as saving images, the not responding
message doesn't seem to hinder saving files, but it is very annoying.
You might try posting here where several adobe employees answer questions:
http://feedback.photoshop.com/photoshop_family/topics
MTSTUNER

Can one embed the complete font (not a subset of it) when saving as an EPS in Illustrator (CS4)?

We are running into some display font issues when our clients use Acrobat 7 or older versions of reader to view our PDF proofs. On occasion, subsetted fonts conflict and reveal question marks instead of the desired type in the final PDF.
We use a proprietary composition system to perform the majority of our file composition, but use Illustrator for tables and charts. Our composition system requires imported elements to be saved in the EPS file format. As far as I can tell, there is no way to have Illustrator embed the complete font rather than a subset of it when saving the file as an EPS. Please correct me if I am wrong?
All help is greatly appreciated.

Russel,
I appreciate your advice.
To answer your befuddlement, the PDF supplied to our client is generated from a PostScript file created from our proprietary composition system. Unfortunately, the casue of the subset conflict is occuring prior to the PDF distillation. We do not create the PDF in Illustrator. Our proprietary composition system can only import the EPS file format for linked bitmap and vector images. The moment the EPS is saved is where the issue is occuring. A redistill further downstream (when the EPS and composition files are already combined in the PostScript) does not appear to eliminate the conflict.
If there was a way for us to embed the entire font and not just a subset of it in the EPS that we export out of Illustrator, then the likelihood of a subset conflict occuring in the PDF during distilling would be eliminated. Fortunately, the question marks only show up when the PDF is displayed on screen in Acrobat. The output from this same PDF looks fine when sent to a printer. Considering the size of our print runs (often in the millions) and the importance of all type displaying properly (risk of large SEC fines), the explanation that the job will print correctly even though it displays improperly does not satisfy our clients.
We can not convert the text to outlines since the fonts would appear slightly heavier in the tables than they would appear in the portion that is composed in our proprietary composition system where the same font is used.
Any other ideas?

After migrating to a new MBP, when saving or opening documents, I sometimes (but not always) get a warning such as: "Word cannot save this document due to a naming or permissions error on the destination volume." Can someone please explain?

I recently migrated from a MBP with OS 10.6 to a MCB with OS 10.8. Some glitches are popping up. Here's the one on my mind at the moment:
When saving or opening documents, I get a warning such as: "Word cannot save this document due to a naming or permissions error on the destination volume." Can someone please explain?

Since this is isolated to a single file, try exporting it to Interchange Format (.inx), then open and save the resulting file as a new InDesign file.
Since the problem occurs during export, that may not be possible. Another option to try would be to copy all elements, page by page, and "paste in place" into a new document the same size. If you used layers, be sure to enable "paste remembers layers" in the layers panel menu.
This kind of problem is often indicative of an underlying font issue. You said there are only three fonts, and you should verify that in Type > Find Font... Try replacing, at least temporarily the fonts in use with something else that you know to be reliable from other documents. You might want to do this before the other steps.
Peter

Problem with lowercase when saving in custom SAP table.

Hi Gurus,
I have a problem in saving entries in a custom table in SAP.
When I enter a name with combinations of upper and lower case in SE16, when saving, my entries were all converted into uppercase. That goes as well in passwords. That's my concern, how can I check passwords if combinations were disregarded?
My parameter fields for these were just type CHAR.
Is there a way I can save data as how they were entered?
Thank you in advance for your responses Gurus...

Hi,
Check the Domain of the field and select Lower case check box if it is a Zdomain or else create the new domain or check for one like this.For example..
Table PA0002 which has a field NACHN and Data element assigned to it is PAD_NACHN...double click on the Data element and now again double click on the Domain and now Under Ouput Characteristics check the Lower Case check.
And now database get's saved with what ever case you entered

In VA02 transaction which exit is triggering when saving the data

hi all sap gurus,
In VA02 transaction which exit is triggering when saving the data

Hi Reddy,
The user exit and badi tried for this transactions are
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
V46H0001 SD Customer functions for resource-related billing
V45W0001 SD Service Management: Forward Contract Data to Item
V45S0004 Effectivity type in sales order
V45S0003 MRP-relevance for incomplete configuration
V45S0001 Update sales document from configuration
V45P0001 SD customer function for cross-company code sales
V45L0001 SD component supplier processing (customer enhancements)
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45E0001 Update the purchase order from the sales order
V45A0004 Copy packing proposal
V45A0003 Collector for customer function modulpool MV45A
V45A0002 Predefine sold-to party in sales document
V45A0001 Determine alternative materials for product selection
SDTRM001 Reschedule schedule lines without a new ATP check
Business Add-in
BADI_SD_SCH_GETWAGFZ Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001 SD Customer functions for resource-related billing
Reward pts if found usefull :)
Regards
Sathish

[svn:osmf:] 14797: Decouple MetadataGroup from synthesizer API, MetadataGroup should only be linked in when a composite element is used.

Revision: 14797
Revision: 14797
Author:   [email protected]
Date:     2010-03-16 16:34:48 -0700 (Tue, 16 Mar 2010)
Log Message:
Decouple MetadataGroup from synthesizer API, MetadataGroup should only be linked in when a composite element is used.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/compositeClasses/CompositeMetadata.as
    osmf/trunk/framework/OSMF/org/osmf/metadata/Metadata.as
    osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataGroup.as
    osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataSynthesizer.as
    osmf/trunk/framework/OSMF/org/osmf/metadata/NullMetadataSynthesizer.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/compositeClasses/TestCompositeMetadata.as
    osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestMetadataGroup.as

The Morena 6.0 - Image Acquisition Framework for Java(tm) Platform from http://www.gnome.sk is a package which enables you to connect to your scanner or a camera in a very intuitive way.
If you just want to see how Morena works with your scanner or camera:
- java (1.2 or higher for Windows, 1.3 or higher for Mac OS X) has to be installed on your computer
- a scanner or camera has to be installed on your computer
- download the trial package from http://www.gnome.sk
- unzipp it
- go to the examples directory of the unzipped package
- in Windows: doubleclick the runExampleShow.bat
- in MacOS:
- open the Terminal window
- change the working directory to the examples
- run .sh file (type ExampleShow.sh or sh ExampleShow.sh)
This will pop up the Twain Source Selection user interface. There, all your scanners and cameras which do have a twain driver should be listed. (About 90% of scanners and cameras on the market do have a twain driver for Windows, only a few do have a twain driver for MacOS.) Select one of them. The user interface of the selected scanner (camera) will appear. Confirm the scanning (you can set the scanning parameters first). The scanned image will be displayed in a separate window. To end the application, close that window.
Running different examples, you can test scanning with hidden UI, saving the scanned image, using ADF, taking images at regular intervals (ExampleCamera) ...
To see how Morena works in applets, go to the online remote examples http://www.gnome.sk/Twain/remote/www/twain/server/php/remote.html
If there is any problem, do not hesitate to inquire about it at the technical support, email: [email protected] or join the online forum at www.gnome.sk
Erika Kupkova

Colour shift in save for web when saving on PC and then viewing on Mac

Hey peeps, I am aware of this colour shift when saving images for web. I have a designer resizing, cropping photos, and then saving on PC. He uses PC and when he sends the photos over to me on my Mac there is a big colour shift (photos are much lighte
Could anyone please explain exactly what he needs to do in order for these photos to look the same as the originals on my computer, basically no lightness shift? Any help would be much appreciated.
Thanks
Adam

Because the WWW is based on untagged (2.2 gamma) sRGB - your genius is probably sending you untagged sRGB if they were Saved for the Web (that's how I prepare my Web color).
Your Mac display should be profiled to 2.2 gamma (you are likely at the old default 1.8 gamma now if you're seeing a lightness shift on untagged sRGB)...if you want "your color" back in Photoshop, you will need to (re)Assign the sRGB profile...

The niFPui.mxx plug-in caused an exception in the CmxAggregateItemUI::InvokeCommand function in the NIMax process. When saving *.iak file in MAX4.6

The niFPui.mxx plug-in caused an exception in the CmxAggregateItemUI::InvokeCommand function in the NIMax process. When saving *.iak file in MAX4.6
Hi There,
The subject header just about says it all. This is the first action I took with MAX - it is a fresh install. The file I wanted to save was still written and the FP seems to be working ok. However, I need to know what happened.
I can't post the whole log file due to the amount of characters allowed on this post. I can cut and paste sections if there is a specific part of the file you need. Below is the first section and last section.
Context where exception was caught:
Func:
CmxAggregateItemUI::InvokeCommand Args: plugin=niFPui.mxx Item=0107EAB1
cmdID.cmdId={4A36174B-EC0C-4D73-A23D-F15D164542DE} cmdID.index=0
Application   : C:\Program Files\National Instruments\MAX\NIMax.exe
User Name     : slaney
OS Version    : 5.1.2600 (Service Pack 3)
Exception Code: C000001E
Exception Addr: 457BC448
Return Address: 457BC448
Function Name : nNIFPServer::tFpLinearScaleRange::`vftable'
Module Name   : FieldPoint71
Parameters    : F001008E 7800FDDD C5100DFC EC0107EA
Source File   : (not available)
Return Address: 481000C3
Function Name : (not available)
Module Name   : (not available)
Parameters    : 00000000 00000000 00000000 00000000
Source File   : (not available)

Hi,
I did a research on your error message and it seems this problem was introduced with MAX 4.6. This version switched to a new error reporting mechanism and reports even errors that are which are not critical to your task.
These errors typically show up as "unexpected" and if your error falls into this category have a look to this KB for further assistance.
If it doesn't fall into this category, your could try to go back to the MAX 4.5 or 4.4.. Of course you would need to reinstall some components and might not be able to use newer drivers at all.
Let me know.
DirkW

Page shows different data when saved after few minutes

Hi,
I have a peculiar problem to describe.
I have a page which contains af:table inside af:panelCollection layout. I use a af:commandLink to drilldown to another page using setCurrentRowWithKey method.
I am able to drill down to the correct data in another page which contains data that is editable. Once after editing the page when i click save button, i am able to save the data. This is working fine.
But the problem is, once i drilled down to this edit page and edit some fields and save it after few minutes, say 5 minutes later, it is not saved. Also, the page is refreshed to bring some random record.
Can anyone let me know why is this happening and how to resolve it?
Thanks

Hi Timo,
Which jdev version?I am using jdev 11.1.1.3.0.
Is it possible that the data has changed (e.g. by an other user) after you drilled to the one record you want to change?There is a possibility that the data can be changed by other user as well. But, for the time being we have implemented for the single user environment.
When you click save after some time, do you get any error (on the screen or in the logs)?Yes. On the screen, it is displayed as "oracle.jbo.JboException: Document type mismatch (source INVOICE, type Sales)". It is a validation exception thrown at viewRowImpl level by me. But it validates the data perfectly when saved immediately after editing
Which session timeout do you have configured in your web.xml?Session-timeout is given as 240
Have you tried your use case with the HR schema?Yes. when i reproduce the situation in HR schema, it is getting saved perfectly
Regards

Print program is not getting triggered when saving the application

Hi all,
My requirement is when i save the invoice using VF01 the print program should get triggered.
The print program is not getting triggered when saving the application even when i have configured the outtype and have attached the print program.
The setting "send immediately (when saving application)" is also checked.
I need to configure it for VF01 transaction.
The error message displayed was " please maintain output device in master data".
Regards,
Umesh

Hi Umesh
Please check if you have missed any of the following:
1. Defining Access Sequence(can use existing).
2. Defining Output Condition Type(can use existing). - Assigning the Driver Program and Form in processing routine.
3. Output Determination Procedure
4. Assign Output Procedure to Billing Types
Kind Regards
Eswar

Downloads Folder No Longer Jumps Up When Saving Attachments

When saving attachments in Mail, my downloads folder on the Doc used to jump up a couple of times when I hit "save" from within an email that I received to signify that I just saved it into that folder.
However, for no rhyme or reason, the downloads folder no longer jumps up when I save attachments. The attachment still save in to that folder but I miss the pop-up action telling me that it did.
I searched the net and posts and found nothing on this quark. This is driving me nutz!
Please help!

Check in System Preferences>Dock and check off Animate opening applications and see if that doesn't do it. Not sure if that is why but it is worth a shot.

Errors when saving to SMB mounts (a thorough examination)

Several of the users I support have reported the following issue when trying to save files to the network from Photoshop. I have found several threads about this on both the Adobe forums and the Mac forums. However, in most of the threads the information provided is incomplete or does not control for enough variables. And the result is that Adobe seems to blame Apple, and Apple seems to blame Adobe. So blame aside, here is information that I hope helps Adobe solve the issue at hand.
When saving to a mounted SMB point, users report one of two errors:
Could not save <filename> because of a program error
Could not save <filename> because write access was not granted
I can replicate the issue on:
Lion 10.7.X with Photoshop CS 5
Lion 10.7.X with Photoshop CS 5.1
Snow Leopard 10.6.X with Photoshop CS 5
Snow Leopard 10.6.X with Photoshop CS 5.1
Details:
We have only seen this error in Photoshop. << Adobe has seen the same problems in several other applications >>
I have not tested out whether the issue applies to any other products in the CS suite.
At first I thought the issue might have to do with permissions, but it does not. I have reapplied permissions and the issue persists. And it affects all users, including Domain Admins, such as me, who have no R/W restrictions at any level.
The issue only occurs when Finder is in a view that shows a thumbnail/preview of the image.
Switching Finder to list mode resolves the error in all scenarios
So far I can replicate this with any file on any mount on any of our servers
It only occurs on mounted network points (ie - if I move the files locally, no errors are encountered)
For the following tests, presume the following:
Source folder: smb://example/source/folder
Target folder: smb://example/source/folder
Target sub-folder: smb://example/source/folder/sub
Here are the steps I tested:
Opened the file problem_file.psd.
A warning pops up prompting me to resolve a font vector issue, I chose "Update"
Note: that this error does not pop up for every file, just the original file I worked with, but this warning has nothing to do with the errors being received
Moved a layer so that there would be a change to save
Clicked save
Received the error: "Could not save <filename> because of a program error" << probably related to the known MacOS bug on SMB, or a known Finder/thumbnailing bug >>
The original file, problem_file.psd, is *DELETED* (very problematic) << Known MacOS bug in SMB service, Apple is working on it >>
Then I tested with multiple variations of the following to conrol for things such as layers or font issues:
To eliminate the source file being the issue, I used a .png file that I had created locally with the OS-X screen shot keyboard command. This eliminated layers and fonts as issues.
In step 2 I chose to not update the font vector issue
In step 4 I tried saving as different file types (.jpg, .png, .gif)
Prior to step 6 I flattend the image to eliminate fonts and layers. This eliminated layers and fonts as issues.
Prior to step 6 I flattened the image, duplicate the image, closed the original (without saving), and attempted to save the new duplicate. This eliminated layers and fonts as issues.
Each variation still resulted in "Could not save <filename> because of a program error" and resulted in the deletion of the source file.
Next I controlled for saving image previews:
Photoshop -> Preferences -> File Handling
Under File Saving Options -> Image Previews, I set it to "Never Save" previews
Now when I repeated the tests from aobve, I receved the error "Could not save <filename> because write access was not granted".
Next I controlled for .DS_store files:
Disabled .DS_Store file creation on remotely mounted points.
Deleted the .DS_Store file for the source folder
Verified that .ds_store files were not being created on remotely mounted points
Ran the tests above, and the issue persisted: "Could not save <filename> because write access was not granted"
Now I decided to test sub-folders:
Created a target sub-folder.
Repeated the test above, and its variations, but saving the problem_file.psd to the target sub-folder.
Still received one of the two errors, depending on the variation, but the source file is no longer deleted. This make sense because saving in another directory is really a "save as", and one would not expect safe saving (talked about more later) to affect source files in this scenario.
Sort of a Solution:
Open the file from Finder
Depending on the Finder view, Finder shows a thumnail of the image
Go back to Finder and select a different file
Make changes to the file
Save the file
No error is received
This is when I discovered that the error only occurs when Finder is in a view that shows a thumbnail/preview of the image. Further testing of Finder show that in Cover Flow the error only occurs for the selected image. For example:
Cover flow shows thumbnails/previews of files: A, B, C, D, E
Open A
In Cover Flow select file B
The thumnails of of files A, B, C, D, E are still visible
Make a change to the open file
Save the change
No error is received
This shows that Finder is treating the thumbnails/previews of unselected files different than selected files.
An Interesting Twist:
If from the last scenario with Cover Flow...
Open file A
Go back to Finder and select a different file
Then make a change and attempt to save to the target sub-folder
Receive the error "Could not save <filename>" because of a program error.
Discussion:
Photoshop does something called safe saving.
Photoshop saves the current document to a temporary file with a unique name
Photoshop deletes the original file << this is incorrect >>
Photoshop moves the temporary file to a file with the name of the original file that was deleted in step 2 << incorrect: the temp file replaces the original with an OS call to a function that is supposed to be an atomic operation >>
However, you can see that "safe saving" is misnamed, because while the original is deleted, Photoshop does not appear to be correctly ensuring that permissions exist to allow the temporary file to be ranemd or that the temporary file was renamed without error. Photoshop is either:
Not checking for the error << yes, it is >>
Checking for the permissions and not catching the error << incorrect >>
Checking for the permissions and giving an error to generic to discern the exact problem from. << also incorrect >>
Somewhere there is a conflict (perhaps a race condition) between:
Photoshop creating the temporary file
The server applying permission to the newly created temporary file
OS-X reporting the file has been created
Photoshop deleting the original file
Photoshop saving the new file
Finder updating the thumbnail of the file
As I've shown here, the problem doesn't seem to reside fully with Apple or fully with Adobe. Hopefully this post provides enough information for some clever engineer to create a fix.
My information about safe saving is from an Adobe mod on a previous thread regarding this issue << and copied incorrectly, plus added bad assumptions>>. He detailed the process and also explained that Photoshop uses OS APIs to create and delete the files during safe saving. If his details are accurate, it seems that a temporary fix would at least change the safe saving process to the following:
Photoshop saves the current document to a temporary file with a unique name
Photoshop moves the original file to a temporary backup file (original-file-name.original-extension.bak)
Photoshop moves the temporary file to a file with the name of the original file moved in step 3
Photoshop checks to make sure that the temporary file has been succesfully renamed
If the temporary file has successfully been renamed, it deletes the backup file from step 2 OR if the temporary file has failed to be renamed, the backup is returned to its original file name
The appropriate error message, if any, is displayed
A Few Sources:
http://adobe.hosted.jivesoftware.com/message/4016324
http://forums.adobe.com/thread/732422
https://discussions.apple.com/thread/3380971?start=0&tstart=0

You got several details wrong.
And it sounds like you are describing 2 known MacOS bugs:
1) The OS fails when creating or swapping files on SMB servers, and this happens more often on files that have a resource fork.
2) The Finder/QuickLook/Thumbnailing holds a file busy when it should not, causing program errors or file is busy errors.
We did as much as we could to work around these issues in Photoshop CS6 - after spending a lot of time debugging the OS issues and working with Apple.
Apple is still working on proper fixes within the OS.

Hourglasses when saving in Elements 10

Similar Messages

Maybe you are looking for