Metadata Incosistency Warning

Hi,
I am getting the following inconsistency warning which is generating a sql error when Answers attempts to run queries:
"[39008] Logical Dimension table <<Logical Table>> has a source <<Physical Table>> that does not join to any fact source"
This warning appeared after I had re-imported the Physical Table to pick up a new field.
In my Phyical Diagram I am connecting my one Phycial Table to 4 tables that are coming from Excel Spreadsheet.
The tables are connected using Foreign Key relationship.
I have deleted the joins and re-joined the the tables but am still recieving the warning above.
Can anybody recommend as to what should be my next step?
Thanks!

Having verified that all three of these conditions are satisfied and still having the 39008 error, I found one more condition that has to be met.
4. The logical level key in the dimension is a key in the logical table.
For example, if your have a logical table
Models
dim_model_key
model
And you have a Dimension with two levels:
All Models
Model Key
Then the field that you use as the logical level key in the dimension must also be declared as key in the logical table.

Similar Messages

How do we find out what the conflicts are when the metadata conflict warning appears?

How do we find out what the conflicts are when the metadata conflict warning appears?

LR doesn't provide any way to do that. If you are really curious, you could use the free Exiftool to capture the metadata in the file before and after you do Metadata > Save Metadata To File, and then compare the before and after.
Also note that many people have reported spurious notifications that a file's metadata has changed.

Please fix the Metadata consistenct warning...

Hello Gurus,
I have come across the scenario where i have to add the Dummy Fact and dummy column for data densification between Fact and Dimension to see all possible result on answer set.
so I have created the Dummy Fact with Dummy column and done the Cartesian join between all dim with that Dummy fact with 1=1 in physical layer.
now in BMM I imported the Dummy fact and done same joins that I have with the other fact.
now when i create the criteria with dummy fact and orginal fact i m getting the consistency check error on report.
can some suggest me what to do in such case??
Thanking You....

Hey Veeravalli,
Dummy Fact is just created in physical layer with "select 1 as dummy from dual"....
and even the RPD is not showing any warning , error or best practise in consistancy check.
it's only when i pull the Dummy Column from Dummy Fact and any Fact column from regular fact , the error msg is showing in result.
Let me know if you need any further details..

Please fix the metadata consistency warning..

Hello Gurus,
I have come across the scenario where i have to add the Dummy Fact and dummy column for data densification between Fact and Dimension to see all possible result on answer set.
so I have created the Dummy Fact with Dummy column and done the Cartesian join between all dim with that Dummy fact with 1=1 in physical layer.
now in BMM I imported the Dummy fact and done same joins that I have with the other fact.
now when i create the criteria with dummy fact and orginal fact i m getting the consistency check error on report.
can some suggest me what to do in such case??
Thanking You....

Hey Veeravalli,
Dummy Fact is just created in physical layer with "select 1 as dummy from dual"....
and even the RPD is not showing any warning , error or best practise in consistancy check.
it's only when i pull the Dummy Column from Dummy Fact and any Fact column from regular fact , the error msg is showing in result.
Let me know if you need any further details..

Do LR4's random metadata warnings mean something serious?

