Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Keywords corrupted

Kommentare

14 Kommentare

  • nancyr
    This happened to my custom fields on a major upgrade (iView 2>3, possibly EM 1>2). It would add 3-5 garbage characters at the end of the name, but was an easy fix that would not come back after saving the catalog. Haven't seen it in keywords.

    Maybe it's something similar? I'll check a couple of catalogs tonight.
    0
  • macsrock
    "but was an easy fix that would not come back after saving the catalog. "

    So are you saying that if I save the catalog it will stop corrupting my keywords?
    0
  • nancyr
    [quote="macsrock" wrote:
    So are you saying that if I save the catalog it will stop corrupting my keywords?


    No, I changed the field name by hand. Wasn't clear enough.

    Can you pull up all the images with the corrupted keywords, drag them onto the non-corrupt one, and then delete the corrupt terms? Might be a workaround for the moment. Did the corrupt keywords apply themselves to the actual images? Highly unlikely, but that could be scary!
    0
  • Dave Heap
    I too remember this happening with an iView version, but can't remember how I fixed it!
    0
  • Reeder Studios
    We've just encountered this exact same issue with one of our catalogs. (We're running Macs.)

    Created an MP1 catalog from scratch (imported images into a new empty catalog). When first created, the new catalog appeared fine, but when re-booted & opened catalog the following morning (computer was off for the night) the keywords were corrupted. Looks very similar to the image uploaded earlier in this thread - random characters tacked onto the end of duplicate keywords.

    We deleted the corrupted catalog & recreated a new one from scratch - & it did the same thing! I have double checked that the keywords have not been synced back to the actual files. Is there a hidden file somewhere that reintroduced the corrupted keywords? Or did whatever happened to cause the corruption happen twice?

    This is one of several catalogs, & the only one with this issue. Other include 1 created in the same way, & several created by opening an EM2 catalog & using Save-As to create MP1 catalog.
    0
  • Reeder Studios
    For the record, we've tried recreating the corrupted catalog from scratch again (that's at least 3 times now) and it did the same thing again. The first time it looked ok at first but then appeared corrupted the following morning; the 2nd & 3rd times it's appeared corrupted before it even finished building. Corrupted keywords are slightly different each time we recreate the catalog (different extraneous characters & different numbers of them).

    Created same catalog in EM2 last night (just to compare) & that one looks fine, so I guess we'll use that version. But how is it that MP1 can't do it right? And why only this one catalog having the problem?
    0
  • rmoorlag
    Are more people experiencing this issue besides the two in this thread?
    Only on Mac?

    Roelof
    0
  • rainerfrey
    No problem with my 2 or 3 large catalogs converted from EM2 - on Mac (OS X 10.6.7)
    0
  • Reeder Studios
    Update - I've traced our issue back to 3 individual folders of images. Everything else seems fine, but these 3 folders, when imported into a MP catalog, have corrupted keywords. When viewed through Finder and Bridge, the keywords appear as they should with no indication of corruption. Importing into an EM catalog works fine with no sign of corruption. But with MP catalog keywords appear corrupted. Cleared this issue up by creating a catalog in EM, syncing annotations back to the files, then creating a MP catalog. That MP catalog is fine, no corruption. I know we could have just used the EM catalog with a save-as conversion to a MP catalog, but we wanted to completely fix the problem if possible. Still not sure what was causing the issue, nor why only MP had the issue.
    0
  • Tom Hassing
    I've been having the same problem with corrupted keywords on a new 17" MacBook Pro running OSX 10.6.7. I cataloged several directories with Expression Media 2 without a problem. I did a sync annotations with a copyright notice to update the images. I still ended up with corrupted keywords as MediaPro slogged through the images building its own catalog. In addition, keywords were often associated with the wrong images. A keyword in the Catalog Field keyword list would often have a different image count and pull up a somewhat different set of images than the same keyword in the Hierarchical Keywords list. And finally, the catalog seems to update every time a query is made or some trivial change is made and while testing with a catalog of 17,215 images taking up 3.7GB of media space and producing a catalog that is 2.2GB in size, it took a couple minutes for each update. All in all, MediaPro is too slow and too buggy to use. I'll wait for Camera Bits.
    0
  • Jack Baty
    Same problem here. Imported maybe 5000 images into a new catalog. Lots of messed up keywords. Images were originally keyworded in Photo Mechanic and then managed in Aperature.

    I just fixed them manually, but would prefer not having to do that of course.
    0
  • This was allready mentioned just after the release of Media Pro, I don't remember the exact topic title. Anyway, I experience the same problem, since day 1, and it makes Media Pro unusable for me. I opened a supportcase, but they wanted me to do further testing on the subject, and I do not have the resources to do their testing for them. Never heard from them again, very unprofessional, IMHO.
    I did not check 1.01 , I will today, let' s hope they solved it.
    0
  • klarson
    Having the exact same problem here with Snow Leopard and MP 1.0.0.49135.
    0
  • macsrock
    Sorry forgot to update this....
    The patch worked (MP ver# 1.0.150536). No more corrupted keywords.

    I merged all of my EM2 catalogs into one MP catalog......11.1 GB catalog with 127696 images.
    So far the only problem is it occasionally opens as read only or when I save, it says it is locked. EM2 did that also.
    0

Post ist für Kommentare geschlossen.