Writing metadata to media-file

Hello everybody,
I'm developing an application for viewing/editing metadata of media files (mainly MP3). Therefore I'm using JavaFX 2.2.
Viewing works like a charm, but I'm currently stuck at the editing part.
I've tried media.getmetadata().put("string", object) but this throws only an UnsupportedOperationException.
Am I doing anything wrong? Or is there any other way writing metadata to media files without using external libraries?
Thank you in advance

is there any other way writing metadata to media files without using external libraries? No.
JavaFX media libraries are currently only support playback and not editing (even for metadata).

Similar Messages

  • Lighroom 3 writing metadata to image files?

    Hi,
    I have been wondering why my backups (differential) weregetting larger than they should, and I noticed that some of the files (.psd and .jpg, and mayde few .tiff) were modified. Interestingly, I do not see this happening to cr2-files, that I mostly use. After trying to figure out what's going on I noticed that corresponding xmp-files were modified also. This is not the issue due to their small size, but still I had not edited images that were changed for quite a while.
    Change that I see in xmp-files is rather large, and presumably related to Adobe's change in xmp-data structure. Eg.
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c007 1.136881, 2010/06/10-18:11:35   
    ">
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40   
    ">
    In addition to the sample above, whole xmp structure is changed. So I presume that maybe LR is writing metadata chages to xmp in the background?
    What I find disturbing is that when checking changed jpg files, I saw the similar data written into the jpg files also (files were created with oldish Canon 20D, and not edited for quite a while). These are examples from changed jpg-files (not the same from which the abone xmp-data change was taken, but similar change is visible in the corresponding XMP):
    Also jpg-file from offset 0x04 was changed from "50 60" to "51 18". Also offset 0x10 was changed (16 bits).
    I have Lightroom configuration option "Include develope settings in Metadata Inside JPEG, TIFF and PSD Files" not selected. The option "Automatically write changes to XMP" is selected. To my understanding neither of these should not have impact to the issue. Is there something else I should check?
    Change is made most likely by Lightroom 3.5 version, and has not occurred with previous versions. I have not notices this happening with 3.6, but I have been using it only few weeks. Is this known issue with previous version 3.5, or am I missing something obvious?
    System running is Windows 7 pro 64bit. I have not have any issues with LR lately, except crashes that I white about a week ago.
    Any advice on what's going on?

    So I was missing something. Thank you Hal.
    I had not realised that XMP goes inside of actual image files with those file types. Obviously my new backup routine spotted that, as I was on backuping only modified/new files.
    I would much prefer that also with above mentioned file types XMP-data would be stored in sidecar files instead of modifying the original file. To support this there are two arguments that I think are valid:
    1) modification of the file is always risky (and spesifically, with image originals I prefer to avoid that),
    2) modification leads to the fact that "smarter" backup strategies relying on "full backup" supported with differential or incremental backups lead to unnecessary long backuptimes and media consumption.
    That said, I prefer to have XMP-data also outside of the catalog so that other tools can also utilise it  (further, in addition to the catalog with sidecars I have sort of failover approach, and some of you may now say "belt and syspenders" after mentioning backups...).
    Is there a way to have all file types to utilise sidecars rather that modifying original file?

  • Error writing metadata to any file except jpegs

    Hi all,
    A coworker and I have been assigned the job of keywording all the photos in our database. We aren't photographers and are only messing with the keyword metadata on the photos.
    But we've been having a consistent problem with Bridge CS4. When I attempt to add keywords to any file format except jpeg, it gives me an error message "Error writing metadata to " and the filename. Then to make matters even worse, Bridge continues trying to add the metadata to the same images over and over again until I do a forced shutdown.
    We're running Bridge on a network with exported cache. The only thing I have found as a possible solution is a permissions setting problem, but I can't find any way to check on that.
    Any help you can offer would be great. Thanks!

    I had this same problem. This was the solution for me in my CS4.
    Go to Bridge
    Go to Preferences
    Go to Metadata
    Make sure IPTC and Keywords are checked.
    This will allow you to add keywords to your metadata in bridge.
    Here it is not checked:
    Here it is checked:

  • Error writing metadata to photo files

    I am using CS6 and have moved to a new computer with a clean install of CS6 under Windows 8.1.  In the past I had no problem using Bridge to append my personal metadata file to photos (RAW files, NEF).  With the new installation I am getting the repeated message " Error writing data to...."  even after trying all the " fixes"  suggested by the help files.
    Can anyone help me to resolve this issue?
    Thanks.

    I found an answer, somewhat different.  I did more search and found that you need to be administrator and for Adobe to see you as administrator, for many functions to work, such as writing metadata to files or putting stars on photos to rank them.  I could do neither.
    THEN, I tried opening Bridge by right clicking on the icon, and opening the file as administrator (a choice).  Everything worked.  So, why was Adobe not seeing me as administrator.  My user account was the only account on the computer and has administrator privileges.
    I started doing searches on that, and stumbled, yes stumbled, on what I think is a solution to that situation.
    I set up my account so that I needed a password to log in.  Once I did that, Bridge worked fine.  But, I still did not want that additional startup step.  You can then back to change password and leave the password entries blank.  Then, the computer starts up with blank passwords, zips past the welcome screen directly to the desktop, and Windows now sees me as the administrator, and so does Adobe.
    Keep you fingers crossed folks, this seems to be working.

  • Bridge CS3 not writing metadata to JPEG files

    For the last couple of months (without my noticing until a couple days ago) all JPEG files that I have edited using Bridge CS3 (on Windows XP) do not have the metadata built into the file. Here are the symptoms: use "File Info" to edit the metadata for a JPEG file (i.e. add a title, description, copyright info, etc.), all appears normal, but if you do any of the following, the metadata you entered disappears:
    - duplicate (the metadata does not exist in the duplicate file)
    - move or copy to another folder
    - open in Photoshop or any other software that can read metadata (File Info shows none of the metadata you entered)
    - rebuild the cache for the folder
    Strangely, the metadata still appears with the file when you look at it in Bridge as long as you don't do any of the above.
    This is really awful as I've put a lot of time into entering this metadata for hundreds of files. Older files (pre-Nov 08) don't have this problem and the metadata is "sticky" and doesn't get deleted. So, somehow my Bridge CS3 got corrupted along the way.
    Has anyone experienced this and more importantly -- do you have a solution? I've tried reseting all Bridge settings (but that of course purged the cache and deleted all my metadata.)

    Hey,
    There are various date/time fields shown in properties panel in Organizer. The dates mentioned in general section are read from OS whereas the dates in EXIF field are read from image's EXIF data. In EXIF data there are three date/time fields-
    1. Date time- This date/time info shows date modified of EXIF properties. So when you are writing a tag into imags's IPTC, you are doing some change in EXIF data. Hence this date should change to date when you are writing a tag into IPTC.
    2. Date time original - Represents date time when a image was shoot.
    3. Date digitized - Represents the date when the image was digitized (in digital camers there is hardly some delay between an image is shoot and it is digitized. So this field is always same as date original).
    So, in your scenario, Date time in EXIF should change whenever you are writing any tag into its IPTC.
    Please let me know if you need more info on it.
    ~Andromeda

  • Can no longer write metadata to Raw files

    My team an d I are working in Photoshop CS5, we write metadata to jpegs and Raw files- saving to Raw database not as sidecar .xmp files.  We are no longer able to save the metadata to Raw files.  There is no error message, the data writes like normal and the user who writes the metadata can see it but when you open in another computer the metadata fields are empty, however the jpegs do have the new metadata.  Was there a setting change at some point? This has been going on for a couple months and I cannot find an answer anywhere.  Again, we batch write to RAW+Jpeg, the jpeg files save the metadata but the Raw files look like the data saved but is not visible on any computer other thant he one that added the new metadata. This is occurring on multiple computers, both Mac and PC.

    TimVasilovic wrote:
    I understand the process you are describing,  In the past I have been able to embed metadata to a Raw file, move it to a server, pick that file up on another computer and see the metadata without need of the .xmp sidecar.  Is the ability to embed no longer supported  by Photoshop? Since this issue began we have taken to doing all our metadata editing in PhotoMechanic, which embeds without creating a sidecar.  If Photoshop is pushing people to create sidecar .xmp files only for writing metadata to Raw files I will probabaly move fully to PhotoMechanic because using sidecars has proven tricky in the past with how our files get moved around.
    If using Adobe Camera Raw on camera raw file you either have an XMP sidecar file created or the data is stored in a database.  Which happens it is your option in Edit/camera raw.  If you use ACR and edit a jpeg it does not create a distinct XMP file but it is also not directly written to the image either.  One can still delete the edits in Bridge with Edit/develp settings.
    If you use a DNG the metadata is written to the image.  Not sure what process Photo Mechanic uses.
    It appears to be a permission problem as other than CS6 Bridge is now 64 bit and has a new cache method there are no changes in how it handles metadata.

  • Lightroom 5 can't write metadata to DNG files

    I have converted a large number of Canon and Nikon raw files to DNG using Adobe DNG Converter (version 8.2.0.94). 
    Using Lightroom 5.2 I wanted to change metadata in these master DNG files.  I import the files into a catalog, select all, modify the metadata, then invoke the Metadata->Save Metadata to Files...  For many (but not all) of the files I get the following message:
    "Could not write metadata.  Unknown file formats."
    The DNG files reside on a Synology NAS server.  If I copy them to a local disk I do not get the above error.  But I would like to make metadata changes to the files on the NAS.
    I do not have problems importing or viewing DNG files from the NAS.  Why does LR 5 have problems writing DNG metadata to the NAS?  How can I fix this?

    Thanks for replying.
    The problem is definitely not one of permissions. I am accessing the NAS from an admin account with full permissions to read/write the files and directories.
    I'm inclined to believe it's the second cause you propose -- network protocol causing data corruption. 
    It seems to be specific to writing metadata to large files such as DNG or TIFF.  I don't get errors writing to JPEG.  And it is inconsistent -- sometimes retrying fixes it.  And, oddly, sometimes I even get the error "photos have read-only access" when it's clear the permissions are OK.
    On the other hand I have had no problems copying thousands of DNGs to/from the NAS -- no errors and no corruption.  So the issue seems to be an interaction between the NAS and LR when LR is updating the metadata on an existing file and the file is large.

  • Error writing metadata to file

    I am getting constant error messages from Bridge CS4 when trying to add keywords to my images "Error Writing Metadata to file "XXXX". It's very annoying and destroying my workflow. I have tried resetting original preferences, and using purge cashe. Finally I reorganized my entire folder structure which seemed to make the problem less frequent.
    The circumstance that makes this error pop up most frequently is when I add keywords to a handful of files that already have another keyword assigned. Quitting the folder and then re-entering it solves the problem for the photos with the current error, but then 20 or so photos later I get the error message again.
    Any Fixes?

    A new suspicion was that the read/write data might be different for the images files themselves than it was for the folder holding them. So I applied the read/write permission to the image files themselves. No luck though. Still getting "Error writing metadata to file xxxx" Errors. Would love to be spending all this time editing photos instead of chasing down bugs. Brand new MacBook Pro and I'm spending more time trying to fix errors than using the software. ::sigh::

  • Faillure writing metadata to some DNG files

    I'm having a problem writing metadata to some dng files using Lightroom 2.6.1. When I try to apply a metadata template to a batch of files most of them get changes but a few don't. This only effects DNG files so far JPEG and TIFF seem to be OK. I have tried running the problem files through DNG converter and the new files have the same problem. Lightroom won't write to them.
    I can change the metadata of these files from Bridge. The changes then appear properly in Lightroom. Afterwards I can change the metadata again from Lightroom.
    I'm working on a MacBook Pro (Late 2008) and running OS 10.6.2.

    I created a preset to export to same folder as original, same format as original, and stack with (above) original. I used this on the seven files, and it has solved the problem without losing any metadata.
    The jpegs had at some point been processed by Photoshop Elements as they were imported/edited using that application in 2010 but the metadata problem didn't show up until recently when I was making some adjustments in Lightroom. I somehow think this may be related to the GPS tag though I don't have sufficient evidence.
    The DNG file was strange in that it was straight the camera with no Lightroom adjustments, although I did add GPS info in the Map module. Anway it is now fixed as well as the jpegs.
    With this preset it would be possible quickly to fix a large number of image files. Just create a Smart Collection to display the problem files and run the preset on them all in one go. The only things that I am aware of that you would need to look out for are (1) if they are in a collection other than a smart collection, or have been published to a service like Flickr or to the Hard Disk the link will be broken, and (2) If you like to sort photos by date/time added, they will be out of the sequence (capture time is fine).
    When you are satisfied that this has worked OK then you can delete the images from the "Metadata Not Up To Date" smart collection. Select all, go to all photos, they should remain selected and press Delete. You could do a thousand in one go if you have the nerve for it
    Hope this helps.
    Peter

  • Errors when writing metadata to files on Windows Server

    Good day!
    I have an iMac running OSX 10.9 (Maverick) and Lightroom 5.2.
    My catalog is on the local iMac drive, and the images are on SMB shared drive (handled by Windows 2012 server).
    I decided to do the final layout of my album using InDesign, and for that I needed to access to images using Bridge. So selected all the images (the rated once...) and issue a Metadata/Save command.
    The system came back with errors on many of the files (such as Photos are read only, and unknown errors).
    Retrying to save the metadata on image that was flagged with an error usually (but not always) worked.
    I tried to select save the metadata for few (6) images in a time, many times it was ok, but sometimes, one or two of them failed (and retrying again usually solved the problem).
    It looks to me like a timing related issue.
    Any ideas?
    (After spending about an hour on this, I have exported the images to my local drive...). In general I don't have similar problems with other apps.
    Any ideas?
    Yuval

    I Yuval
    I'm experiencing more or less the same behavior (see Read-only error when writing metadata to file over network (Synology DS1315+ using AFP) ). For me however, the problem is more pronounced if I use the AFP protocol and is better (I think as you described) if I use SMB (all done on a Synology DS1315+). With SMB it most often works but in very rare cases I also get the "read only" message!
    Do you have solution to this? Or are you stuck as I am?
    Cheers, Chris

  • Error when Writing Metadata to Files in Bridge (Mac) but not in Bridge (PC)

    We get an error when writing metadata to files in Bridge (Mac) but not in Bridge (PC). In the same drive and folder, the PC can successfully write a keyword to a file on the PC, where the Mac returns an error. I have researched this at the Adobe Knowledgebase, but their answer seemed to indicate it was a global issue, and we don't see that behavior on the PC.
    The client is a Mac of course, and the server volume is a Windows share volume. The Mac is bound to AD, and the domain\username and username formats have both been tried when logging in, but you receive the error in both.
    Any help would be appreciated.
    Thanks!
    Rich Oliver

    Hi, I'm having the same problem using FreeNAS (which uses Samba and Netatalk in the backend), but I tried with both AFP and SMB on Mavericks and Yosemite, I still have the same issue.  I think it might be a timing issue with how lightroom interact with a slower write delay using network shares.  I suggest you also chime into this thread:  Lightroom 5 can't write metadata to DNG files   I really hope this is resolved as this is impacting my productivity as I moved my workflow to my Macbook with a shared NAS.

  • DNG file modification date not changed by writing metadata?

    I use LR 2.7 on Windows XP.   To my surprise, I just noticed that writing metadata updates (e.g., new keywords) from LR to the DNG files does NOT appear to update the file modification date, which suggests obvious issues for backup strategies (yes, I understand that a changed modification date introduces other backup issues).   I have verfifed that the metatdata does indeed change in the DNG files, so I am mystified.   Can someone shed some light on this?   Thanks.
    js
    www.johnshorephoto.com

    Yes, I explicitely invoke "save metadata to file".   Furthemore, I have checked the behavior by (a) modifying DNGs in LR; (b) saving the metatdata to the DNG; (c) creating a new LR catalog and importing the revised DNGs.    The metadata changes do show up in the re-imported DNGs (and the metadata field "Metadata Date" correctly shows the recent change).  Morevover, the file sizes do change (wth the metadata changes) even though the modification dates shown in windows explorer do not change.
    However, I just redid the experiment to double check, and discovered an important clue - the mysterious behavior occurs when the DNG files are on a NAS device (in particular a Netgear ReadyNAS Duo.   To summarize:
         - When the DNG files are on a local hard drive, the file modification dates change as expected
         - When the DNG files are non local (i.e., on the network but on a NAS device), the file modification dates do not change even though the file sizes do change;
    What's more, I see the same behavior when accessing the DNGs via Adobe Bridge (CS5) - i.e., if I change the metadata, I'm asked if I want to apply the metadata changes to the DNG, and I say yes (and confirm by looking via Bridge at a copy of the changed file).   On a local disk, the file modificaiton dates change (as do the modification date displayed in Bridge), but if the files are on the NAS, the modification dates do not.
    Any additional thoughts?
    js

  • Writing metadata back into photos without exporting each file

    I am most likely going to be switching from PC to Mac. I currently use Adobe Photoshop Elements to organize my photos. I like iphoto, but it is lacking a lot of the features I enjoy in Elements.
    One feature that I use a lot in Elements that I can't seem to find in iphoto is writing of keywords, descriptions, and GPS data back into the metadata for the file. In Elements, you click a button and the data is written into the original file. But, how do I do that in iphoto? Do I have to export it? That seems strange to me.
    -Debbie

    You can do it with the demo version ofMedia Expression. But you only have about a 20 day window to use the application. Follow the first 8 steps of Old Toad's Tutorial #1 - Recovering Keywords and Rolls From a Damages or Crashed iPhoto 6 or 7 Library for a New Library.. It applies to iPhoto 8 also.

  • Writing metadata to file iphoto 11

    I came across a script (by Andrew Turner, linked to from here -http://stuffforlife.blogspot.com/2009/10/face-recognition-in-adobe-photoshop.htm l) that writes the iphoto metadata to the original file, allowing the metadata to be read by other apps.
    However, i get an error
    Here's the script.
    -- This applescript will set the exif keywords, name, and comments of all selected iPhoto
    --   images using the information current in iPhoto.
    -- Author: Andrew Turner (http://highearthorbit.com)
    property copyright : "©. All Rights Reserved."
    property URL : ""
    property exifToolOriginal : "_original"
    -- True retains copyright, False means Public Domain
    property Copyrighted : "True"
    tell application "iPhoto"
      activate
              try
                        copy (my selected_images()) to these_images
                        if these_images is false or (the count of these_images) is 0 then ¬
                                  error "Please select a single image."
                        repeat with i from 1 to the count of these_images
                                  set the keywordslist to ""
                                  set this_photo to item i of these_images
                                  tell this_photo
                                            set the image_file to the image path
                                            set the image_title to the title
                                            set the image_filename to the image filename
                                            set the image_comment to the comment
                                            set the assigned_keywords to the name of keywords
                                  end tell
                                  repeat with j from 1 to the count of assigned_keywords
                                            set the keywordslist to keywordslist & " -keywords+=" & item j of assigned_keywords
                                  end repeat
                                  set output to do shell script ¬
                                            "exiftool -title='" & image_title & ¬
                                            "' " & keywordslist & ¬
                                            " " & " -comment='" & image_comment & ¬
                                            "' " & " -Copyright='" & copyright & ¬
                                            "' " & " -CopyrightNotice='" & copyright & ¬
                                            "' " & " -Rights='" & copyright & ¬
                                            "' " & " -Marked='" & Copyrighted & ¬
                                            "' " & "'" & image_file & "'"
      do shell script "rm '" & image_file & "'" & exifToolOriginal
                        end repeat
                        display dialog "Exif writing complete."
              on error error_message number error_number
                        if the error_number is not -128 then
      display dialog error_message buttons {"Cancel"} default button 1
                        end if
              end try
    end tell
    on selected_images()
              tell application "iPhoto"
                        try
      -- get selection
                                  set these_items to the selection
      -- check for single album selected
                                  if the class of item 1 of these_items is album then error
      -- return the list of selected photos
                                  return these_items
                        on error
                                  return false
                        end try
              end tell
    end selected_images

    yeah, i just noticed that...!
    when exiftool is working, does it write the metadata to the original raw file or the jpeg.
    trying to find info on how to get round the "warning duplicate orientation tag in IFDO" error, has me scratching my head
    i also have aperture 3 trial, wil this allow face keywords from iphoto to be added as metadata to the file?
    cheers

  • Metadata writing in progress (n files pending).... error

    After updating to the latest version of the Premiere Pro last week, everytime I am closing the project I now get a "Metadata. Metadata writing in progress (n files pending). If you quit before writing is complete, data will be lost. Are you sure you want to quit? Yes/No" error window. Please see a screenshoot attached for one of such errors.
    What is interesting, is that no matter how much time i give it the process is never complete.

    dkitsov wrote:
    After updating to the latest version of the Premiere Pro last week, everytime I am closing the project I now get a "Metadata. Metadata writing in progress (n files pending). If you quit before writing is complete, data will be lost. Are you sure you want to quit? Yes/No" error window. Please see a screenshoot attached for one of such errors.
    What is interesting, is that no matter how much time i give it the process is never complete.
    So the metadata writing in Premiere is fairly involved.
    It tries to write metadata in the background asynchronously, but only when the file isn't being touched by something else in the application or by some other application.  What you're experiencing is potentially (I can't say for sure yet) where these 23 background metadata writing tasks never finished, or someone else never let go of the file.  If that someone else is Premiere, it is definitely a bug (which is my current guess).
    Are you able to provide which file types these 23 files are, and what sort of drive/volume they're on (e.g. local/external USB/firewire/SSD/etc).
    And since a number of other posters are mentioning that this started in 6.0.2 for them, is that the same for you?

Maybe you are looking for