(LR4.1 on a 2011 iMac with 16GB RAM, running OS 10.7.4)
I am doing my first big job in LR4, and am worried by the way that metadata conflict warning flags (of two types: 'Error writing metadata' and 'Metadata was changed externally') are appearing and reappearing randomly on my image thumbnails. There is absolutely no consistency in which images are affected. I imagine the problem may be caused initially because I used to apply a couple of presets on import - a copyright line, and also camera-specific Develop settings. These were created in Lightroom 2: most of the 14,000 images in my Lightroom catalogue predate my upgrade to LR3 in October (I went to LR4 at the end of April, and 4.1 a week ago; I didn't notice this problem in LR3, but I didn't do much work in that version of the program, so it may have been present and I just didn't notice).
As I say, not all images are affected; but those that are have nothing particular in common. (Whereas most of my photographs will have had the presets applied on import, or else later - when I came up with the new camera-specific defaults, I also applied them retrospectively to all images I hadn't yet processed individually.)
My frustration is not just that this problem exists in the first place: if it is caused by the import presets, I've deleted the develop one (and triple-checked that nothing other than Lightroom's own processing defaults is being applied), and recreated the copyright one, throwing the original away. However, when I try to clear the flags, by clicking on them and OK'ing the dialog box, or doing command-S and OK'ing that way, they sprout up again either immediately or soon after; sometimes on the same images as before, sometimes on other ones.
I've got 'automatically save to XMP' checked as a preference (have had for years, so all my images have XMP files beside them). Although Lightroom imagines the images have also been edited in another program, the vast majority are NEF raw files, and I don't use any other image viewing or editing programs. (There are also a few Photoshop files that may or may not have flags.)
How I've tried to solve it:
1. Doing lots of saves - either selecting all the images in a folder or collection and doing a manual save or clicking the flag and OK'ing the dialog box; or selecting only the images affected and doing the same; or going through one by one, ditto. But whatever I do, more flags sprout on the same or other images in the folder (although sometimes after several saves, they seem to vanish for good).
2. Throwing LR's preferences away. Since this made no difference, I retrieved and reinstated them.
3. Deleting all user presets in Develop, plus the copyright one for Import. (I do have Print and FTP presets, which I hope I don't have to throw away as well. I'm not using those modules at the moment, though.)
4. Realized there was no point on optimizing the catalogue, since that happens automatically, alongside checking its integrity and backing it up, every time I quite Lightroom - which I do after every work session, to ensure I'm fully backed up.
5. At some point in all this, I also restarted my Mac (after I'd deleted the preferences, I think).
6. I have excluded the LR catalog from my Time Machine back-ups, although there was an interruption to this for a few days this week, after I upgraded to LR4.1 (and now I'm worrying that in fact this might date back to my upgrade to LR4 in April). But presumably the catalog isn't corrupt, or I'd get a warning during the regular checks on its integrity?
What's really worrying me, is that this weird behaviour means that there's some instability in Lightroom that'll mean the work I've done on my images is compromised in some way, and I'll lose it.
How can I get rid of these random (incorrect) warnings permanently?
(I did post on this last week, but didn't realize how pervasive and peristent the problem was. I rang Adobe for support on 7 June and got cut off twice; they haven't responded to the case they opened when I was cut off the second time. I tried phoning them three times this morning, and couldn't get through - I was cut off again, twice; the other time I just got dead air. Their phone system seems to be completely up the creek. When I did manage to speak to someone, the sound kept going - which the techie seemed oblivious to, no matter that I kept telling him I couldn't hear him.
I'm really worried that the intensive work I'm doing in Lightroom at the moment will all go to waste, so I'm holding back when I really need to take advantage of the few days I have free right now to do the work.)

Thanks, everyone, for your suggestions.
John: I back up the catalogue (and optimize/check its integrity) every time I quit Lightroom - which is why excluding it from Time Machine isn't the end of the world. I did rename the catalogue early on in my troubleshooting process - as you say, I didn't like the fact I felt out of control of it.
I tried synchronizing a folder that had some flags: when I'd done there were three flags in the folder. (I have unclicked - and clicked and then unclicked - the 'unsaved metadata' checkbox in View Options: as I say, Lightroom shouldn't be displaying these flags at all.)
Rob: Thanks for understanding why I'm fretting! I've checked my XMP sidecars, as you suggest, and they have read and write privileges. I then checked the last-modified date on the XMPs that came up with flags after I'd synchronized that folder. One of them displayed the time I'd just synchronized the folder (it's one I haven't worked on apart from applying a blanket preset in LR2, and then a blanket update to PV2012 in LR4, as I've done to all the images I haven't yet worked on individually); the other two showed the time (I presume) I worked on them yesterday. I selected these three and applied command-S: they then showed, correctly, that they'd been modified a minute before. So far, that folder's now flag-free. (As I said in my original post, the flags sometimes do seem to vanish if I save enough times - and they're unpredictable, not necessarily appearing on the same images in a collection or folder as before I do I group save/clear conflict.)
Mollysnoot: I don't see how the Mac OS would be doing this (although who knows - I'm not a software expert). I don't have any other programs open that can modify images. And since these flags can reappear instantly when I've dealt with the conflict - before I've had time to take a breath, even - I don't think they represent any actual modifications.

LR 4 versus PS CS6 Metadata Question

I am new but am starting to use LR 4 and PS CS6 for about 25,000 images of golf course holes. I have added keywords, GPS coordinates, copyright data, etc to these images as well as collections for picks, star ratings, color ratings, etc.
In the workflow I have started using, I first take a selected image from LR and go to PS to use the lasso tool and content aware fill, healing tool or clone stamp to remove unwanted "distractions" in the images such as golf carts, extraneous people, cart paths, etc. I save these changes to the ORIGINAL image file. (I do this before I do anything else to the image in the develop module of LR or in PS. I need to know that I can "clean up" the image before I do other processing)
When I return to LR from PS after using these tools, I get a message that states "The metadata of this photo has been changes by both Lightroom and another application. Should Lightroom import settings from disk or overwrite disk ssettings from the catalog?"
Which option should I select? I have no idea what changes I have made to the metadata by eliminating a golf cart in an image using PS.
Thanks,
Mel

Saving metadata to file is not really a safeguard against catalog mishap since not all data is saved to file. For instance Virtual Copies, Collections, and Stacking are saved to the catalog only and are not saved to file.
The reason is (probably) that saving metadata to file makes it possible to display the Lr edits in Adobe Bridge - Bridge reads the metadata from file. But since Bridge doesn't have the features for VCs, Stacking, Collections these are not saved to file in Lr.
The best "insurance" against catalog mishap is to create backups regularly. I have set Lr to create backups on every exit (in >Edit >Catalog Settings >General tab) - I can always skip if I think it's not necessary. The advantage of having Lr do the catalog backup is that optimization of catalog and of the previews is part of the backup procedure.
Also, it ensures that Lr can read the backup.
To save metadata to file for all images, select <All Photographs> in the Grid View / Catalog Panel (above the Folders panel). Make sure that all of your external drives that contain photos are plugged in. Then go Ctrl / Cmd + A to select all photos. Then do Ctrl / Cmd + S to save metadata to file. Expect that it may take quite a while for all 250000 images. Alternatively you can do >Metadata >Save metadata to file
You can check the box <Automatically write changes to XMP> in Catalog Settings / Metadata tab. But this causes an old Lr bug to constantly send you the "metadata conflict" warning, and it may drive you nuts.
I therefore save to file manually. Whenever I have edited a bunch of images, I select them all in Grid View and do a Ctrl / Cmd + S.

Why aren't album keyword tags written to metadata using Write Keyword Tag... command

When I display file properties within organizer it shows albums as keyword tags but after using the "Write Keyword Tag and Properties Info to File" command, the album keywords do not make it to the metadata.
Why is this? I would really like for it to work.
I am using PSE version 8. Does it change in version 9?
Thank you!

Ken,
Thanks for your reply.
I think the way that Adobe has implemented albums is a little more like keywords than a saved search. The reason I say this is because of the following:
1. They appear with the keyword tags to the bottom right of the photo in the organizer.
2. When you right-click on a photo and choose "Show Properties", they are listed with the other keywords.
3. If you try to create a keyword with the same name as an album (to get the album name written to the metadata), PSE warns you that you already have a keyword with the same name.
I see what you are saying but I think the Adobe should either make a clear distinction between albums and keywords or at least give you an option to write the album keywords to the metadata if you choose.
Do you know how to submit product enhancement requests?
Thanks again for your time.
Patrick

Lightroom is generating metadata warnings - what's going on?

I've just upgraded to LR4.1 on a Mac running OS10.7.4 (27in iMac with 16Gb RAM). I think this problem probably started when I installed LR4 a while back, but it's only now I've started to process hundreds of images and therefore realized how widespread and persistent it is. Many of my photos have a metadata conflict warning flag, which leads to the message, 'The metadata for this photo has been changed by both Lightroom and another applicaiton. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?' I've been OK'ing the default 'Overwrite settings' option; but whereas I thought this was a byproduct of updating to Process Version 2012, I've just gone to the Library/Photo menu and set a virtual copy of a photo as the master, only to find the same flag and warning instantly appeared.
I was using LR2 until I bought the iMac last October, and nearly all the images in my catalogue predate that (there are nearly 14,000). The only similar query I could find here received the answer, 'select all the images in your catalogue and do command-S' - presumably to save the metadata to each image. But I've always had 'automatically write changes into XMP' checked in Catalogue Preferences; and I quit Lightroom so that it backs up the catalogue at the end of each session.
What's worrying me is that this behaviour isn't logical: I haven't used any other programs to even view, let alone work on these images. Is this a sign of something really worrying like a corrupt catalogue? And what should I do about it?
I'm now finding that on images I've got rid of the warning from - e.g. a couple I've just worked on in Develop - that the warning regenerates itself a few moments later. Weirder and weirder.

I don't think you have to worry too much about this.
The "metadata conflict" warning is an indication that Lr "perceives" a discrepancy between the data in its catalog and the data in the image file (or in the xmp-file). The conflict message is NOT an indication that your catalog is corrupt.
As you probably know "Saving metadata to file" (either automatically as you do or manually via Ctrl + S) writes the Lr data into (the header of) the image file (for JPGs, TIFFs, PSDs) or into a xmp-file (for Raw files). This "saving metadata to file" is in addition and separate of the saving of all data in the catalog.
Lr always uses the data from the catalog - unless go make it read the data from file (via Metadata / Photo >Read Metadata from file).
I assume that your change to a new computer makes Lr "believe" that the image data written to file under your old system is different than what is in the catalog.
You can do the following test: When you get the "metadata conflict" message for a certain image press Ctrl / Cmd + "S" to save the metadata to file. After a few moments the conflict message should disappear, and in the Library Module, in the Metadata panel under Metadata status it should say "Up to date".
You say that you have <'automatically write changes into XMP'> checked. It should only be a matter of time until Lr has written the metadata to file for all your images to file; Lr does this in the background but it takes a while.
Alternatively you could uncheck <'automatically write changes into XMP'>. Since you don't use any other program to work on your images saving metadata to file is not necessary for you.
This would not make the conflict message disappear but it would disappear if you saved the metadata manually (Cmd + S).

Is Photoshop Elements 11 compatible with Windows 8.1?

Is Photoshop Elements 11 compatible with Windows 8.1? I got a new computer 2 months ago and have been loading in my photos and pngs slowly and tagging all of them. If I understand correctly, even though I am saving the tagging to the metadata, Elements warns me that it will not save to pngs, which is what most of mine are. As I have added about half now (about 100 hours of tagging) my computer is freezing up and will no longer open my Elements. My computer completely froze and needed tech support for several hours to get anything to work again. The tech support couldn't find any malware to explain this problem and have concluded that the Elements is not compatible with my operating system. I have not been really pleased with this computer from the start and am not totally convinced that Elements is the cause of the initial lock up of my computer. I am willing to purchase a newer version of Elements if that is the problem, but am worried I will get a newer Elements, go through the loading and tagging process and have the same thing happen again, especially if I have to retag everything I just did. I cannot find anywhere that specifically states whether Elements 11 is compatible with Windows 8.1 (only windows 8). Before I go to a lot of trouble, does anyone know for sure whether Elements 11 is compatible with Windows 8.1? Thanks,Donna

PSE11 will run as a 32-bit application in W8.1-64, PRE11 will run as a 64-bit application.
Cheers,
Neale
Insanity is hereditary, you get it from your children
If this post or another user's post resolves the original issue, please mark the posts as correct accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks.

Customizing rulset of flexPMD 1.2

Hi,
I am totally new to FlexPMD and iam happy that i got succeeded in executing FlexPMD commandline tool version 1.2 for my flex project and take care of the warnings.
I just wanted to customize or add some extra rules in addition to the existing ruleset available with version 1.2
I read the instructions given in http://opensource.adobe.com/wiki/display/flexpmd/Get+Source+Code to download the source code and followed as per mentioned.
I got the entire source code (including branch, trunk,..etc)..As I mentioned before since i wanted to customize the rule available with version 1.2, i thought i need to edit the project flex-pmd-ruleset of 1.2 which is found inside "trunk" folder.
Before doing that, Iam supposed to make the environment ready as mentioned in http://opensource.adobe.com/wiki/display/flexpmd/Developer+Documentation.
while i tried to execute the mvn package command into flex-pmd-parent folder, i did not have internet access to my machine..
is the command internally access any resource from net in order to build the project?
i got the following error msg after a long list of warnings......
[INFO] ------------------------------------------------------------------------
[INFO] Building Adobe Flex PMD Java Parent 1.2
[INFO] ------------------------------------------------------------------------
Downloading: http://repository.codehaus.org/org/apache/maven/plugins/maven-compi
ler-plugin/maven-metadata.xml
Downloading: http://mc-repo.googlecode.com/svn/maven2/releases/org/apache/maven/
plugins/maven-compiler-plugin/maven-metadata.xml
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compil
er-plugin/maven-metadata.xml
[WARNING] Could not transfer metadata org.apache.maven.plugins:maven-compiler-pl
ugin/maven-metadata.xml from dist.codehaus.org (http://dist.codehaus.org): No co
nnector available to access repository dist.codehaus.org (http://dist.codehaus.o
rg) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.apache.maven.plugins:maven-compiler-pl
ugin/maven-metadata.xml from repository.codehaus.org (http://repository.codehaus
.org): Error transferring file: repository.codehaus.org
[WARNING] Could not transfer metadata org.apache.maven.plugins:maven-compiler-pl
ugin/maven-metadata.xml from mc-release (http://mc-repo.googlecode.com/svn/maven
2/releases): Error transferring file: mc-repo.googlecode.com
[WARNING] Could not transfer metadata org.apache.maven.plugins:maven-compiler-pl
ugin/maven-metadata.xml from central (http://repo1.maven.org/maven2): Error tran
sferring file: repo1.maven.org
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Adobe Flex PMD Java Parent ........................ FAILURE [5.375s]
[INFO] As3 Parser API .................................... SKIPPED
[INFO] As3 Maven plugin Utils ............................ SKIPPED
[INFO] Adobe Flex PMD RuleSet test resources ............. SKIPPED
[INFO] Adobe Flex PMD Files .............................. SKIPPED
[INFO] As3 Parser ........................................ SKIPPED
[INFO] Adobe Flex PMD RuleSet API ........................ SKIPPED
[INFO] Adobe Flex PMD RuleSet ............................ SKIPPED
[INFO] Adobe Flex CPD (Copy and Past Detector) ........... SKIPPED
[INFO] Adobe Flex CPD Ant task ........................... SKIPPED
[INFO] Adobe Flex PMD Core ............................... SKIPPED
[INFO] Adobe Flex CPD Maven plugin ....................... SKIPPED
[INFO] Adobe Flex PMD Command line API ................... SKIPPED
[INFO] Adobe Flex CPD Command line ....................... SKIPPED
[INFO] Adobe Flex PMD Ant task ........................... SKIPPED
[INFO] Adobe Flex PMD Maven plugin ....................... SKIPPED
[INFO] Adobe Flex PMD Command line ....................... SKIPPED
[INFO] Adobe Flex Metrics ................................ SKIPPED
[INFO] Adobe Flex Metrics command line ................... SKIPPED
[INFO] Adobe Flex Metrics Ant task ....................... SKIPPED
[INFO] Adobe Flex Metrics Maven plugin ................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.985s
[INFO] Finished at: Wed Nov 24 18:07:50 IST 2010
[INFO] Final Memory: 3M/6M
[INFO] ------------------------------------------------------------------------
[ERROR] Error resolving version for plugin 'org.apache.maven.plugins:maven-compi
ler-plugin' from the repositories [local (C:\Documents and Settings\pcuser\.m2\r
epository), dist.codehaus.org (http://dist.codehaus.org), repository.codehaus.or
g (http://repository.codehaus.org), mc-release (http://mc-repo.googlecode.com/sv
n/maven2/releases), central (http://repo1.maven.org/maven2)]: Plugin not found i
n any plugin repository -> [Help 1]
I even tried the same mvn package command for flex-pmd-parent for version 1.1 inside trunk for which i got the following error....
[ERROR] The build could not read 26 projects -> [Help 1]
[ERROR]
[ERROR]   The project com.adobe.ac:as3-parser:1.1 (F:\FlexPMD Source code\tags\1
.1\as3-parser\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact com.adobe.ac:
flex-pmd:pom:1.1 from central (http://repo1.maven.org/maven2): Error transferrin
g file: repo1.maven.org and 'parent.relativePath' points at wrong local POM @ li
ne 8, column 11: Unknown host repo1.maven.org -> [Help 2]
[ERROR]
[ERROR]   The project com.adobe.ac:as3-parser-api:1.1 (F:\FlexPMD Source code\ta
gs\1.1\as3-parser-api\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact com.adobe.ac:
flex-pmd:pom:1.1 from central (http://repo1.maven.org/maven2): Error transferrin
g file: repo1.maven.org and 'parent.relativePath' points at wrong local POM @ li
ne 7, column 11: Unknown host repo1.maven.org -> [Help 2]
i also tried opening the project files in eclipse galileo without executing mvn package command ...i noticed many errors in import statements where the actual package referred does not even exist in the code...pls refer the attached image..is the source code downloaded is unstable...
where am i going wrong...pls help me with a detailed procedure to set the environment so that i can customize the ruleset...

The documentation has not been updated since early days of planning, I am not even sure if it is still valid as in my experience it is hardly ever used.
If you are version 11.1.2 then I would assume it would be the file in the planning product installation directory.
Cheers
John
http://john-goodwin.blogspot.com/

Invoking PageTemplate Bug?

Hi folks,
I'm using jdev 11.1.2.4.0 by with that i h've been created fusion web app. it comprise of model-viewcontroller projects. In VC i h've been created a custom pagetemplate.jsf then i try to invoke that in all my .jsf.
it's fine.
but i'm trying to do that same in jdev11.1.1.6.0. in this case i created my custom pagetemplate.jspx then i try to invoke that in all my .jspx. it's throwing some feedback window is appearing each and every time. so i can't achieve this. Is this Bug in this specific version? or else i'm doing mistake.
i got a message like this in jdev11.1.1.6.0.
SEVERE: Error calling postJSPCreationHook for oracle.adfdtinternal.view.rich.addin.plugin.ADFFacesJsfWizardExtension
java.lang.NoSuchMethodError: oracle.adfdt.view.rich.template.PageTemplateInfo.configureProject(Loracle/ide/model/Project;)V
at oracle.adfdt.view.rich.template.TemplateDTUtils.applyPageTemplate(TemplateDTUtils.java:301)
at oracle.adfdtinternal.view.rich.pagelayout.quickstart.PageTemplateFlowLayout.configure(PageTemplateFlowLayout.java:60)
at oracle.adfdtinternal.view.rich.addin.plugin.ADFFacesJsfWizardExtension.postNodeCreationHook(ADFFacesJsfWizardExtension.java:251)
at oracle.adfdtinternal.view.rich.addin.plugin.ADFFacesJsfWizardExtension.postJSPCreationHook(ADFFacesJsfWizardExtension.java:150)
at oracle.jdevimpl.webapp.jsp.AbstractJspFileBuilderModel.postProcessNode(AbstractJspFileBuilderModel.java:95)
at oracle.jdevimpl.webapp.jsp.taglibraries.jsf.JsfJspFusionWizard$JsfJspFileBuilderModel.postProcessNode(JsfJspFusionWizard.java:465)
at oracle.jdevimpl.webapp.wizards.AbstractWebAppFileBuilderModel.postProcess(AbstractWebAppFileBuilderModel.java:121)
at oracle.jdeveloper.builder.AbstractBuilderModel.addFileToProject(AbstractBuilderModel.java:278)
at oracle.jdeveloper.builder.AbstractBuilderModel.commitWizardState(AbstractBuilderModel.java:225)
at oracle.jdevimpl.webapp.fusion.wizards.AbstractWebAppFileWizard$4.run(AbstractWebAppFileWizard.java:192)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:642)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:603)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:612)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
at java.awt.Dialog$1.run(Dialog.java:1046)
at java.awt.Dialog$3.run(Dialog.java:1098)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Dialog.java:1096)
at java.awt.Component.show(Component.java:1585)
at java.awt.Component.setVisible(Component.java:1537)
at java.awt.Window.setVisible(Window.java:842)
at java.awt.Dialog.setVisible(Dialog.java:986)
at oracle.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:395)
at oracle.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:356)
at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:352)
at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:243)
at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:215)
at oracle.jdevimpl.webapp.fusion.wizards.AbstractWebAppFileWizard.doFinish(AbstractWebAppFileWizard.java:93)
at oracle.jdevimpl.webapp.fusion.wizards.AbstractWebAppWizard.invoke(AbstractWebAppWizard.java:151)
at oracle.ide.wizard.WizardManager.invokeWizard(WizardManager.java:372)
at oracle.ide.wizard.WizardManager$1.run(WizardManager.java:420)
at oracle.ide.util.IdeUtil$3.run(IdeUtil.java:1089)
at oracle.javatools.util.SwingUtils.invokeAfterRepaint(SwingUtils.java:509)
at oracle.ide.util.IdeUtil.invokeAfterRepaint(IdeUtil.java:1102)
at oracle.ide.wizard.WizardManager$2.run(WizardManager.java:428)
at oracle.ide.util.IdeUtil$3.run(IdeUtil.java:1089)
at oracle.javatools.util.SwingUtils.invokeAfterRepaint(SwingUtils.java:509)
at oracle.ide.util.IdeUtil.invokeAfterRepaint(IdeUtil.java:1102)
at oracle.ide.wizard.WizardManager.invokeSecondaryWizard(WizardManager.java:424)
at oracle.ide.gallery.ObjectGallery.invokeWizard(ObjectGallery.java:383)
at oracle.ide.gallery.ObjectGallery.runDialog(ObjectGallery.java:204)
at oracle.ide.gallery.ObjectGallery.runDialog(ObjectGallery.java:124)
at oracle.ide.gallery.ObjectGalleryAddin._invokeGallery(ObjectGalleryAddin.java:405)
at oracle.ide.gallery.ObjectGalleryAddin.handleEvent(ObjectGalleryAddin.java:208)
at oracle.ide.controller.IdeAction.performAction(IdeAction.java:529)
at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:897)
at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:501)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
at java.awt.Component.processMouseEvent(Component.java:6289)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6054)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4652)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4482)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4482)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:603)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:617)
at java.awt.EventQueue$2.run(EventQueue.java:615)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Nov 1, 2013 3:31:07 AM com.oracle.webapp
SEVERE: Error calling postJSPCreationHook for oracle.adfdtinternal.view.rich.addin.plugin.ADFFacesJsfWizardExtension
java.lang.NoSuchMethodError: oracle.adfdt.view.rich.template.PageTemplateInfo.configureProject(Loracle/ide/model/Project;)V
at oracle.adfdt.view.rich.template.TemplateDTUtils.applyPageTemplate(TemplateDTUtils.java:301)
at oracle.adfdtinternal.view.rich.pagelayout.quickstart.PageTemplateFlowLayout.configure(PageTemplateFlowLayout.java:60)
at oracle.adfdtinternal.view.rich.addin.plugin.ADFFacesJsfWizardExtension.postNodeCreationHook(ADFFacesJsfWizardExtension.java:251)
at oracle.adfdtinternal.view.rich.addin.plugin.ADFFacesJsfWizardExtension.postJSPCreationHook(ADFFacesJsfWizardExtension.java:150)
at oracle.jdevimpl.webapp.jsp.AbstractJspFileBuilderModel.postProcessNode(AbstractJspFileBuilderModel.java:95)
at oracle.jdevimpl.webapp.jsp.taglibraries.jsf.JsfJspFusionWizard$JsfJspFileBuilderModel.postProcessNode(JsfJspFusionWizard.java:465)
at oracle.jdevimpl.webapp.wizards.AbstractWebAppFileBuilderModel.postProcess(AbstractWebAppFileBuilderModel.java:121)
at oracle.jdeveloper.builder.AbstractBuilderModel.addFileToProject(AbstractBuilderModel.java:278)
at oracle.jdeveloper.builder.AbstractBuilderModel.commitWizardState(AbstractBuilderModel.java:225)
at oracle.jdevimpl.webapp.fusion.wizards.AbstractWebAppFileWizard$4.run(AbstractWebAppFileWizard.java:192)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:642)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:603)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:612)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
at java.awt.Dialog$1.run(Dialog.java:1046)
at java.awt.Dialog$3.run(Dialog.java:1098)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Dialog.java:1096)
at java.awt.Component.show(Component.java:1585)
at java.awt.Component.setVisible(Component.java:1537)
at java.awt.Window.setVisible(Window.java:842)
at java.awt.Dialog.setVisible(Dialog.java:986)
at oracle.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:395)
at oracle.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:356)
at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:352)
at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:243)
at oracle.ide.dialogs.ProgressBar.start(ProgressBar.java:215)
at oracle.jdevimpl.webapp.fusion.wizards.AbstractWebAppFileWizard.doFinish(AbstractWebAppFileWizard.java:93)
at oracle.jdevimpl.webapp.fusion.wizards.AbstractWebAppWizard.invoke(AbstractWebAppWizard.java:151)
at oracle.ide.wizard.WizardManager.invokeWizard(WizardManager.java:372)
at oracle.ide.wizard.WizardManager$1.run(WizardManager.java:420)
at oracle.ide.util.IdeUtil$3.run(IdeUtil.java:1089)
at oracle.javatools.util.SwingUtils.invokeAfterRepaint(SwingUtils.java:509)
at oracle.ide.util.IdeUtil.invokeAfterRepaint(IdeUtil.java:1102)
at oracle.ide.wizard.WizardManager$2.run(WizardManager.java:428)
at oracle.ide.util.IdeUtil$3.run(IdeUtil.java:1089)
at oracle.javatools.util.SwingUtils.invokeAfterRepaint(SwingUtils.java:509)
at oracle.ide.util.IdeUtil.invokeAfterRepaint(IdeUtil.java:1102)
at oracle.ide.wizard.WizardManager.invokeSecondaryWizard(WizardManager.java:424)
at oracle.ide.gallery.ObjectGallery.invokeWizard(ObjectGallery.java:383)
at oracle.ide.gallery.ObjectGallery.runDialog(ObjectGallery.java:204)
at oracle.ide.gallery.ObjectGallery.runDialog(ObjectGallery.java:124)
at oracle.ide.gallery.ObjectGalleryAddin._invokeGallery(ObjectGalleryAddin.java:405)
at oracle.ide.gallery.ObjectGalleryAddin.handleEvent(ObjectGalleryAddin.java:208)
at oracle.ide.controller.IdeAction.performAction(IdeAction.java:529)
at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:897)
at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:501)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
at java.awt.Component.processMouseEvent(Component.java:6289)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6054)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4652)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4482)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4482)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:603)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:617)
at java.awt.EventQueue$2.run(EventQueue.java:615)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Nov 1, 2013 3:31:07 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key GRID_CELL
Nov 1, 2013 3:31:07 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key CODE_EDITOR
Nov 1, 2013 3:31:07 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods getShortDescription
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key PANEL_GRID_LAYOUT
Nov 1, 2013 3:31:07 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key GRID_ROW
Nov 1, 2013 3:31:07 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key LIST_VIEW
Nov 1, 2013 3:31:07 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key LIST_ITEM
Nov 1, 2013 3:31:15 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key GRID_CELL
Nov 1, 2013 3:31:15 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key CODE_EDITOR
Nov 1, 2013 3:31:15 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key PANEL_GRID_LAYOUT
Nov 1, 2013 3:31:15 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key GRID_ROW
Nov 1, 2013 3:31:15 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key LIST_VIEW
Nov 1, 2013 3:31:15 AM oracle.adfdtinternal.view.rich.metadata.ADFFacesMetadataMethods
WARNING: Can't find resource for bundle oracle.adfdtinternal.view.rich.resource.AFUTaglibBundle, key LIST_ITEM
I hope this bug?.
if it is bug i h've a question.? one of my collegue project pagetemplate created using jdev11.1.1.6.0 consuming the template in all jspx page it working fine till now.
I tired the same jdev11.1.1.7.0 "unexpected error throwing". even though i ignore the error. In some case pagetemplate is affecting all my pages.some other case it is not..
Thanks.

