File Name Character Limited to 31 - New or something I've done?

I have been using my MacBook Air with Mavericks for ~6 months and just started getting file name size limit of 31 character warnings a few days ago. I have many files saved with much longer file names but now cannot go over the 31 character limit. Have I inadvertantly changed a setting or is this something new in a recent update?
Bottom line - how do I get back to using longer fle names?
MacBook Air, OS X Mountain Lion (10.8.4), MBA 11" Loaded (1.7G / 8G / 512G)

call Apple Care - 800-275-2273
But I doubt that you will get FaceBook support from Apple - I'd suggest calling FB support
LN

Similar Messages

Need to add date/time stamp to file name without time change creating new files

We have setup our application to save data once a trigger event occurs. We also need the date/time stamp as part of the file name. We used Format Date/Time String and concatenated it into the file name. It all works good, but as the time changes (seconds, minutes, etc.) it causes the Write to File to create a new file with the new filename. Is there a way to create the file and save/latch/buffer the time in the file name so that it doesn't create a new file for every second?
I've attached a shot of the relevant part of our VI. It's all in a big while loop. The data save is in a case/switch so that when it is triggered it starts saving. (The for loop is to split the data up
into 4 different files). Like I said, it all works except new files are created every second as the time changes instead of just putting it all in one file with the initial time in the file name.
Attachments:
TimeInFileNameQuestion.jpg ‏46 KB

I need a loop in order to use a shift register. I cannot stop the outer while loop (because it would stop the hardware from collecting data), and I cannot add loops inside which bogs down the processor to where the app stops. I've attached a simpler version of my VI which illustrates the problem. While the button is pressed (the trigger) it should save the data (in this case just cycle numbers) into one file with the initial date/time. But, you can see that it creates 1 file/second. I tried using shift registers, but without adding extra loops I can't see how to do it. Thanks
Attachments:
FileNameTest.vi ‏29 KB

File name character encoding in zipped file

Hi All,
I have the following problem: I have received a zipped file which contains a folder and file structure. The file was zipped on Windows XP with Czech language. The problem is that the folder/file names use Czech characters (codepage CP1250). The characters in filenames after unzipping the structure are corrupted.
Is there any way how to define the codepage during unzipping or, more in general, way how to convert file names in one codepage to UTF-16 used in Mac's file system?
Thanks for ideas.

You might give this a try for converting the filenames after unzipping, though I think it is designed for the old Mac CE encoding rather than the Windows version:
http://support.apple.com/downloads/FileName_Encoding_RepairUtility
Otherwise the only option may be manually converting the text strings with something like TextWrangler.

How can we change the file name character limit on PSE 7?

When I save for web I need more than 26 characters in the file name. Can you please tell me how to turn this Mac compatibility option off? Thanks.

Save the file with a short name and rename afterward.
Juergen

File Name not set when creating new file in EP 6.0 SPS20

Hi,
We recently upgraded from EP6 SP15 to SP20. Now when I create a new file or folder in a KM folder, the name that I give for the resource is not taken into account. The display name of the newly created resource will be New Text or New HTML Document or New Folder, etc. Even if I open the Properties and change it there, it is not getting reflected. But if I select Rename from the Context menu and give a new name, it gets set. What could be the problem?
Thanks in advance
Regards
Ranjith

Hi,
It was an issue with the customized PropertiesControl class.
Regards
Ranjith

Save For Web - saves original file name not new name

Hello, when I use Save for Web with slice(s) the original file name (appended with the slice number) gets saved even though I have changed the file name in the save dialog. This only happens about 50% of the time. Sometimes it saves as expected - with the new file name. I am using the default settings in the save dialog all the time.
Stranger is that if I am saving (for Web) say 10 slices some will be named with the original file name and some will be saved with the name I gave it in the save dialog.
This was happening on my Windows XP sp2 system when I was saving to an Ubuntu server (local network). So when I switched to a new computer running windows 7 and saving to a new server (windows 7 pro) I thought it might fix the problem - but it has not. So there must be a setting I am missing - though that does not account for the intermittency of the problem. I have changed settings under "custom" in the save dialog and things do change except the original file name is persistent not the new name I have given it.
The PSD files come from a designer using a Mac.
My system:
PS 10.01
Windows 7
AMD x2 duo 250
4 gig Ram
Thank you for any help you may provide
jim

