File Bundle - File Version Changes

Now that I have the file bundle issue fixed, I have come across another issue:
I have a file Bundle with two files. One of which is a Perl script that changes every now and then. I tried to remove the file from the Bundle, add the new file, apply, and then deploy the new Bundle. The Bundle installs as planned, but the new version of the Perl script is not distributed.
Do I need to create a new Bundle for each version of the Perl script?

On Thu, 18 Oct 2007 15:46:10 +0000, skeplin wrote:
>
> Just re-read the TID again -- I didn't have a secondary server so I
> should be OK.
>
> Still have the problem with the file versions though...
I tried this right now on my testserver and after correcting some
directory permission problems it worked.
Can you see that the filesize has changed in the file bundle details
after you upload the new version ?
Also check that whenever a modification to that bundle is made (files
uploaded or someting like that, not when changing assignments) a new
version has to be created and to be deployed.
After you upload the file do not forget to press apply at the bottom, that
will generate a new version that has to be deployed on top of that screen.
After it has been deployed it should be delivered to the device after the
refresh interval or you send it a refresh command.
If you still expect some problems, check the tomcat logfile on your zlm
server when you upload a new file for some errors:
/var/opt/novell/log/zenworks/tomcat/catalina.out
Rainer

Similar Messages

Hello, in former Versions it was available to mark text in a pdf file and change it. How do I have

Hello, in further Versions it was available to mark text in a pdf file and change it. How do I have to act, to do the same in Acrobat XI? Also I need to now, how can I import a graphic file into a pdf to add my handwrote signature or a picture of mine? Please help me soon. It is urgent.

Moving the discussion to Acrobat Forums

A Good Reference for Aperture, Versions, File Names, Changing & Moving