Hi,
What means "try to invoke that in all my .jspx."
i re-phrase in another words i have pagetemplate. i'm trying to apply the template in my jspx page.
In detail, After creation of template. while i'm trying to creating the jspx page in the Intial Page Layout and content i choose my template radiobox. after hitting ok. the above log prints in message tab.
i hope that i make it more clear.
Page based on that template does not work ?.
yes.

To XMP or not to XMP

I was bitten by the Lightroom 5.0 History bug (images developed in earlier versions of Lr lost complete histories if the history state was changed in the Develop module) and was able to recover because I had good backups. I've updated to 5.2 since, so I don't expect to run into that again. One thing I noticed during my recovery operation is that Lr will warn me if there is a mismatch between metadata in the catalog and metadata in the image file. Overwriting the metadata in the image with the metadata in the recovered catalog fixed the some issues with the effects of the bug, but it got me thinking -- what if the metadata hadn't been written to the image file at all?
I'm more of a video guy than a photo guy, and I set up Lr to automatically write metadata to the files because that's what I do for my video files when I use Premiere Pro. But I think my recovery would have been easier and less stressful if I hadn't had to see or base a decision on the intimidating metadata mismatch warning that Lr presents.
So I'm asking for general opinions -- what do you think about the pros and cons of having Lr automatically write metadata to XMP?
Jeff