I made an action to save large batches to a designated "pics" folder. Then when I'm done with a big batch, I just move them to the original folder and let the OS overwrite them. May seem like a lot of work, but I can do a batch of 500 gallery thumbnails in about four minutes and it takes about 30 seconds to move them and replace the originals.

File name too long cannot copy (cont'd)

This is a continuation of the post started September 01, 2009, with the last post on
October 17, 2011 named File name too long cannot copy
Since this is an ongoing unsolved issue, and the thread was locked, it continues here.
It is ever so easy to create a long file/path using explorer.exe as will be shown below.
What needs to be solved is, what is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were)
too long to copy, (and then perhaps even copying those over either intact or renamed)?
Maflagulator said:
I'm running the 7100 build...enjoying it except for one big thing:
While attempting to copy 402gb from my main storage volume onto a spare 500gb drive (for the purpose of changing to a new RAID array) I've come across something that I would expect a Windows 98 OS to give me.
It tells me that a file has TOO LONG of a file name, then provides with two unhelpful options: SKIP or CANCEL
I never had XP give me an issue like this at all, so what gives? And while some specific files did have long file names (such as for songs, etc.) it had 7 issues with folders stating that their name was too long, but in fact they were not since they were
titled '07-06-07' for the date that I dumped the audio files in them. However, they may have contained FILES with long file names though.
Anyone else get this same situation? Perhaps the RTM version does not do this? Can anyone verify this regarding their install of the RC or the RTM?
It made it through 400gb out of the 402gb transfer.
I'm just happy to see that it doesn't spazz out about an issue like this until it has done all the other transfers that it can do because it saves the issues it has with files until the very end. In XP it would spazz about it the moment it came across it
causing the transfer process to halt.
Since long path/file names can so easily be created on Win7, it might be useful to see a typical way this happens, which might then give clues how to work with them.
In Windows Vista, we learnt from:
File names and file name extensions: frequently asked questions that:
Windows usually limits file names to 260 characters. But the file name must actually be shorter than that, since the complete path (such as C:\Program Files\filename.txt) is included in this character count.
In Windows 7, we are told here:
File names and file name extensions: frequently asked questions that:
It depends on the length of the complete path to the file (such as C:\Program Files\filename.txt). Windows limits a single path to 260 characters. This is why you might occasionally get an error when copying a file with a very long file name to a location
that has a longer path than the file's original location.
From the Windows Dev Center - Desktop, we read about Maximum Path Length Limitation here:
Naming Files, Paths, and Namespaces
This helps us understand why a folder can be a maximum of 244 characters, from the defined 260 length of MAX_PATH as follows:
260 minus C:\ (3) minus <NUL> (1) = 256
256 minus 8.3 file name (12) = 244
We also learn there that: The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
And we read the claim that: The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not be able to interpret properly.
There is also a comment below this document that reads: In a previous iteration of this document, it is mentioned that The Unicode versions of several functions permit a maximum path length of approximately 32,000 characters composed of components up to
255 characters in length. This information is now gone.
So we are in a position where the file system and Windows API can create long path/flies that the shell cannot handle.
But then we need to be able to handle it, so a little exploration might lead to a better understanding of how to do this.
For most tasks being performed on long folder/files, Windows 7 and other Windows programs balk when the Path+Filename length > 260
Let's create a long path/file.
Create a folder called A at the root of a Drive.
Create a sub-folder of A called: B
Create a sub-folder of B called: C
Make a FILE in sub-folder C called (no spaces or break, one long continuous string): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X123456.txt
Rename sub-folder C to the string (no spaces or break, one long continuous string) (The actual directory created will be slightly shorter than this full length): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456789Y123456789Z
Rename sub-folder B to the same full string above. (The actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
Rename folder A to that same full original string. (Again the actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
You now have the lovely file placed at (the breaks are just so it fits into the screen):
C:\123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X1234\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X12\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456.txt
You have a folder length of over 700 and a file length of over 250 for a total of over 950
However you will notice that each folder, when created, could only be a maximum of 247 charachters including the path (example C:\ , & C:\A , & C:\A\B
This only applies backwards, that is up the path. It did not matter what was further down the path.
Now, you can't easily access or rename the file, but you can rename the folders easily.
For best results, start renaming from the top of the Tree, working down the subfolders, because renaming from down up will limit you, and in fact won't work if the folder lengths are too long.
So how might knowing this help us?
Well, to copy this long_file from the C:\ drive to the D:\ drive, and keeping the path structure, this should work:
Note the name of the top folder. Rename it to something very short, say: A (Make sure C:\A does not exist)
Note the name of the 2nd folder. Rename it to something very short, say: B (Make sure C:\A\B does not exist)
Note the name of the 3rd folder. Rename it to something very short, say: C (Make sure C:\A\B\C does not exist)
Make sure D:\A does not exist - then copy the A folder on disk C: to disk D: (which gives you D:\A\B\C\long_file
Rename D:\A\B\C to D:\A\B\Original_3rd_Folder_name
Rename D:\A\B to D:\A\B\Original_2nd_Folder_name
Rename D:\A to D:\Original_top_Folder_name
Rename C:\A\B\C back to their original names, in this same reverse order starting with C, then B, then A
Note: If using Explorer, at some points you might have to press the F5 refresh key.
This is of course how you might copy such long path/files without using the other more "easy" techniques for the "normal" everyday user like:
sharing a sub-folder
using the commandline to assign a drive letter by means of SUBST
using AddConnectionunder VB to assign a drive letter to a path
using the "\\?\" prefix to a path string to tell the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system
and so on.
See how simple Windows can be for Dummies!
But then, how can we know that files to be copied exceed this MAX_PATH? Or also after a copy has taken place, know exactly which files that have NOT been copied because of exceeding the MAX_PATH limit, and then a procedure to copy these either by renaming
them, or by copying them intact as they are?
There have been suggestions to use
LongPathTool, but this does not have a facility to check a series of folders and tell you which files are going to be caught by the error when copying. So once a copy has taken place using Windows 7, one does not know which files did not get copied, and
where exactly they are located.
Neither does the free
Old Path Scanner do that. It can only check for overly long directory paths, but misses out when the directory path is within limits, but adding in the file name puts it out of bounds.
So, as shown above, it is ever so easy to create a long file/path using explorer.exe
So, what then is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were) too long to copy,
(and then perhaps even copying those over either intact or renamed)?

This is a not a "solution" ....but a "work around": a low tech fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
1. problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
limit, the error appears). The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
2. How do you know which combined file names + path names are too long if you are in the middle of a copy operation and this error pops up? Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
files are the "too long" ones. If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files. Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
3. Here's how you sort out the "bad" from the "good":
4. Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong
 There are five levels root "1 football" with subfolders 2, 3, 4 and lastly "5 injuries"
5. Use "cut" and "paste" (for example to backup all five levels to a new backup folder):
 select "1 football" ....cut....select target folder....paste
 ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
 Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
character limit"...instead "paste" to a C:/ root directory.
 Suppose in the middle of this operation...error pops up: "5 files have file names that are too long" Skip or cancel?
 select "skip" ...and let operation finish
6. Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
7. You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
 C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
8. select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
9. hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
 like this: 5 injuriessidelineplayers ....you should delete 'toolong'....from the folder name
10. then go into folder 5....and do the same operation ...with the too long file name:
 hit F2 rename file....file name hightlighted...delete some of the letters
 like this: injuriessidelineplayers.....you should delete 'toolong' from the file name
11. Now..."cut and paste" the renamed file to the target backup folder.
The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
12. Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty)
Of course, this "makeshift" solution would not be necessary if MSFT would fix the problem...

File name generated when saving a process file

When I choose to save a file (save as for instance) I get an odd
looking default file name with a ~ in it such as; ne6e29~1.l4p. Why?

Leo,
I agree, that is an odd file name. I am not sure where the "~" is coming from. I am using Lookout 5.1 on a Windows XP machine. If I open a new process and use the default process name "Process1", the same name is appears in the "File name:" field of the "Save Process File As..." window when I navigate to File >> Save As. Even if I choose another name for my process, that name is then used as the default file name when I go to "File >> Save As."
If you save your process with another name, such as "myprocess.l4p", does the same default name appear when you go to "File >> Save As"?
I have seen the "~" character used in other applications when a file name exceeds the maximum length but I do not recall having that problem on newer OSes like Windows 2000
or XP. I tried to save a process with a really long random file name on my machine and I was still unable to reproduce the behavior you are seeing.
What version of Lookout are you using and what OS are you running. If your process is running on an older OS or you are using an older version of Lookout, it may be that the file name is limited to fewer characters.
Regards,
Aaron C.
National Instruments
Applications Engineer

Destination file characters too long (File names) , while copying from one external to another

I have a external my book fat32 formated and a new mybook ntfs formated external as well. Now when I copy my files from the fat32 to the ntfs external all files copy fine but some give that destination location file characters are too long, meaning that the file names are too long. Now I could change the file names but that would conflict with programs that need that file name. I am using vista ultimate and would like to copy all the files over from the fat32 to ntfs so I can reformat the fat32 to ntfs. The files got on the ntfs from a simple drag and drop from my IDE NTFS internal hard drive.
I hope you guys to tell me what to do.
Thank you :)

