LR3 to CS5 metadata changing

I start with a DNG in LR3. Take the photo into CS5 using Stack with Original turned on. Make changes and save the file. LR3 tells me the metadata has been changed by another software.
Does anybody know why the metadata is being updated? Do I need to change a setting in LR3 or CS5?
Thanks for any info.

Are you using filtering (e.g. using the number of stars)?
If so the problem is that LR3 is not updating the metadata when the file is passed to PS.
Save the metadata on the original RAW/DNG before triggering the edit in PS and the rating info will show up in the TIF/PSD and you'll see it since it will match your filter.
I had exactly the same problem, only with CS3.
Hope this helps,
Selby

Similar Messages

  • Magenta Printing Issues in LR3 and CS5

    Hi,
       I have seen this issues mentioned in various forms over the last year or so but I have yet to see a real solution to the problem I am now experiencing
    History:
       I was running a Vista 64b OS and using LR 2.X along with Epson's r2880 printer.  I was able to print using LR 2.X without any issues both in B&W and color using the various paper iccs provided by the vendors (Moab for example)  I never had the Magenta printing issues.
    Fast Forward:
       I recently installed LR3 and CS5 under the same OS (Vista 64b) and when I printed in color it is obviously Magenta heavy.   I am following the same practices as before of having LR3 manage the color (using one of the vendor iccs) and setting "No Color Managment" in the printer driver UI.  Doing this gives me terrible crazy Magenta prints.  I have un-installed and re-installed the Epson Printer drivers numerous times with no positive effect.  The causal effect was installing CS5 and LR3. These were the only changes made.
    I was wondering if anyone had a similar problem and had found a solution other than switching over to a Mac.
    This is very frustrating and depressing.
    Thanks,
    David.
    [email protected]

    Thanks for the great Feed back.  I was able to fix the printing problem by doing several things:
    1) Re-install the printer drivers
    2) Runnning the printer through nozzle checks and cleaning cycles. Had to peform the cleaning cycle 3 times.
    3) Replacing the yellow ink cartridge.  The ink level was showing about 15% remaining but in fact I was out of yellow ink. I had read that the ink levels were not always accurate.
    So for me this issue has been solved.  Thanks for the help.
    -D

  • Global Metadata changes in Bridge?

    When CS5 Bridge and adding my metadata changes for my photos, I cant seem to find a way to make these changes globally to several large blocks of photos.  I tried to click on all the photos involved but then it refused to accept any changes.  PLease! tell me there is a way?  I even tried to "saved" the changes so all I had to do was one click on the new photo but that didnt work either.   I'm new to Bridge so please bear with me.  Thanks.

    If what you want to change is description, credits, copyright and other IPTC and other metadata that is shown in File Info, you can use Bridge to change multiple image files at a time.  In Bridge, select the block or blocks of images for which you want to change the metadata. Then right click and and click on File Info... in the right-click popup menu (or instead ofright click, use Control-I or File > File Info...).  This will bring up File Info dialog box.  If what you want to change is in a saved template, you can click on the templates button (at bottom of file Info box between Preferences and OK).  Select and click desired template, which should bring up Import Options popup box. Select one of the three options, depending on how much of existing in-file metadata you want to keep or replace.  Or instead of calling a template, you can make entries directly into desired File Info fields.  Any information you enter in a field overrides existing metadata and applies the new value to all of your selected files.

  • LR3 JPEG/DNG Metadata Confusion

    Hi,
    I'm a little confused about XMP data and the LR3 catalog itself.
    First, I understand that DNG files can have embedded keywords and other metadata -- and 95% of my files are CR2 files that I bring into LR3 as DNGs and keep them as DNGs.  So I am NOT using raw files with sidecar files.
    But where I'm confused is the "automatically write changes into XMP" LR3 catalog option and how it relates to JPEG files.
    I was of the understanding that if I make changes in the develop module (eg. contrast)  to a JPEG file (not a DNG), then these changes will NOT be saved to the original JPEG file, but will be "recorded" in the LR3 catalog.
    But now If I allow LR3 to "automatically write changes into XMP"  -- will this WRITE these develop module changes (e.g. the contrast change)  to the original JPEG?  Or does the "automatically write changes into XMP" only refer to the keywords and other metadata in a JPEG file?
    Thanks for any help in clearing this up,
    R

    So just so I have this correct with JPEGs:
    1, If I make changes in LR3 to a JPEG (e.g. contrast), this contrast change is saved in the LR3 catalog.
    2. I can ADDITIONALLY save metadata (keywords, etc)  in XMP data into a JPEG if I have the "automatically write xmp." settings checked or if I save it manually to the file
    3. I can ADDITIONALLY save the develop settings (e.g. the contrast change I made in #1) by including the develop data in the JPEG in the same dialogue box.
    But now if I opened this keyword, added contrast-adjusted JPEG in another program,  only "XMP-aware" programs would allow me to see these keywords and contrast changes.  Is this a correct assessment?
    And lastly, if I do save the develop settings to the JPEG itself, doesn't that violate the "non-destructive" editing concept of LR3?
    Thanks again!

  • LR3 not writing metadata to xmp

    Preferences set to automatically write changes to xmp file.  LR3 has stopped writing changes to xmp. 
    When I choose a thumbnail and click the "!" in upper right corner + click "Retry Metadata Export", I get this message: "Could not write metadata.  Your disk has less than 1 gigabyte of space left".
    This is correct, as there is 200mb free space on the particular disk, but I would think this would be sufficient.  So question is: how much free disk space do I need for LR3 to continue to automatically write metadata to xmp?

    From the message you have received and the statement made in the requirements for running LR on the Lightroom home page
    minimum1GB of available hard-disk space
    it would seem likely that 1 GB is the minimum. However I would suggest rather a great amount of free hard disk space is required in order for LR to function efficiently. But the minimum is pretty clear.Once you go below this you will experience problems and not just with writing metadata to file, but writing changes to the catalog itself if that is located on a disk with less than the minimum requirements The metadata once written takes up very little space, but the process of writing it can require space on disk for temporary files etc. Just make sure you have lots of spare capacity on any drive you use with LR.

  • Can't open .CR2 files off of a Canon PowerShot S95 (LR3/PS cs5)

    I just bought the new Canon S95.  I download pics off of a reader and usually go directly through LR.  This time, LR would only download the few Jpgs I had on the SD card and showed me "The files are from a camera which is not recognized by the raw format support in Lightroom." 
    It does however show a Canon S95 as part of the info when viewing the jpegs in the library module. 
    I copied the files from the SD card to my hard drive via copy and tried to open the files in Photoshop and got the following error.  "Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw.  Please visit the Camera Raw help documentation for additional information."
    I am running a MacPro with 8 G of ram and the current versions of LR3, Photoshop CS5 and Camera Raw.   I can see the thumbs of these raw files in finder where I placed the copies.  I have downloaded many .CR2 files from a Canon S40, S70, 20D, etc.  I'm lost.
    Thanks to all.
    Peace

    mybrotherbob wrote:
    try using Adobe DNG converter to convert them to a supported format…
    That's silly.     The Adobe DNG Converter and ACR are always released in tandem and the same camera models are supported in each respective version.
    If that camera is not yet supported in any version of ACR, it wll not be supported in any version of the DNG Converter either.
    Wo Tai Lao Le
    我太老了

  • Import from Catalog- Why is metadata changing?

    Whenever I run Import from Catalog (going from portable drive to desktop), the dialog box shows several photos that have been "modified," even though I haven't touched them since they were last imported to the desktop.  I'm guessing, the desktop install of LR is finding metadata changes in some files. In fact, some thumbnails even show the "metadata changed" badges even though I haven't touched them.
    I'm using LR 3 Macintosh, and want to share catalogs between my laptop and desktop using Import from Catalog.  I consider my desktop the "master catalog" and mainly use the laptop for capture or editing when I'm traveling.  The laptop catalog and photos are stored on a portable drive.
    Here's what I did to try to isolate the problem - all of this was executed on my desktop machine so the LR settings should be identical:
    1) Created a new catalog on the portable drive while attached to desktop.
    2) Restart LR with new portable drive catalog active.
    3) "Import to catalog" and import 10,000 photos to portable drive from the desktop catalog. This ran with no problems as expected.
    4)  Restart LR w/ original desktop catalog.
    5)  Run "Import from Catalog" to import form the portable drive. -- NOTE I hadn't touched ANY photos on portable since step 3.
    6)  Import from catalog show 0 "new" photos but about 10 "changed" photos.  Why??  It shouldn't show any.
    7)  Cancel step 6 and run Import from catalog again.  This time it shows 0 new and 0 changed. (that's what I'd expect).
    8) Cancel step 7 and run Import from Catalog again.  This time it shows 0 new and about 30 changed - But they're a different set than in step 6.
    9) Give up and post this question.  What is changing the metadata?
    As background, I'm running most current versions of OS X and LR 3.  My library contains mostly DNG files with some jpg and some TIF and PSD.  The "modified" files that are showing up all seem to be DNG files.  The files in the library were shot with  Canon, G2, G10, 10D, 20D, 60D and 7D.   The "modified" files appear to be from the 20D, 60D and 7D (all files shot in last 6 months).  The library has some virtual copies and stacks, but this doesn't appear associated with the "modified" files.
    Thank you in advance.
    Marshall

    Ian;
    Thank you for your response.  I suspect you may be correct, although I can't trace the problem to explain lens profiles as the issue either at this point.  Each time I try to "Import from Catalog" back and forth between two catalogs - both made from the same instance of LR, it shows a different set of photos with who's metadata is changed.  I make absolutely NO changes to any photos.  I just choose "Import form catalog," look at the list of photos it says are changed, select, 'cancel," and then select "Import form catalog" again.  Each time it gives me a different set of, and total amount of changed photos.  First its 9 photos, then 32 photos, then 447 photos, etc.
    This has "BUG" written all over it.  If it's actually a feature, I wish someone could show me how to control it.
    A lot of people complain about LR's ability to share catalogs between computers and keep multiple catalogs in sync.  If I could master "Import from Catalog," I'd feel I'd have a workable solution for managing multiple computers (with one photographer / editor).
    Just my opinion on this one feature. Overall, I LOVE working with LR.
    Thanks again,
    Marshall
    PS.  Thank you, Ian for the many tips and tutorials you've provided over the past years.  I've learned a lot from them.

  • How to solve illustrator cs6 save as cs5 problem about the stroke(when the stroke with clipping mask and color is gradient, save as cs5 will change to embed ).

    how to solve illustrator cs6 save as cs5 problem about the stroke(when the stroke with clipping mask and color is gradient, save as cs5 will change to embed ).

    Because it was not possible to apply a gradient to a stroke in CS5. When you open the file in CS5, it is reduced to something that can be rendered in CS5.

  • How do I get Bridge and Lightroom to respect - read - metadata changes?

    I cull my wedding images in Bridge (CS 6) and then export them into LR 4.  I typically rate images as I'm culling, but when I import those images into LR, the ratings don't carry over.  Likewise, when I label images in LR and export them, Bridge shows all the color labels as white - regardless of which label was actually assigned. 

    Lr saves all edits and any other metadata changes in its database (= the catalog).
    Additionally to the catalog you can <save to file>,i.e. to a xmp-file (in case of a Raw photo), or in the header (but not in the image pixels!) of a JPG, TIFF, or PSD.
    Saving to file is done by
    _ either checking the box <Automatically save changes to xmp> in >Edit >Catalog Settings >metadata tab, or manually
    _ by going >Metadata >Save metadata to file (in Lr Library Module), or
    _ by going >Photo >Save metadata to file (in Develop Module.
    When you save manually to file you can select multiple photos in the Grid Mode and do <Save metadata to file>.
    This saving to file is necessary in order that Bridge can read and display the Lr edits because Bridge cannot read the Lr catalog.
    Bridge saves to file automatically (there is no option of deselecting it) and Lr will read the metadata from Bridge when you import the image into Lr.
    In case of an image that is already in Lr you have to select >Metadata >Read metadata from file (in Lr Library Module), or 
    by going >Photo >Read metadata from file (in Develop Module). Without this <Read metadata from file>, Lr will not display any changes made in Bridge after the import  into Lr. Since this <read metadata from file> would overwrite any different edits you may have done in Lr, it is best to do this before you do further edits in Lr.
    The rating stars should transfer from Bridge to Lr and vice versa without problems.
    For the color labels to transfer correctly you have to make the textual descriptions for the individual colors identical in Lr and in Bridge - down to upper/lower case, commas, hyphens, underscores, etc.
    Having said this:
    I would recommend that you do not use Bridge for culling your images. You can do the culling just as easy in Lr. When you manage photos in Bridge and in Lr, you will always have the problem of synchronizing the metadata. This can be done but it needs a meticulous workflow that is adhered to strictly.
    There is nothing in Bridge that Lr cannot do *). Make your life easier and choose Lr as your only image management and editing tool, except for CS6 itself (I mean Photoshop itself, not the ACR ).
    *) Well there is one thing: Since Lr is not a browser-based program it does not automatically "see" what is on a hard drive. Photos need to be imported in order that Lr will "see" them.
    Bridge is browser-based. Whatever photo is on a hard drive - irrespective of which program put it there - it will be "seen" by Bridge.
    So Bridge is a valuable tool if a photo is not displayed in Lr and you want to check if it is in a particular folder.

  • Iphone ignoring song metadata changes

    Why are song metadata changes made in iTunes not respected by iPhone, for purchased (via iTunes) content ?
    I have a large classical music collection, and I use composer surname as my primary sort method.  To do this, I blank the composer field for all non-classical music and ensure that for classical music, the composer name is listed by surname first - this means a lot of metadata changes.
    This filing system works very nicely in ITunes on my computers and on my old iPods.
    However, on the iPhone, my metadata changes are replaced by the original metadata for purchased content, so messing up my filing system.  This apparently is known and 'normal' apple behaviour.  And it is self-contradictory - for when i look at my device list of songs in iTunes on laptop, my metadata changes are listed as intact.  I'm not sure whether the iPhone is simply ignoring metadata changes or whether the original metadata is over-writing via iCloud.
    My question is, why would anyone design the system to ignore a user's metadata changes when using the iPhone ?  In what way is this good ?  And why not have a simple toggle switch 'respect my metadata changes on device - on/off' ?  I can't believe I'm unique amongst Apple users in wanting to listen to classical music  on an iPhone?!
    many thanks Paul

    Settings > Music > unselect "Group by Album Artist" seemed to work for me.

  • I'm stuck! Going from LR3 to CS5 I don't get Camera Raw dialog box

    I'm stuck. When I edit pics from LR3 to CS5 the Camera Raw dialog box does not open. Everything is updated.  I can get Camera Raw dialog box to open if I open a photo directly in to CS5.  I have looked at my external editing options.  All seems fine.  Please help.  Thanks!

    I'm not a LR user, but I believe it serves as your raw converter (similarly to ACR), therefore when you edit directly out of LR into CS5 the image is already rendered ready for CS5 usage.  If you start directly in CS5 then ACR is invoked for raw file conversion.
    Richard Southworth

  • HFM-Metadata changes -impact on Database.

    Hello Experts & Gurus,
    1)  I want to understand the impact of changes in MetaData (Members of Dimensions like Scenario, Year, Period....) on the size of database in HFM.
    2) If Metadata changes can result in creating new tables or cubes, can we find out such new tables or cubes which were created and delete them to take back the Database to Normal Stage.
    Thanks in Advance....

    Hello Erich,
    Thanks for your reply.
    We have did some changes to MetaData and uploaded into production. We had some serious issues with the performance of the Application.
    We revoked the MetaData but still we have problems with Application.
    What strange we have observed is size of Data, which has increased three folds than previous, I am of opinion that change in MetaData might of created new cubes or tables and increased the size.
    Please correct me if I am wrong and let me know your opinion what might have increased the data base size..
    Thanks & Regards.

  • Possible Bug: Excessive writing to TEMP directory for any PDF metadata change

    I am using the latest version of Adobe Bridge CC 6.1.0.116 x64 for Windows.
    I use Adobe Bridge to manage large archives of scanned PDF's composed of full page JPG's.
    Whenever I attempt to change metadata on these PDF's, Bridge performs heavy writing to the TEMP directory. Even when using an SSD, changing any metadata is very slow and the TEMP writes are enough to produce noticeable wear on the disk.
    [I would have attached screenshots, but I get a "That image type is forbidden" error in these forums whenever I attempt to upload screenshots (either JPG or PNG; and they are less than 900px on longest edge).]
    Resource Manager:
    IMAGE: Bridge.exe
    FILE:...\Temp\A9R12b8-1315f76
    WRITE: 349,175,808 B/sec
    The Task Manager also shows 356MB/sec writes for over fifteen seconds for each metadata change, with brief pauses between files.
    This amount of data written amounts to about 20GB each minute!
    (Note that the files I was modifying in this test averaged only about 100MB each.)
    Bridge did not always do this. I remember earlier versions performed metadata changes swiftly without these excessive write issues. I do not remember in which version this problem began, however.
    Resaving the files in question does not solve the problem. I have also tried exporting as Postscript and re-Distilling, and even exporting JPG's and recreating the PDF from scratch.
    This problem seems to affect any PDF that is a collection of full-page JPG's. The PDF's that I have made from TIFF's or non-rendered text do not cause this issue. On non-JPG based PDF's metadata changes are fast and do not cause noticeable writes to the TEMP directory.

    Thanks a lot Rob. That works.
    "Rob Woollen" <[email protected]> wrote in message
    news:3f29b665$[email protected]..
    java -Djava.io.tmpdir=<tmpdir path> weblogic.appc
    -- Rob
    Bernhard Lenz wrote:
    I realized that weblogic.appc creates a working directory
    /var/tmp/appcgen
    when compiling ejbs. What happens if 2 developers run weblogic.appc atthe
    same time? Will they be using the same temp directory and therefore getin
    each others way? I'd rather like to create a temp directory which isunique
    for the machine. Our build scripts would be able to create such adirectory
    but I couldn't find anything in appc to set the temp directory.
    Do you have any advice?
    Thanks for your help.
    Greetings
    Bernie

  • [svn:osmf:] 14317: Pre-PARB metadata changes: Merge IIdentifier and ObjectIdentifier, rename to FacetKey.

    Revision: 14317
    Revision: 14317
    Author:   [email protected]
    Date:     2010-02-21 17:09:26 -0800 (Sun, 21 Feb 2010)
    Log Message:
    Pre-PARB metadata changes: Merge IIdentifier and ObjectIdentifier, rename to FacetKey.  Make similar adjustments to TemporalFacet class.  Move TemporalFacetEvent to events folder.  Update unit tests and samples.
    Modified Paths:
        osmf/trunk/apps/samples/framework/CuePointSample/src/CuePointSample.mxml
        osmf/trunk/apps/samples/plugins/AkamaiPluginSample/src/AkamaiPluginSample.mxml
        osmf/trunk/apps/samples/plugins/CaptioningSample/src/CaptioningSample.mxml
        osmf/trunk/apps/samples/plugins/ControlBarPlugin/src/ControlBarElement.as
        osmf/trunk/apps/samples/plugins/ControlBarPluginSample/src/ControlBarPluginSample.as
        osmf/trunk/apps/samples/plugins/MASTSample/src/MASTSample.as
        osmf/trunk/framework/OSMF/.flexLibProperties
        osmf/trunk/framework/OSMF/org/osmf/elements/CuePoint.as
        osmf/trunk/framework/OSMF/org/osmf/elements/VideoElement.as
        osmf/trunk/framework/OSMF/org/osmf/elements/f4mClasses/ManifestParser.as
        osmf/trunk/framework/OSMF/org/osmf/events/FacetValueChangeEvent.as
        osmf/trunk/framework/OSMF/org/osmf/events/FacetValueEvent.as
        osmf/trunk/framework/OSMF/org/osmf/layout/AbsoluteLayoutFacet.as
        osmf/trunk/framework/OSMF/org/osmf/layout/AnchorLayoutFacet.as
        osmf/trunk/framework/OSMF/org/osmf/layout/BoxAttributesFacet.as
        osmf/trunk/framework/OSMF/org/osmf/layout/LayoutAttributesFacet.as
        osmf/trunk/framework/OSMF/org/osmf/layout/PaddingLayoutFacet.as
        osmf/trunk/framework/OSMF/org/osmf/layout/RelativeLayoutFacet.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/Facet.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/KeyValueFacet.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataNamespaces.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataWatcher.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/ObjectFacet.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/TemporalFacet.as
        osmf/trunk/framework/OSMF/org/osmf/net/dvr/DVRCastDVRTrait.as
        osmf/trunk/framework/OSMF/org/osmf/net/dvr/DVRCastNetConnectionFactory.as
        osmf/trunk/framework/OSMF/org/osmf/net/httpstreaming/HTTPStreamingUtils.as
        osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as
        osmf/trunk/framework/OSMFTest/org/osmf/elements/TestVideoElement.as
        osmf/trunk/framework/OSMFTest/org/osmf/elements/f4mClasses/TestManifestParser.as
        osmf/trunk/framework/OSMFTest/org/osmf/layout/TestAbsoluteLayoutFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/layout/TestAnchorLayoutFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/layout/TestLayoutAttributesFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/layout/TestPaddingLayoutFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/layout/TestRelativeLayoutFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestKeyValueFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestMetadataWatcher.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestTemporalFacet.as
        osmf/trunk/framework/OSMFTest/org/osmf/utils/TimerTimeTrait.as
        osmf/trunk/plugins/CaptioningPlugin/org/osmf/captioning/media/CaptioningProxyElement.as
        osmf/trunk/plugins/CaptioningPlugin/org/osmf/captioning/model/Caption.as
        osmf/trunk/plugins/CaptioningPluginIntegrationTest/src/org/osmf/test/captioning/media/Tes tCaptioningProxyElement.as
        osmf/trunk/plugins/CaptioningPluginTest/src/CaptioningPluginTest.mxml
        osmf/trunk/plugins/MASTPlugin/org/osmf/mast/media/MASTProxyElement.as
        osmf/trunk/plugins/MASTPluginIntegrationTest/src/org/osmf/test/mast/managers/TestMASTCond itionManager.as
        osmf/trunk/plugins/MASTPluginIntegrationTest/src/org/osmf/test/mast/media/TestMASTProxyEl ement.as
    Added Paths:
        osmf/trunk/framework/OSMF/org/osmf/events/TemporalFacetEvent.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/FacetKey.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/TemporalFacetKey.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestFacetKey.as
    Removed Paths:
        osmf/trunk/framework/OSMF/org/osmf/metadata/IIdentifier.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/ObjectIdentifier.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/TemporalFacetEvent.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/TemporalIdentifier.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestObjectIdentifier.as

    These are automated emails from the OSMF forums.  To unsubscribe, go here:
    http://forums.adobe.com/community/opensource/osmf/commits
    -- Brian

  • [svn:osmf:] 14313: Pre-PARB metadata changes: Rename MetadataUtils to MediaTypeUtil.

    Revision: 14313
    Revision: 14313
    Author:   [email protected]
    Date:     2010-02-21 14:34:19 -0800 (Sun, 21 Feb 2010)
    Log Message:
    Pre-PARB metadata changes: Rename MetadataUtils to MediaTypeUtil.  Make MediaTypeUtil non-public, as it's fairly trivial for clients to check for matches on their MIME type.
    Modified Paths:
        osmf/trunk/framework/OSMF/.flexLibProperties
        osmf/trunk/framework/OSMF/org/osmf/elements/F4MLoader.as
        osmf/trunk/framework/OSMF/org/osmf/elements/ImageLoader.as
        osmf/trunk/framework/OSMF/org/osmf/elements/SWFLoader.as
        osmf/trunk/framework/OSMF/org/osmf/elements/SoundLoader.as
        osmf/trunk/framework/OSMF/org/osmf/metadata/MediaType.as
        osmf/trunk/framework/OSMF/org/osmf/net/NetLoader.as
        osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestMediaType.as
        osmf/trunk/libs/ChromeLibrary/src/org/osmf/chrome/controlbar/widgets/PinUpButton.as
        osmf/trunk/libs/VAST/org/osmf/vast/media/DefaultVASTMediaFileResolver.as
        osmf/trunk/plugins/SMILPlugin/org/osmf/smil/loader/SMILLoader.as
    Added Paths:
        osmf/trunk/framework/OSMF/org/osmf/metadata/MediaTypeUtil.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestMediaTypeUtil.as
    Removed Paths:
        osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataUtils.as
        osmf/trunk/framework/OSMFTest/org/osmf/metadata/TestMetadataUtils.as

    These are automated emails from the OSMF forums.  To unsubscribe, go here:
    http://forums.adobe.com/community/opensource/osmf/commits
    -- Brian

Maybe you are looking for