Samoreen wrote:
But you will regularly forget Ctrl-S anyway .
Actually, I never forget. Or perhaps I should say if ever I do forget, it will be caught.
There are two times I save metadata:
1. When I've done enough editing I'd be bummed if it got lost, but I'm not finished yet.
2. When I'm finished.
finished means "finished for now" - most photos are published after they're finished, and re-published after they're finished again...
In the former case (1), I just don't worry about it too much, in the latter case (2) it's done as part of a "finalization ritual" which (takes snapshots of and also) assigns metadata to finished photos... I use the ChangeManager plugin for that, but there is more than one way to accomplish a goal. For example, Jeffrey Friedl has Folder Status plugin for "managing change" on a folder basis instead of photo basis. You can also follow a self-designed procedure which does not require plugins.
The concept is: once saving xmp becomes part of a workflow that includes assigning (and/or clearing) metadata, it's the assigned (or cleared) metadata that drives the relationship (status) between catalog settings and xmp on disk.
I turn xmp status indicators off, and rarely look at the metadata status collection(s). Why?
1. They sometimes say metadata needs to be saved when it doesn't.
2. They sometimes say metadata wasn't saved when it was.
3. They may seem to indicate you should read metadata when you shouldn't.
4. Metadata conflict status depends on date/time only, not contents, and so many "conflicts" are simply false alarms.
etc.
i.o.w. it's never been a reliable (nor robust) feature in Lightroom, and I just don't need it, since I have other "metadata status" metadata that I have complete control of, which *is* reliable.
If I ever get confused, ChangeManager's "Compare Catalog to Disk" feature gives a complete list of all differences between develop settings and metadata in catalog and those in xmp on disk.
I don't necessarily recommend everybody do things how I do them, since my way (although robust) employs plugins - it's not "as simple as possible", and there is something to be said for simplicity.
My main point is that if you can figure a way to assure xmp is saved when appropriate, manual method may be best.
If you can't or just don't want to, then auto method may be best for you. And of course there are those that rely on the catalog exclusively and never save xmp - that's another way to go.
UPDATE:
=======
Perhaps the most important aspect to me of saving manually: I want to save (finalized) xmp only after scrutinization, since part of the goal is NOT to save screw-ups in xmp! - they're already in the catalog .
=======
Rob
Message was UPDATED by: Rob Cole