Here's the fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
limit, the error appears). The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
2. How do you know which combined file names + path names are too long if you are in the middle of a copy operation and this error pops up? Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
files are the "too long" ones. If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
3.   Here's how you sort out the "bad" from the "good":
4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong
       There are five levels root "1 football" with subfolders 2, 3, 4 and lastly "5 injuries"
5.    Use "cut" and "paste" (for example to backup all five levels to a new backup folder):
       select "1 football" ....cut....select target folder....paste
       ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
      Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
character limit"...instead "paste" to a C:/ root directory.
       Suppose in the middle of this operation...error pops up: "5 files have file names that are too long" Skip or cancel?
       select "skip" ...and let operation finish
6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
      C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
9. hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
       like this:   5 injuriessidelineplayers ....you should delete 'toolong'....from the folder name
10. then go into folder 5....and do the same operation ...with the too long file name:
        hit F2 rename file....file name hightlighted...delete some of the letters
           like this: injuriessidelineplayers.....you should delete 'toolong' from the file name
11. Now..."cut and paste" the renamed file to the target backup folder.
The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
12.    Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty)

Problem loading Image data with French accent in file name

We have a very complex commercial application that has been working perfectly in English for over a year. We have now localized it to French and Spanish, and discovered a serious show-stopping problem. We need help fast, with the scheduled release being less than 2 weeks away...!
We iterate over a folder to find all the images in it, then display those in a user window. The code for loading the images is:
            for each (var name:String in filenames){
                var image:SmoothImageTransformable = new SmoothImageTransformable();
                var imagePath:String = dir + "/" + name;
                image.source = imagePath;
                trace("Adding Item to picture carousel with url " + image.source);
                image.data = {directory:dir, filename:name};
                image.isDragEnabled = true;
                image.setStyle("horizontalCenter", 0);
                image.setStyle("verticalCenter", 0);
                _images.push(image);
Our SmoothImageTransformable class is an internal class that inherits from Image. This all works fine for image names like 'myFavoritePhoto', 'test', 'photo346', etc. However, it fails to load the data if the file name is something like 'caméra' Any name with a UTF-8 character causes the data load to fail.
To be sure we weren't doing a load somewhere else in the code that I had overlooked, I added a "image.autoLoad = false' line in there. That did exactly as expected -- all image squares then show a grey blank, with no image shown. Removing that line (reverting to the original code, as shown above) causes all the images to work perfectly, except for those with French accent characters like the é.
HELP! Is this a known bug? Is there some additional setting I need to make it understand the extended character set? I can't find any mention about this at all in the documentation.

@markerline:
We have a fix! Almost... I don't understand one aspect of what I am seeing though.
We have one test file named "camèra.jpg" that is an example of what I am unable to load into an Image. I decided to examine the character codes at each letter, and this is what Flex has as the string:
name = cam?ra.jpg
   [0] = c; 0x99
   [1] = a; 0x97
   [2] = m; 0x109
   [3] = ?; 0x232
   [4] = r; 0x114
   [5] = a; 0x97
   [6] = .; 0x46
   [7] = j; 0x106
   [8] = p; 0x112
   [9] = g; 0x103
Note that the è prints as gibberish in the trace statement, and shows a numeric encoding of 0x232. According to
     http://docstore.mik.ua/orelly/web2/action/appb_01.htm
The unicode equivalent of Latin1 for è is 0xE8, which is equivalent to 0x232. That implies that the string is already Latin1, which I would think would mean that Windoze would recognize the file name and open it properly -- but it does not.
I then tried taking the "camèra.jpg" string, pasting it into NotePad++ in a UTF8 document, then telling NotePad++ to display as ASCII. The result is "camÃ¨ra". I then tried just forcing the file name within Flex to this new mangled string. The result then is:
MAGIC name = camèra
   [0] = c; 0x99
   [1] = a; 0x97
   [2] = m; 0x109
   [3] = ?; 0x195
   [4] = ?; 0x168
   [5] = r; 0x114
   [6] = a; 0x97
   [7] = .; 0x46
   [8] = j; 0x106
   [9] = p; 0x112
[10] = g; 0x103
Note this time the trace statement looks proper. More important, the IMAGE DOES LOAD! (Our display of the name to the user now looks like crap, but that just means I need to modify our class to have a separate 'name' property, rather than extracting it from the 'image.source')
So... my remaining question -- what encoding did I just do through that NotePad++ incantation? That site I quoted above said that it was already Latin1, which is what I thought I was trying to get to. I clearly need to write a method to map from incoming (UTF8 I thought, but maybe Latin1?) to Windows file system (Latin1 I thought, but maybe ASCII).
In other words, I am not sure what charcter set to come from or go to... It turns out the code was already in the character set I had been trying to go to (which is why it wasn't working) and the set I seem to need to go to is not the one I thought...

Batch rename files preserving the original file name in metadata

How can I batch rename files while preserving the original file name in metadata? (Don't want the old file name as part of the new file name)
(Adobe CS Bridge can do this with some success, but I don't want to be dependant on this software. Results are inconsistent.)

With a simple terminal script. More details needed, though.

File Name in Place command changes

I have Photoshop CS5 on a MAC and have developed actions that use the Place command.
The initial recorded action places a file called FILENAME.PSD into the currently open file.
If I use the Finder to rename this external file (outside of Photoshop) to FILENAMEBAK.PSD, Photoshop will keep track of that change and change the file referenced in the Place command to FILENAMEBAK.PSD.   My intention was to back up the original file and replace it with another new revised file. If I then put another file with the name FILENAME.PSD into the same folder, Photoshop will still keep track of the original file regardless of the name change.
I have also tried doing this with Photoshop completely closed and yet it still keeps track of the original file. Surprisingly, I've even moved the original file to the trash and the Place command in the action will still find the file in the trash.
Can someone help me understand exactly how Photoshop is keeping track of the file? I always assumed actions were very unintelligent and simply followed the instructions as they were written but in this case, the action is somehow linked to the file and it's not just the file name.
Any help/insight is appreciated.
Rob

so I don't know when this changed
To be honest, It may never have changed. Whenever I have tried to have files linked with Actions I have pysically replaced the file. Its very easy to duplicate files by option (alt) dragging them, thats how you create a copy in OSX. You then can then over-save the original with an amended version.
Another probably better solution open to you in Photoshop, that you may not be aware of, is to use Smart Objects and the "Replace Contents" feature? This can also be automated.
The problem is that what the Action step says about the files location and name is in fact technically inaccurate if you move or rename the file.
What I'm trying to figure out now is how I can manage symbolic links manually. Or, is there something in Photoshop where I can force the action to look only at the specified name and path.
I don't have time now to experiment with this now, but you could try rebuilding the "Launch Services" or "Display of Folders content" databases. I don't know if this will work. But one word of warning - Its not a quick process!

Export List of File Name with Faces Identified

I'd like to export a list from Aperture, into any file format - Words, Numbers, rich text, MS Word, MS Excel, anything!!
The list would show the file name and all the faces identified in that file.
My daughter is in her High School dance team. I've taken more than 1000 photos. Here is is the end of the season and I'd like to distribute the photos among the dancers/parents. They don't have the software or care to take the time to sort through the pics to figure out which photos they are in. I'd at least like to give them a list of photos so that can find the ones
Faces can be a helpful feature (though I hate all the file versions all over the place in iPhoto and Apeture).
I've read that Faces is not stored in the metadata of the file. I've tried to export metadata, but not much comes out other than the standard file size, camera settings, etc.
Easier to describe the situation, I guess, but would be helpful for many photos with people (weddings, parties, reunions, genealogy photos ...)
which is Faces is supposed to be about, RIGHT???
I guess a work around could be exporting the files from the identified faces. That seems like it would just junk up more storage/memory. I guess you could use a file list naming app and then delete the exported files - that just seems stupid.
I expect a little more from a souped up version of iPhoto for $79. Especially if I have Adobe Creative Suite with Bridge. If Apple wants to give a little shove to Apple, and bring novice users from looking for a non Apple solution, I think this would be an EASY no brainer.
Thanks anyone who has a solution of a decent work around.
Beth in Wisconsin
Aperture 3.06
Adobe Creative Suite 6

Dear Kirby, Thank you so much for your reply.
I'm familiar with Metadata. I've worked with Canto Cumulus and Filemaker.
I guess a more important question - where is the Faces data stored?
I'm looking to export a text version by file name, such as in a spreadsheet. Something like this
File Name     PhotoFile_01.jpg     PhotoFile_01.jpg     PhotoFile_03.jpg
Faces ID'd    Nina Totenburg        Carl Kasel               Tom Ashbrook
Faces ID'd    Carl Kasel                Peter Sagel
Faces ID'd    Terri Gross               Terri Gross              Nina Totenburg
Faces ID'd     Renee Montaigne    Tom Ashbrook
OR
File Name                    Face 1               Face 2          Face 3               Face 4
PhotoFile_01.jpg         Bob Braun         Tina Fey        Andy Warhol
PhotoFile_02.jpg         Leah Jones       Beyonce        Tina Turner      Dave Matthews
PhotoFile_03.jpg         Lisa Liu            Geena Davis
Anything that would identify the faces in a photo to a text file ....
Yes I understand that most of the IOS software is supposed to make it easier for the new and less techie user. But if you are going to create all these versions and mini files for the photos, why not make them accessible to a power user. I'm not a coder, but I've been using macs for 25 of my 40 years.
What gets me is that you go to the trouble of identifying all the Faces. What is Faces really supposed to help you with?
I mean Facebook is better at face recognition than this. Don't go on a tangent - about this - just sayin'.
Thanks for your time!
Beth

How do I change file names in "Windows Friendly" attachments before sending?

In sending some "Windows Friendly" attached images, I want to change the file names so they are meaningful to the recipient. (I don't want to change the file name in my picture catalog, just for this mailing.) In Outlook on an old pc, I remember being able to right click and rename the file in the email draft. I've tried right clicking on the image (which looks embedded in my draft), but there is no option for renaming. I can't see the file name in my draft to figure out another way to change it. I'm sure other people want to do this when sending other types of files, so there must be a way, right? I'm using the current version of Mail.
Thanks!

I'm pleased to have helped, if you are mailing images all the time perhaps you could create a new folder on the Desktop or in Finder/Username store your images in the folder rename the images click Drag & Drop more than one at a time but don't make the package too big!

Changing trace file name giving odd results - 10.2.0.2

Hello,
I'm trying to run a trace on a particular session. Using this:
execute dbms_monitor.session_trace_enable(122, 58)
It creates a tracefile in udump just fine. I turn tracing off:
execute dbms_monitor.session_trace_disable(122, 58)
Then the trace usually catches the next sql statement after I issued the disable and I've got a complete trace file.
If I use the statement:
alter session set tracefile_identifier = 'TEST';
With or without quotes, what ends up happening is the tracefile is created with TEST tacked onto the end but what's inside the file is the full path to the file itself, no trace. The previous trace file before setting the identifier then gets all the trace output. This is on Red Hat. After this the only way to get tracing to work again is to close both sessions and start over.
Am I forgetting to set another parameter when doing this? The litteral set of steps is:
-open session 1
-open session 2
-session 1 run alter session set tracefile_identifier = 'TEST';
-session 1 run execute dbms_monitor.session_trace_enable(122, 58)
-session 2 run some sql
-session 1 run execute dbms_monitor.session_trace_disable(122, 58)
-session 2 run another sql statement
-check the udump for the trace file
Now the ultimate goal here is to be able to tag a trace with a name so I can trace a specific session (made by an application) and then find it later in udump. If the tracefile_id needs to be set in the offending session...well then I need another solution.
Thanks

Once the session starts writing to the trace file it
is going to write to the same file until the session
is closed.
Until the session is closed...aaahhhh gotcha. Well that explains that.
I tried the above with a new session and immediately set the identifier and got the same result, except it created the default trace file name as well as the new identifier copy with the path in it.
The logon trigger might be a workaround but it's not killing me at the moment.

File Name Character Limited to 31 - New or something I've done?

Similar Messages

Maybe you are looking for