I was wondering if there is a consensus on a good reference for understanding how Aperture handles files?
Versions and file names.
How do you change them in Aperture?
What happens if you change them in Finder?
Do I need versions? (can't I just us file names?)
What about moving the masters, or changing where there are located at in Finder?
Can I do that in Aperture?
Can I only do that in Finder?
Should I never do that in Finder?
The reason I'm looking for a good reference is because I haven't found one. The user guide (or manual) that comes with Aperture doesn't help with these issues. Search file name and nothing comes back.
I did get a copy Apple Pro Training Series book for Aperture 3. But I don't think it does a good job explaining how Aperture's file system works, especially in relation to Finder.
Rather than fill this forum with endless questions (which could be answered by reading the manual and using it the software) I'd like to get a better understanding, from a good source.
I've only used iPhoto for Mobile Publishing, ATV and now Photo Stream. I don't use it to organize my decades of photos. I don't like having all my photos inside a managed database, which I don't have to do with Aperture. I never understood why you'd want to change the name of a photo in iPhoto, when it never changes the file name. If you send it to someone, after you changed it's name, the other person gets the photo with the original (still in Finder) file name.
Thanks.

I never understood why you'd want to change the name of a photo in iPhoto, when it never changes the file name.
This may help or not but here goes.
There's a distinction to be made between files and the data they contain. The example I use is as follows: In my iTunes Library I have a file called 'Let_it_Be_The_Beatles.mp3'. So what is that, exactly? It's not the song. The Beatles never wrote an mp3. They wrote a tune, some lyrics, recorded it and a copy of that recording is stored in the mp3 file. The file is just a container for the recording. That container is designed in a specific way attuned to the characteristics and requirements of the data. Hence, mp3.
Similarly that Jpeg / tiff/ raw/ whatever is not your photo, it's a container designed to hold that kind of data. And along with that data comes opportunities: Metadata, for a start. Exif and IPTC contain vast amounts of information - some it very basic, like the date and time the shot was taken - some of it quite complex, like a lot of details of the settings used in the camera.
Aperture, iPhoto et al are all about the data and not the file. Import the file and forget about it. Process the image - crop it, fix red eye, run it through the whole gamut of tools in the App and the file never changes at all. Create multiple versions of the image. But there's still only one file. Name it. You name the photo - and that is an entry in the Exif or IPTC. The name of the photo has nothing to do with the name of the file. Because the file is just the tin for the beans.
Even when you export, unless you specifically choose to export the Master, you are exporting the processed Photo into a different container - that's why you can export Raw as Jpeg, or Jpeg as Tiff. Because the process of export just puts the image into a new container.
Basically, if you want to manage files you need to use a File Manager. But you're using a Photo manager and expecting it to behave like a file manager.
And, of course, apps like Aperture and iPhoto have the option to use the Title of the photo as filename on export to the new file.
Does that muddy the waters?

What is, "Portrait Displays" displayed: "version changed bad license file".

Monitor: w2207h. Nvidia GeForce 8300GS 128MB graphics card. a6437c #KJ400AA-ABA. Vista Home Prem 64 bit. [email protected] 4GB memory. New July 4, 2008. Sam's Club.
Uninstalled "My Display" (display driver), per advice this forum in '08 or '09.
Guessing this driver enables landscape/portrait display swith when monitor rotated. Don't know what else.
Thanks in advance
Dean2011
[email protected]

Hi,
Go to NVIDIA and download and install the latest NVIDIA video driver.
Go into the Control Panel ---> NVIDIA Control Panel and locate the rotate display function.
If the above solves your issue except for the message issue then I would delete out the Pivot software.
The "version changed bad license file" message sounds like this issue.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

How to change bundle short version to a higher number?

How to change bundle short version to a higher number?
Apple has rejected my dist-view file as my old version of the app had a bundle short version key of 1.5 but DPS makes a 1.0 version. I believe that only Adobe can change this. Can you please tell me who to contact?

Thank you.
The App name is Exploring Essential Anatomy. app id: eea19102012. The folder number is 2.1. Using DPS app builder 2.3.2.70.60038.
The bundle version is 2.8.0.4.59944
The bundle version short string is 1.0.3
The problem is that the old bundle short string (of my previous build using xcode) is 1.5.
Hence new short string needs to be 1.6 or higher.
Sorry, not sure if this is the info you need

Use of xsdconfig file to change doc. elmt. name?

I've got the following simple xsd file:
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="/my/ns"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="Outer">
<xs:complexType>
<xs:sequence>
<xs:element name="Inner1" type="xs:string" />
<xs:element name="Inner2" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Which produces a "document" class named OuterDocument with a member "element"
class named Outer.
But let's say I need a different name, so I use the xsdconfig capabilitiy to direct
the name change. Here's the xsdconfig file:
<?xml version="1.0"?>
<xb:config xmlns:xb="http://www.bea.com/2002/09/xbean/config"
xmlns:xai="/my/ns">
<xb:qname name="xai:Outer"
javaname="NotInner"/>
</xb:config>
I now get a document class named NotInner with an element class not very elegantly
named NotInner2. Ideally I'd either like a NotInnerDocument with element NoInner,
or I'd like to specify name transformations for both. Is there any way to do
this?
Thanks in advance for any advise.

Hi,
Letting an application edit files to change names and terms looks like an ugly solution, apart from any difficulties that arise (such as rights on directories and files). I think it's best to create a separate output (one project, multiple webhelp outputs) each specified for the client.
To do this, I can come up with three usefull features:
1. CBT's: look into conditional build tags. With these, you can keep topics/text/etc out of certain outputs.
2. Variables. In RH8, you can create multiple sets of those (same variable, different value) and use the separate sets for separate outputs.
3. Multiple style sheets. In RH8, you can select which style sheet you want to use for your topics when you create the webhelp. You can create a separate style sheet for every different brand and use those style sheets when you output your files.
Hope this helps,
Willam
This e-mail is personal. For our full disclaimer, please visit www.centric.eu/disclaimer.

Upgrade Error when starting the DB ora-00201 control file version

Hi Experts,
While Upgrading R12.1.1 Vision database version from 11.1.0.7 to 11gR2on RHEL 6 64bit Plateform the following patches 've been applied successfully on apps tier
According to note ID: 1058763.1
Patch 7303030 , 9062910 , 8919489 - Oracle E-Business Suite Techstack 12.1.3 Product Release Update Pack ANd 9868229 - 10163753 - 11071569 -
9738085 - 9852070 - 12686610 - 6400501 Applied without any Issue.
On DB tier i.e 11.1.0.7 these patches are applied successfully According to metalink Note *[ID 1058763.1]*
Oracle Database Upgrade Guide 11g Release 2 (11.2) And Complete Checklist for Manual Upgrades to 11gR2 *[ID 837570.1]*
*7695070 - Change In The Timezone File Format*, And 13417321 -14112098 DST Changes For DSTV18 -7695070
Than we 've. Downloaded the 11.2.0.3 x86_64 software (of patch 10404530) Installed 11.2.0.3 on this Location /u01/oracle/VIS/db/tech_st/11.2.0.3
the Old ORACLE_HOME is /u01/oracle/VIS/db/tech_st/11.1.0.7
AND after that
On 11.2.0.3 home, applied these additional 11.2.0.3 RDBMS patches successfully according to metalink Nots Mentioned above :
*4247037 , 9858539, 3) 12942119 ,12960302 ,12985184 ,13001379,13004894 ,13258936 , 13366268,*
Now Need to Run utlu112i.sql on existing 11.1.0.7 oracle database.. for that started the listener But when i tried
to startup DB from sqlplus prompt. got this ora-00201 control file version error,
We Unable to start the Database in order to run the utlu112i.sql on existing 11.1.0.7 oracle database..
Please advise. we are doing manual upgrade.
Thanks
Priya