Checksum validation failed for some Xtext Maven artifacts and corresponding problems

Hi
I've been noticing some Checksum validation warnings during the build
for some Xtext Maven artifacts, e.g.,
[INFO] Downloading:
https://repo.maven.apache.org/maven2/org/eclipse/xtext/org.eclipse.xtext.util/maven-metadata.xml
[INFO] Downloading:
https://oss.sonatype.org/content/repositories/snapshots/org/eclipse/xtext/org.eclipse.xtext.util/maven-metadata.xml
[WARNING] Checksum validation failed: Checksum validation failed,
expected 872cc77705d19d8f59e22b784036430356246697 but is
56dfb41a5a16e797f052660debc509bd44d10880 for
https://repo.maven.apache.org/maven2/org/eclipse/xtext/org.eclipse.xtext.util/maven-metadata.xml
[INFO] Downloaded:
https://repo.maven.apache.org/maven2/org/eclipse/xtext/org.eclipse.xtext.util/maven-metadata.xml
(649 B at 3.2 KB/sec)
[INFO] Downloaded:
https://oss.sonatype.org/content/repositories/snapshots/org/eclipse/xtext/org.eclipse.xtext.util/maven-metadata.xml
(380 B at 0.9 KB/sec)
[INFO] Downloading:
https://repo.maven.apache.org/maven2/org/eclipse/xtext/org.eclipse.xtext.util/2.8.3/org.eclipse.xtext.util-2.8.3.pom
[WARNING] Checksum validation failed: Checksum validation failed,
expected 25d651226b11727df3b99a6325e989f4e08c82ee but is
453418e3e74ace9b69e7c34094ee712f81c55991 for
https://repo.maven.apache.org/maven2/org/eclipse/xtext/org.eclipse.xtext.util/2.8.3/org.eclipse.xtext.util-2.8.3.pom
similar for org.eclipse.xtext.dependencies, org.eclipse.xtext.xbase.lib
This hasn't prevented the build from completing so far; but now that I
started to play with some mwe2 custom generator fragments in my DSL,
when running the mwe2 workflow during the build it fails with such
exception, which I guess might be related:
java.lang.SecurityException: class
"org.eclipse.xtext.util.XtextSwitch"'s signer information does not match
signer information of other classes in the same package
can it be related?
thanks in advance
Lorenzo
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

