Metadata handling in ProxyElement (inconvenient)

Hello!
I've come across the inconvenience when working with metadata in ProxyElement.
1) Every element that is proxied gets ProxyElement metadata values (that have been set before) on permanent basis and not loses it after being unset as a proxied element:
public function set metadata(value:Metadata):void{
// Transfer all old values to new: 
for each (var url:String in proxiedMetadata.keys){
value.addValue(url, proxiedMetadata.getValue(url));
proxiedMetadata = value;
proxiedMetadata.addEventListener(MetadataEvent.VALUE_ADD, redispatchEvent);
proxiedMetadata.addEventListener(MetadataEvent.VALUE_CHANGE, redispatchEvent);
proxiedMetadata.addEventListener(MetadataEvent.VALUE_REMOVE, redispatchEvent);
2) Consumer that is listening for METADATA_ADD of ProxyElement never gets informed of new values appearing in ProxyElement metadata after the proiedElement is set. Look at this code in creating ProxyElement:
proxy2 = new ProxyElement(); 
proxy2.addEventListener(MediaElementEvent.METADATA_ADD,
function(event:MediaElementEvent):void { 
trace ("METADATA ADDED: " + event.namespaceURL);});
proxy2.addEventListener(MediaElementEvent.METADATA_ADD,
function(event:MediaElementEvent):void { 
trace ("METADATA REMOVED: " + event.namespaceURL);});
And this, say, button click handler:
 var e:MediaElement = new MediaElement(); 
if (null == proxy2.getMetadata("META1")) {e.addMetadata(
"META1", new Metadata());}
else {e.addMetadata(
"META2", new Metadata());}
proxy2.proxiedElement = e;
METADATA_ADD and METADATA_REMOVED are never called.
This is particulary inconvenied when using LoadFromDocumentElement. Imagine complex processing of loaded content with adding metadata to it - top level LoadFromDocument will never inform a listener of the addition of proxied metadata when its content is loaded and formed.
For now I'm using a temporary solution like this:
 override public function set proxiedElement(value:MediaElement):void { 
     super.proxiedElement = value; 
     if (null == value) return; 
     //Copy all proxied metadata 
     var keys:Vector.<String> = value.metadataNamespaceURLs; 
     for each (var key:String in keys) {          addMetadata(key, value.getMetadata(key));
It does not fire METADATA_REMOVE events but OK for LoadFromDocuments.
I think it will be great if ProxyMetadata gets somehow rewritten in later releases - or may be I'm not getting a concept of ProxyElement?
What do you think?
Thank you!

Coorection on quick proxy remedy in my first post. The overriden func should look like this:
override public function set proxiedElement(value:MediaElement):void { 
     super.proxiedElement = value; 
     if (null == value) return; 
     //Dispatch proxied metadata events ;O) 
     var keys:Vector.<String> = value.metadataNamespaceURLs; 
     for each (var key:String in keys) {          metadata.dispatchEvent(
new MetadataEvent(MetadataEvent.VALUE_ADD, false, false, key, value.getMetadata(key)));     }
I did not take into account the:
var oldValue:* = data[key];data[key] = value;
if (oldValue != value){
in Metadata code - so resetting values as in my first post does not fire events.
Worked for me because my own bug :O)

Similar Messages

  • Improved Metadata Handling?

    The 1.1 PDF states:
    Improved Metadata Handling
    Mac OS X v10.4.6 includes support for EXIF metadata when exporting TIFF files with Aperture. You can view the EXIF information in exported TIFF files using other image editing applications, such as Adobe Photoshop.
    OK, when I use Open with External Editor, I see the EXIF data in Photoshop (namely the IPTC) but when I instead use the Export command to a TIFF, no data. Bug?

    Like William Lloyd posted earlier, I am not able to replicate this problem, at least on my PowerMac G5. Tried exporting the same image, loaded with IPTC data, in 16-bit and 8-bit TIF and PSD. Got the same results in all exports -- all the IPTC data showed up in Bridge Metadata panel and Photoshop Info window for all four images. Shoot only Canon Raw.
    Wonder if there is a source data to output data bug specific to a camera make/model? Perhaps if the posters who are having this problem can state the source image type (camera make/model/file type) we can see if there is a pattern.
    Mike
    PowerMac G5 Dual 2.0GHz, Radeon X800XT Graphics Card; MacBookPro 2.0Ghz   Mac OS X (10.4.6)   iMac800 and Powerbook G4 also in household

  • Quicktime Metadata handling in podcast producer batchs

    Hi,
    I'm wondering if there's a way to extend the amount of metadata that can be handled by the podcast producer batch so that it feets iTunes needs ?
    I know that it depends of the workflow you use for the "common" metadatas (artist name, year, type, ) but what about the exotic ones : commentaries, lyrics and even illustration ?
    Thanks in advance for your answer.
    Nicolas

    HAZAAR! Solved it for me, hope it's the same for you. Ensure your Server HOST name is identical to your service name. IT IS CASE SENSITIVE! I had to edit the /Library/PodCastProducer/Shared/Server/memberpreferencesUUID so it matched my hostname identically, and all is now working.
    You'll notice you probably have errors in /Library/Logs/pcastserverd/apache_error.log referencing SNI name not matching hostname, this is the clue. Hope this resolves it for you also.
    Pete

  • Photoshop and Metadata handling.

    We have two related issues we're trying to solution.
    (1) If we create a blank Photoshop file ("template") that is merely a size, resolution and color profile, when we add an image (that does contain metadata), the image's metadata is not retained in the template metadata. We need to be able to transfer that image's metadata, automatically, to the template. (We do not want to have to copy/paste.)
    (2) Let's say we now have a template with 1 image and associated metadata. We now need to add another image(s) to this template and have the second image's metadata also transfer automatically. (This auto-transfer of metadata would occur for any subsequent image added.)
    We are using CS4 v11.0.2.

    You may want to also ask over at
    http://forums.adobe.com/community/photoshop/photoshop_scripting
    as I suspect achieving this in Photoshop may require Scripting.

  • Aperture 3.1 doesn't export lens metadata

    When I export images from Aperature (File->Export->Version), they are missing lens metadata.
    I exported a master version of an image and a version of the same image.
    I open both the master and the version in DxO.
    The master contains lens metadata with a value of "18-105mm f/3.5-5.6" and the version is simply blank.
    This is a fresh copy of Aperature 3.1, with no plugins, and I can repeat this behavior for any master image that contains lens metadata.
    Is this a bug that will be fixed in a Aperature update? This is a very frustrating bug.

    I bought AP 3.1 after my metadata nightmares with iPhoto '09 (I wasn't going to pay for '11). AP 3 has some nice features (like iPhoto on steroids) and its metadata handling is much better than iPhoto. But this bug is really, really messing with my photo processing workflow.
    I'm going to keep looking for a solution (I haven't had the time thus far) and will update the thread. Thanks for the confirmation of the bug, and the commiseration
    -Elliot

  • Can the Metadata Browser be extended?

    I am thinking of filtering according to 'Focal Length' or 'ISO Speed Rating' or eventually the aperture f-value (if only this were not shown together with the exposure time in 'Exposure').
    Thanks
    Stefano

    Hoping, not only for extension but Metadata handling Module with more choices of handling Metadata than current two panes.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
    http://donricklin.blogspot.com/

  • Work around for writing out metadata to masters?

    I am sure that the aperture community has dealt with this before.
    Prior to purchasing aperture, I made sure that metadata like captions keywords, etc. could be written back out to the master file. This would allow one to not be held hostage to aperture. With various updates this ability has gone away. The statement from Apple less than a year ago, seems to indicate that aperture will not write metadata back out to the Masters.
    Quote: http://support.apple.com/kb/TA23784?viewlocale=en_US
    By Design: Aperture won't export metadata with RAW masters
    Unlike applications such as Photo Mechanic, Aperture does not write IPTC and keywords to the original RAW file. Instead, Aperture stores this information in its library and attaches it when exporting versions in JPEG, TIFF, PSD, or PNG format. If you export the RAW masters, none of your metadata changes will come along with them. Unlike the issues listed above, this feature is by design.
    If your goal is to archive RAW files outside of Aperture with metadata attached, you'll need a workaround to this aspect of Aperture's metadata handling. Because Aperture is designed to read added metadata at time of import (despite the current issue described above), the best long term solution (after issues are resolved) will be to add your metadata in Photo Mechanic (or similar) prior to importing them to Aperture and then refrain for the most part from using Aperture's metadata tools. If you don't like that workaround, a secondary workaround is to export JPEG versions to be kept alongside the RAW masters. To save disk space, the JPEG copies could be a minimal size."
    I am sure that many community members have encountered this problem. Specifically, I have many slides to scan, so the raw input file is a tiff. Aperture does not support writing metadata to tiffs. And to depend on aperture to write out metadata to any master file is probably setting yourself up for disappointment.
    Can the community recommend a way around this?
    Thanks

    You are referring to a very old document about Aperture 1, clearly marked as 'no longer updated'. Aperture 3 can export IPTC metadata with RAW files. You have the choice of embedding them into the RAW file, or write them in a separate xmp sidecar file. Just choose 'Export Master'. Aperture can also write back metadata into a RAW file without exporting them. Choose 'Metatadata - Write IPTC metadata to original'.

  • Nothing in list view of the browser

    Hi all
    I'm liking the new FCPX a lot but there seems to be a bug (perhaps only on my version). When I switch from filmstrip view to list view in an event, there is nothing in the list and then when I try and switch back to filmstrip nothing happens. Eventually it just crashes.
    I'm thinking that I may have to delete the plist preference file but I can't find it. Am I right to do this if there is one or shall I just re-download the app.
    By the way, this was happening on vers 10.0.0 and the new upgrade.
    Looking forward to rectifying this with your help.

    Aperture's metadata handling in the 1.x days skipped or missed some things (e.g. lens info). So images imported in the 1.x days may not have all the details. For these images, if you've upgraded to Aperture 2, running this may get you more EXIF info on the photo.
    For images that have been imported in the last 6 months, its not going to do anything at all.
    The one exception is if you somehow add GPS info to the RAW files themselves (with a tagging application) after they've already been imported. I think Ian Wood has a couple applications that will do this. Anyway, if you run this command after adding GPS info to a RAW file, I think Aperture will pick it up (I haven't managed yet to successfully add GPS info to a shot tho').

  • IPTC legacy Contact - not imported by 3.4.1

    Last year I tried out Aperture and found that it was able to see the 'IPTC legacy Contact' field. This is important for me, as it corresponds to the field "People" in the wonderful iView programme that I've been using for ever. It lists the people on my images. Recently when I upgraded to Mountain Lion, this old program stopped working however. And so I decided to buy a fresh Aperture, and import my pictures.
    However: the new version of Aperture does not import the IPTC legacy Contact anymore!
    This XMP:People field is equal to the IPTC:Contact (legacy) field, and in iView it is used to list the people on the image.
    I've checked the jpeg file using exiftool to see if Aperture can write fields using 'Metadata'->'Write IPTC Metadata to original', or do the inverse with 'Metadata'->'Update from Original'.  The result is:
    -- Aperture can write the IPTC legacy Contact field
    -- Aperture does not input the IPTC legacy Contact field
    That means that the new Aperture 3.4.1 version cannot do what the older version did half a year ago??
    Something else I notice, is that when I fill in the name of a face, this name is added as one of the IPTC Keywords.
    .. so should I try to copy my "XMP:People" = "IPTC:Contact" (the two are equal) to the Keywords?
    Is this is a known bug, where can I see a list of other known bugs in metadata handling?
    How soon it will be fixed? And will I  then be able re-read my metadata from the original files?
    Another question: in iView, I was used to being able to merge the metadata that I had entered with the fields in the file, where either information in the file or in iView would 'win' in the merger.  How should I do such an operation in Aperture?

    Same here. I checked on my iMac and an MBP in Aperture 3.4.1, MacOS X 10,8.2, and I see the same. Aperture exports the legacy contacts field, but it does not show it in the versions when importing an image.
    However, when I check the imported original/master image file, the IPTC field is not erased - the version just does not reflect the data stored in the legacy contacts field.
    Something else I notice, is that when I fill in the name of a face, this name is added as one of the IPTC Keywords.
    .. so should I try to copy my "XMP:People" = "IPTC:Contact" (the two are equal) to the Keywords?
    Keywords? or do you mean IPTC tags? The keywords are a special kind of metadata tags, and I do not see the "faces" names in the Aperture keywords. In which tag do you see them?
    if you want to use another IPTC field to store the Contact info, I'd recommend to copy your info to one of the metadata fieldds, that are not marked as "legacy". Any feature labelled "legacy" is likely not to be supported in the near future.
    Is this is a known bug, where can I see a list of other known bugs in metadata handling?
    I have not seen this bug reported before, and do not know of any list of known bugs.
    How soon it will be fixed? And will I  then be able re-read my metadata from the original files?
    Write a bug-report to Apple: http://www.apple.com/feedback/aperture.html
    They should be told, that users still depend on this legacy tag, otherwise the chances are slim that they will bother to fix it - the name "legacy" clearly indicates that this metadata tag is doomed and only supported for compatibility reasons.
    Your imported originals/masters still have this field and carry the data - at least mine do - so you might consider to write an Automator service to access them with a shell script using exiftool.
    But it might be easier in the long run to simply copy these data to a different tag that is still supported.
    in iView, I was used to being able to merge the metadata that I had entered with the fields in the file
    Aperture keeps the data you enter in the versions. Also, when you import an image file, the tags should be copied to the version. When you edit the tags and want to add these changes to the original file, you can use the command "Metadata > Write IPTC Metadata to Original". That will write your changes to the original file, but not merge the data.
    Just some thoughts - sorry that I do not have a solution for your problem
    Regards
    Léonie

  • List of new features in PSE11 vs. PSE10

    Does anyone know where I can get a comprehensive list of features that are new in PSE11 relative to PSE10?  I've seen the high level lists and videos.  But I'm looking for a complete technical type list, not a marketing oriented one.  I am interested in metadata handling, and the marketing lists never get down to that sort of thing.
    Also, I understand that PSE comes out with a new version every September/October.  Does anyone have any info on what will be in PSE12, particularly with regards to metadata handling?
    Thanks.

    BillCz wrote:
    Does anyone know where I can get a comprehensive list of features that are new in PSE11 relative to PSE10?  I've seen the high level lists and videos.  But I'm looking for a complete technical type list, not a marketing oriented one.  I am interested in metadata handling, and the marketing lists never get down to that sort of thing.
    I would be very much surprised if Adobe issued such technical type lists... especially for Elements. It seems that even for Photoshop or Lightroom, there is not much technical info in that metadata question.
    Also, I understand that PSE comes out with a new version every September/October.  Does anyone have any info on what will be in PSE12, particularly with regards to metadata handling?
    The usual answer is "Those who know don't tell, those who tell don't know..."

  • Focus points Aperture 3.0.3 not correctly shown

    Hi,
    When I press the Alt-F key-combination the focus points are shown in the image. But for some reason they are off. I took some pictures where I'm sure I used the center focuspoint, but in Aperture they show up as the far right focuspoint.
    Is this a known issue ?
    Grtx,
    Remco

    Remco - this is NOT an explanation or answer to your question (sorry), but I sometimes see the focus point highlighted in RED, other times it is highlighted in WHITE...I have 12 focus points in the VF and the display normally shows the correct one (as I remember), but as described, the selected point varies in color...I don't understand this and wonder if that part of the metadata handling is buggy...I've also noticed that sometimes metadata values are reported as scientific notation (2.3 x E*some value), other times as ordinal numbers (the correct way)..makes me suspicious of ALL of the metadata info presented.
    Sorry I couldn't help but only corroborate and commiserate...maybe someone from Apple will see this and look into the problems.
    cheers,
    david

  • Bridge modifying .mov files?

    I am suspecting Bridge to try and drive me nuts by randomly destroying my .mov files when I browse the folder where they are stored (within Bridge).
    Briefly: I convert my AVCHD files to .mov ones using ClipWrap (hello Adobe! Premiere can interpret .mts files but not Bridge?) and start adding metadata to them.
    A few days/week back, I reopen the same folder and say, half of my .mov files are now unreadable. When I check them in the finder, they appear as "modified today a few minutes ago" and their size is in the few dozen of KB (vs ~100 MB before). Now I have to get back the original and go through the conversion process again...
    Before I start screaming, has anybody experienced this? I will stop using Bridge (I was using it for its metadata handling capabilities, but at this price, no thank you).
    iMac i7 12GB RAM, Lion, Prod Premium CS 5.5 up-to-date

    I was just trying to narrow down the process to see if it was the conversion or the adding metadata that caused the problem.
    Can't also imagine this is caused by Bridge, however, writing metadata lets Bridge save data to the file itself. But again, not very familiar with movie files myself I just tried a .mov file and added some metadata to it. Ironically it does get a tiny bit smaller in size after having used the metadata panel (just in the range of 1 or 2 kb).
    As Curt already stated, Bridge is a file browser and highly unlikely to overwrite files from 100 MB with only a few kb metadata and deleting the original.
    Some other observations. In any case it is wise to use back up systems. It seems you did not have a back up from the converted files, assuming you also don't have a back up of the originals (?) you have a very dangerous workflow. Although Mac is pretty save it is a certainty any HD stops working once, not if but when. Some can last very long, some can't, some warn with different behavior, some don't...
    If you have set Bridge to launch at log in (it is a pref settings in Bridge) it is by default hidden. I don't agree with that default but it is a fact. If you don't want that behavior just go to the system preferences / accounts and under start at log in deselect the checkmark in front of Bridge so that it is ready for use when your start up from system is completed.
    When stating that the folder is modified at the same time you start Bridge can you clarify on the settings you have for Bridge? Do you have set cache to write to the folder?
    I don't have Lion and don't let Bridge write cache to folders but normally pointing Bridge to a folder should not effect the modification date of that folder.

  • How to edit video files (mp4, avi ...) meta data (Title, author ...) ?

    Hello all,
    After transcoding a DVD into MP4 using Avidemux I would like to change the video meta data title so that it looks great when listed into my favorite portable video reader.
    It seems Avidemux uses the file name as title, but do not provide any way to change it afterwards. I also know how to set the title using ffmpeg, but I do not want to re-encode the video each time I want to do that !
    Does anybody know about a simple tool (command line or gui) to change MP4 and other video formats meta data such the movie title ?
    Thank you very much for sharing your experience !
    Cheers,
    Chicha.

    shtrom wrote:
    Easytag works fine for MP4 files, but doesn't consider even showing AVI files in its list. I ended up using FFmpeg for similar purposes.
    From what I've seen around, it seems to have supported command line arguments like "-title" or "-comment". My version (22511-1) does no like them. It however supports a generic "-metadata" argument.
    ffmpeg -metadata title="TITLE" -metadata artist="ARTIST" -metadata date=DATE -metadata genre="GENRE" -metadata comment="COMMENT" -acodec copy -vcodec copy -i old.avi new.avi
    The list of metadata names FFmpeg supported at some point in time (r20910, 2009-12-21) can be found here [0].
    For some reason, my vlc (1.0.5-5) doesn't show them in the media information, but mplayer does.
    [0] http://multimedia.cx/eggs/supplying-ffm … -metadata/
    FFmpeg's metadata handling is in flux. If one builds an unpatched version from subversion right now, the metadata doesn't line up properly in some cases. This may be why VLC isn't seeing the data. It's for sure why MPD from Git is having trouble right now. The patch below fixes a lot of it. I added a comment on a bug report that I filed with FFmpeg previously to try to get them to commit it:
    http://lists.mplayerhq.hu/pipermail/ffm … 83487.html

  • IPTC issues with Save for Web

    I have images with the copyright notice field, copyright status, provider and source fields filled in.
    When I do a save for web, I'm trying to adjust the IPTC data that gets saved but nothing I do seems to work. On thumbnails, I don't need any of that data but I can't get it removed. No matter what I select, there's always stuff in the copyright notice field.
    Similarly, if I try to simply change the copyright status field and leave everything else as is, I usually lose (data gets wiped out) provider and source and I get extra data put into the copyright URL field which wasn't there before.
    I also get the file data cannot be read error when opening up these files sometimes because photoshops seems to mess up how it writes the IPTC data. Image data seems file, it's only when photoshop fills in the copyright url with the same data from the copyright notice without asking me.
    In CS2, I had to use ImageReady because it would wipe out all the data and then I just used iView to easily put back in the 3 fields I was using. Now that IR is gone, I figure I need to migrate this to CS3 but no matter what combination of options I select, it seems metadata handling is horribly inconsistent.
    Can anyone tell me how it works? I've tried making a script step to set the data I want, I've tried working with an image with the fields the way I want them and then doing the save for web so it records the data I want, I've tried both with and without the include XMP option but I can't seem to get anything to work properly.
    Edit: Didn't make it clear but I'm trying to record a batch action where I scale images to 6 different sizes and then do a save for web at each size.
    Please help.
    Thanks

    Depending on your use of the image in context, won't the transparent strip "disappear?"
    The only solution I know is to open it in Photoshop and manually crop out the transparent strip. AI or Save for Web also seems to antialias the edge of free-standing art over a transparent background. I just make the artwork slightly larger than the final cropped size, save for web, then crop in Photoshop.

  • Wrong capture time when importing from iPhoto to FCPX

    I am experiencing a strange problem when importing from iPhoto to FCPX. If I open the info panel in iPhoto I see the real date/time when the picture was taken, but if I import them to an event in FCPX using the PHotos Browser and I check the info it shows the time when the image was imported to IPhoto and everything gets messed up.
    I have search for somebody with same problem but I have not found anything so far.
    MY workaround is to import directy onto the timeline, but it is... well, a workaround.
    Thanks in advance

    Why is knowing that important during the edit?
    Yes, FCP only shows the date imported" date metadata.  Future updates of FCP X I assume will add more metadata support, such as Creation Date and Modification Date, since metadata is vital to FCP X and there are some metadata handling features that are on the way. 

Maybe you are looking for

  • No bootable device -- insert boot disk and press any key, over and over again...

    I've seen a lot of discussions about "no bootable device -- insert boot disk and press any key" but the answers in them don't seem to help me at all. from the begining... i was tryin to instal windows 7 on my 2014 iMac and after bootcamp prepared the

  • Requirement from other plant.

    Hi Gurus, There are plants A and B. Plant B is in need of service parts. Plant A is also not having stock for same parts then creates Purchase order for some vendor and corresponding requirement is triggered in plant B with reference as Procurement s

  • Is Now the Time to Upgrade?

    I have been a long time Mac user. Ever since the OS 7 days. I thought it would be good to start a thread to discuss when the best time is to upgrade to the next OS. What are the indicators it is stable enough? What are the other variables to take int

  • Help to find org.unit manager

    hallow here i try to find org unit manager but its not working well plz some one can help i think i have problem in dates but i not sure thankes & regards LOOP AT i_t_data INTO lw_t_data_0org. SELECT begda endda sobid FROM hrp1001 INTO TABLE lt_relat

  • Thunderbolt Adaptor with FW800 issue

    I have an iMac with a FW800 port.  I purchased a desktop 4TB RAID to hook up to my MBP with Thunderbolt.  It comes with two Thunderbolt ports.  My thought was I could buy a FW800 cable and then use the FW800-Thunderbolt adaptor and it would work.  I