Please verify the value of COMPATIBLE initialization parameter.
Troubleshooting ORA-201 ORA-202 [ID 948710.1]
OERR: ORA 201 control file version <num> incompatible with Oracle version <nu [ID 18286.1]
Thanks,
Hussein

Default for opening pdf files keeps changing back to 'save file' after I set it to open in firefox

Since upgrading to the latest Firefox version, my options for opening adobe pdf files have changed. I set it to 'use Adobe Acrobat in Firefox', it works absolutely fine, then some time over the next few days it changes itself back to 'save file'. Then I have to open options and change it again. This happened to me some years back with a much earlier version of Firefox - I can't remember how it was resolved, I think it just stopped doing it after a while. But it is most irritating!

I echo the request for Help! I've added Options to my Toolbar so I can more easily change "Save File" to "Use Adobe Acrobat (in Firefox)" as the default. Why does Firefox keep reverting to the save file default?

ORA-00201: control file version 10.2.0.4.0 incompatible with ORACLE version

Hi,
I have upgraded the database from 9.2.0.4 to 10.2.0.4 and for some time compatible parameter remained 9.2.0.0.
Recently i have changed compatible parameter to 10.2.0.4.Now I could open the database with pfile but when I am trying to open database with spfile then I am getting following error:--
SQL> startup
ORACLE instance started.
Total System Global Area 1694498816 bytes
Fixed Size 1299532 bytes
Variable Size 1342180276 bytes
Database Buffers 343932928 bytes
Redo Buffers 7086080 bytes
ORA-00201: control file version 10.2.0.4.0 incompatible with ORACLE version
9.2.0.0.0
ORA-00202: control file: 'C:\ORACLE9I\ORADATA\UPGRD9I\CONTROL01.CTL'
OS=Windowxp 32 bit
Database version=10.2.0.4 32 bit.
Please share your experience with me.
MK

Yes,everything is set to 10g only with spfile I am getting this error.
When i am starting it with pfile it is opening and running good the onle thing I can not enable alter system set db_file_recovery_dest_size=5G scope=both bcoz spfile is not being used .I started using pfile and created spfile from pfile and then bounce the database startup then I am getting above error.
Mk

Access file type changing

iPlanet-Web-Proxy-Server/3.6-SP6/2004.243.0654 SP6
Obj.conf Init section:
Init fn="flex-init" access="/web/soft/3.6proxy/proxy-ntsmtcmlon01-acl-xrp1/logs/access" format.access="%Ses->c
lient.ip% - %Req->vars.pauth-user% [%SYSDATE%] \"%Req->reqpb.proxy-request%\" %Req->srvhdrs.clf-status% %Req->
vars.p2c-cl%"
Init fn="load-types" mime-types="mime.types"
Init fn="init-proxy" timeout="300" timeout-2="15"
Init fn="init-dns-cache" status="on" dir="/tmp" semas="4" size="512" expire="3600"
<Object name="default">
NameTrans fn="reverse-map" from="http://someurl.com" to="http://someurl.com"
NameTrans fn="pfx2dir" from="/ns-icons" dir="/web/soft/3.6proxy/ns-icons" name="file"
NameTrans fn="map" from="/" to="http://someurl.com"
PathCheck fn="url-check"
Service fn="deny-service"
AddLog fn="flex-log" name="access"
AddLog fn="urldb-record"
</Object>
Server starts fine and the access file type is ascii text
As soon as someone hits the site the file type changes to data
These were migrated using the interface and I ahve also tried tobuild a new site and get the same results.