We have the same problem for weeks now. Seems, that there is really a wrong checksum in the maven repo.

Missing sidecar - remove missing file status

I have raw files that had metadata written to XMP sidecar files, the XMP are now missing, and I don't want to have LR create new sidecar files. The files show up as missing in the catalog. How can I get rid of the missing status and the little "metadata status warning" icons without having to write new sidecar files? If I can't that's pretty insidious and I would call it a bug.
Thanks

Writing to xmp and then deleting the xmp is how I got to this stage. They show up in the Missing Files folder in the library tab of the library module. If I hover over the little question mark icon it says sidecar file is missing. If I click on the question mark it writes the metadata to xmp, even if "auto write changes to xmp" is unchecked in the catalog settings>metadata preferences.
But there's no way to delist them from missing files without creating a new xmp, as far as I can tell. You're basically stuck with "missing files" warning forever unless you create new xmps.
It's pretty annoying. I'd call it a bug. Essentially it's probably just a scenario that wasn't considered or accounted for in development. Creating missing file folder on demand - I like that.
Thanks for your input, let me know if you come up with anything

Wrong track length listed

Hi everybody,
So, I'm running iTunes 7.4.2, and several of my longer songs (generally over 10 minutes) have the wrong length listed. For example, I have one that is over 12 minutes long, but is only listed as 9:57.
I tried converting it to MP3 using the convert to MP3 function, but the new track had the same length as the old one.
Is there any way for me to fix this for this song and all the other ones in my library?
Thanks in advance.

thenewdawg wrote:
As of this week, with recently updated iTunes (7.4.2), I'm finding some songs (all mp3's) with a changed bit rate, now 64 bits and some longer songs (8 minutes +) with changed, incorrect times. Is there something going on here beyond an Apple bug fix, something I need to educate myself on to protect my files ?
I'm not sure what's causing these problems, but over the years I've seen plenty of reports of things like this. MP3s created with Audion using the included LAME encoder were notorious for incompatibility with iTunes a few years ago. I think the best thing to do is to keep a "virgin" backup of your music somewhere out of iTunes' or any other player's reach.
Can this, or any iTunes version actually corrupt previously recorded files ?
MP3s are somehow susceptible to corruption and damage, much more so than with other formats of music files. Determining whether any version of iTunes actually causes the damage or corruption is quite a difficult task. Actually, without having a safe backup of MP3s which have never been allowed into contact with iTunes, it's pretty much impossible to prove.
iTunes is my favorite player by a long shot, but the only application I trust with my master archive of FLAC files is foobar2000 (on my PC). I have this whole library backed up on different drives in my Mac in both FLAC and Apple Lossless formats, but the FLAC library will always be the one I rely on and use for transcoding to other formats.
For what it's worth, I don't really consider iTunes an "MP3" player anymore, and I suspect that Apple doesn't either. Nothing in iTunes in the way of MP3 support has changed or been improved in any way for literally years--unless someone has evidence to suggest otherwise. Starting with iTunes 7.x, I suppose the single exception would be that Apple figured out and implemented a way to analyze the gapless playback information stored in LAME-encoded MP3 files.
Finally, it's fair to comment that iTunes does alter audio files when the default settings are used. Adding MP3s to your library with Sound Check enabled, for example, actually alters the tracks' metadata without warning. Supposedly, when you turn Sound Check off, iTunes simply ignores the information it has written to the files, but the files remain altered and this can be easily proven by examing the files in other players such as foobar2000. A good rule to follow is to always be extremely careful when setting up iTunes in order to disable every possible function that has the ability to tamper with files before adding any files to the library.

Metadata Incosistency Warning

Similar Messages

Maybe you are looking for