If the server gets a small request GET /f5/proxy.html all is fine. When it gets its first request longer than that it starts corrupting and you can see part of the first request in the second request log entry. It happens on any every server I have that was migrated . I have also created a brand new site through the GUI and get the same results.
Once I stop and start the site the logs are fine until a first long request.
All of this started when I migrated to this version.
Thanks for all of your help!

CS4 Photoshop.exe file name changes

Has anyone had the CS4 Photoshop.exe file change names? I have had this happen on a couple of computers, one machine it happened twice. When CS4 is installed, the Photoshop file name is Photoshop.exe, at some point, the file name changes to PHOTOSHOP_CS4.EXE. I'm going to check with our sys admins to make sure they aren't doing some software push that might be changing it, but thought I would post here in case it was a known issue.

When you find the culprit you might let him know that different Photoshop versions always live in different Program Files subfolders.
-Noel

How can/should I handle file versioning during a TFS Continuous Integration Build?

Hi all,
First, I've gone through many docs, links, etc to get a test Build Server up and running along with a successful first Build Definition using both the default and a customized template. I say this because the question(s) I'm about to ask may have been
buried in all that information that is now swirling around my head.
First it might be advantageous to quickly look at what we do now. In our script we have Major, Minor, Build, and Revision variables that are manipulated both manually and in code. Let's say we are creating a version 10 of our product. I
will go in and edit the Major (10), Minor (0) and Build (0) numbers manually before that versions first script run. The Revision number is bumped by 1 with each subsequent build. So, build one of v10 will be 10.0.0.1, then 10.0.0.2, etc.
This 4 segment version is then used to set the PRODUCT version of the compiled files.
Later in the build script, we do a dance to get three position version number for our Windows Installer packages since Microsoft only utilizes #.#.# in that realm. It's basically Build# * 256 + Revision# or something to that effect. This
is then passed in to the package. I guess this part of it could or will need to be handled with an external script and InvokeProcess, which is fine.
My main concern deals with how versioning works within the confines of a TFS Builds. I believe I read something about tokens that may be the answer. What I would like to happen is that all FILE versions are bumped automatically with each build.
I don't know if there is a setting that can be utilized within each solution/project that could handle that or not. Then I'm hoping I can somehow get the Major, Minor, Build and Revision numbers for script use, etc.
Is there a canned way of going about this or should all of this be scripted in some way with maybe Pre MSBuild/compile script set up in the Build Definition.
Any help/guidance with this would be greatly appreciated!
THANKS IN ADVANCE!!!

Hi NitLions,
Thanks for your post.
Do you mean that you want to custom assembly file version in each CI build? As far as I know there’s no an standard way of changing the assembly version as part of each build, you can refer to the solution in this article:
http://tfsbuildextensions.codeplex.com/wikipage?title=Build%20and%20Assembly%20versioning%20%28alternate%20to%20above%20using%20SDC%20Tasks%29.
Or the information in this article:
https://tfsversioning.codeplex.com/documentation.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Whenever I modify a photo in Iphoto it puts it in a "modified" subfolder. Why can't I move this modified file (I changed name) back to the Iphoto main file so I can see it when I open my photos?

Whenever I modify a photo in Iphoto it puts it in a "modified" subfolder. Why can't I move this modified file (I changed and saved file name) back to the Iphoto main file so I can see it when I open my photos?

A good general step for strange issues is to renew the iPhoto preference file - quit iPhoto and go to "your user name" ==> library ==> preferences ==> com.apple.iPhoto.plist and trash it - launch iPhoto which creates a fresh new default preference file and reset any personal preferences you have changed and if you have moved the iPhoto library repoint to it. This may help
This does not affect your photos or any database information (keywords, faces, places, ratings, etc) in any way - they are stored in the iPhoto library - the iPhoto preference file simply controls how iPhoto works - which is why renewing it is a good first step.
If that does not cure it backup up your iPhoto library and rebuild it - depress the option and command keys and launch iphoto and use the options there - exact option depends on teh version you have
And always remember - NEVER make any changes of any sort to the structure or content of the iPhoto library - nothing - no deletions - no name changes - nothing
LN

CS4 opens unchanged file with changes made to different saved file

Ok, I searched for this but couldn't find anything. Probably because I have no idea what is happening. 1) I opened a raw file from a CD in photoshop cs4, lets call it photo1.nef. 2) I saved the file with a different name on my HARD DRIVE after making changes, photo1b.tif. I did not in any shape or form save the file on the CD (can't anyways). 3) Now, whenever I open the original file, photo1.nef on the CD it opens with all the changes I made previously to the file saved as photo1b.tif (remember this is the original unchanged file not the file I changed). But, when looking at thumbnails it appears to be the unchanged version of the file. I have closed photoshop and deleted all my temp files and still it opens the file with the changes, even though other programs open the file in it's original state without any of my changes. How do I stop this? I think I may be going nuts over this! Help! My wife is laughing at me when I show her.

Sounds like you may be using a centralized cache for your Camera Raw adjustments (as opposed to sidecar XMP files). Check your preferences inside Camera Raw or do an Edit>Camera Raw Preferences from Bridge.
You should be able to clear the edits by right-clicking the image in Bridge and selecting Develop Settings>Clear Settings.
Only Adobe programs are going to use those edits by the way. That's why opening the file in other programs doesn't show them.

"Date Modified" for all files being changed if "Automatically write to XMP" is on

Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
Is anyone else seeing this? Any ideas would be greatly appreciated!
-- David
diff Exif5609_original Exif5609_update
2c2
< FileName: DSC_5609_original.JPG
> FileName: DSC_5609_update.JPG
5,6c5,6
< FileModifyDate: 2009:11:27 21:32:54-08:00
< FilePermissions: rwxr-xr-x
> FileModifyDate: 2011:08:07 22:06:47-07:00
> FilePermissions: rw-r--r--
27a28,29
> ShutterSpeedValue: 1/200
> ApertureValue: 7.1
55d56
< SerialNumber: 3209521
75d75
< Lens: 18-200mm f/3.5-5.6
185,188d184
< UserComment:
< SubSecTime: 00
< SubSecTimeOriginal: 00
< SubSecTimeDigitized: 00
211a208,299
> XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
> CreatorTool: Ver.1.00
> MetadataDate: 2011:08:07 22:06:47-07:00
> SerialNumber: 3209521
> LensInfo: 18-200mm f/3.5-5.6
> Lens: 18.0-200.0 mm f/3.5-5.6
> ImageNumber: 26634
> RawFileName: DSC_5609.JPG
> SavedSettingsName: Import
> SavedSettingsType: Snapshot
> SavedSettingsParametersVersion: 6.4.1
> SavedSettingsParametersProcessVersion: 5.0
> SavedSettingsParametersWhiteBalance: As Shot
> SavedSettingsParametersIncrementalTemperature: 0
> SavedSettingsParametersIncrementalTint: 0
> SavedSettingsParametersExposure: 0.00
> SavedSettingsParametersShadows: 0
> SavedSettingsParametersBrightness: 0
> SavedSettingsParametersContrast: 0
> SavedSettingsParametersSaturation: 0
> SavedSettingsParametersSharpness: 0
> SavedSettingsParametersLuminanceSmoothing: 0
> SavedSettingsParametersColorNoiseReduction: 0
> SavedSettingsParametersChromaticAberrationR: 0
> SavedSettingsParametersChromaticAberrationB: 0
> SavedSettingsParametersVignetteAmount: 0
> SavedSettingsParametersShadowTint: 0
> SavedSettingsParametersRedHue: 0
> SavedSettingsParametersRedSaturation: 0
> SavedSettingsParametersGreenHue: 0
> SavedSettingsParametersGreenSaturation: 0
> SavedSettingsParametersBlueHue: 0
> SavedSettingsParametersBlueSaturation: 0
> SavedSettingsParametersFillLight: 0
> SavedSettingsParametersVibrance: 0
> SavedSettingsParametersHighlightRecovery: 0
> SavedSettingsParametersClarity: 0
> SavedSettingsParametersDefringe: 0
> SavedSettingsParametersHueAdjustmentRed: 0
> SavedSettingsParametersHueAdjustmentOrange: 0
> SavedSettingsParametersHueAdjustmentYellow: 0
> SavedSettingsParametersHueAdjustmentGreen: 0
> SavedSettingsParametersHueAdjustmentAqua: 0
> SavedSettingsParametersHueAdjustmentBlue: 0
> SavedSettingsParametersHueAdjustmentPurple: 0
> SavedSettingsParametersHueAdjustmentMagenta: 0
> SavedSettingsParametersSaturationAdjustmentRed: 0
> SavedSettingsParametersSaturationAdjustmentOrange: 0
> SavedSettingsParametersSaturationAdjustmentYellow: 0
> SavedSettingsParametersSaturationAdjustmentGreen: 0
> SavedSettingsParametersSaturationAdjustmentAqua: 0
> SavedSettingsParametersSaturationAdjustmentBlue: 0
> SavedSettingsParametersSaturationAdjustmentPurple: 0
> SavedSettingsParametersSaturationAdjustmentMagenta: 0
> SavedSettingsParametersLuminanceAdjustmentRed: 0
> SavedSettingsParametersLuminanceAdjustmentOrange: 0
> SavedSettingsParametersLuminanceAdjustmentYellow: 0
> SavedSettingsParametersLuminanceAdjustmentGreen: 0
> SavedSettingsParametersLuminanceAdjustmentAqua: 0
> SavedSettingsParametersLuminanceAdjustmentBlue: 0
> SavedSettingsParametersLuminanceAdjustmentPurple: 0
> SavedSettingsParametersLuminanceAdjustmentMagenta: 0
> SavedSettingsParametersSplitToningShadowHue: 0
> SavedSettingsParametersSplitToningShadowSaturation: 0
> SavedSettingsParametersSplitToningHighlightHue: 0
> SavedSettingsParametersSplitToningHighlightSaturation: 0
> SavedSettingsParametersSplitToningBalance: 0
> SavedSettingsParametersParametricShadows: 0
> SavedSettingsParametersParametricDarks: 0
> SavedSettingsParametersParametricLights: 0
> SavedSettingsParametersParametricHighlights: 0
> SavedSettingsParametersParametricShadowSplit: 25
> SavedSettingsParametersParametricMidtoneSplit: 50
> SavedSettingsParametersParametricHighlightSplit: 75
> SavedSettingsParametersSharpenRadius: +1.0
> SavedSettingsParametersSharpenDetail: 25
> SavedSettingsParametersSharpenEdgeMasking: 0
> SavedSettingsParametersPostCropVignetteAmount: 0
> SavedSettingsParametersGrainAmount: 0
> SavedSettingsParametersLensProfileEnable: 0
> SavedSettingsParametersLensManualDistortionAmount: 0
> SavedSettingsParametersPerspectiveVertical: 0
> SavedSettingsParametersPerspectiveHorizontal: 0
> SavedSettingsParametersPerspectiveRotate: 0.0
> SavedSettingsParametersPerspectiveScale: 100
> SavedSettingsParametersConvertToGrayscale: False
> SavedSettingsParametersToneCurveName: Linear
> SavedSettingsParametersCameraProfile: Embedded
> SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
> SavedSettingsParametersLensProfileSetup: LensDefaults
> SavedSettingsParametersToneCurve: 0, 0, 255, 255
> IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
228,230d315
< SubSecCreateDate: 2009:11:27 21:32:54.00
< SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
< SubSecModifyDate: 2009:11:27 21:32:54.00
http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

clvrmnky wrote:
davidpope007 wrote:
Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
Yuck. As a former software engineer, this is very bad software engineering.
It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
[Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
* Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
* However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
* Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
* Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
* A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
* So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
* Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
Here's a screenshot from Finder of what I see everytime I look at this folder:
* So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
* What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
* Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
I am really at a loss as to what to do and would welcome your suggestions.
Thanks again and kind regards,
-- David

File Bundle - File Version Changes

Similar Messages

Maybe you are looking for