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. ⚠️

Catalog Sets Error

NNN634418950439932088
Hi,

First time on this forum but I've been a user since iView Media pro and really appreciate this program.

For a while now I have been experiencing a strange error. I use Catalog sets with a hierarchy to classify animal shots. The top category is Animalia and branches down to species. Recently all pictures have been tagged as Animalia, whether I like it or not, if I am not tagging them with a specific species. Previously the default position would be no tag unless I tag an animal picture.

Can anybody help me fix this bug?

Thanks

James
0

Kommentare

13 Kommentare

Datum Stimmen
  • rmoorlag
    I think you best post a support call for this one.
    Roelof
    0
  • H. Cremers
    I actually believe this is some kind of setting, if i understand you correctly.

    Somewhere, i don't recall exactly where, there is a setting to apply the whole "path" of keywords.

    If this is not the case, then i agree with Roelof, a support case is the only way to get further help.
    0
  • rmoorlag
    @HCS: I believe it's not about keywords (and their hierachy) but catalog sets and their hierachy. However, there is this setting:
    https://dl.dropboxusercontent.com/u/25580003/EM%20Sets%20and%20Subsets.JPG
    @James: Is this what you refering to?

    Roelof
    0
  • NNN634418950439932088
    Thanks for your replies. I will try to get some screenshots when I'm back home later this week.
    0
  • H. Cremers
    Ah Roelof, thanks. I didn't understand correctly then.

    Then a support ticket should help the OP.
    0
  • NNN634418950439932088
    I have taken a screen shot to help explain my bug. (So far I can't attach it to this post, how do you do that?)
    The example picture, along with all other pictures in my 16k+ library, show Animals although most are not. Only about 2.2k are tagged with any catalog set. Note total library size bottom left is 16,346 and number of items tagged Animals is 2,197, however every picture shows Animals under catalog sets.
    https://dl.dropboxusercontent.com/u/52284045/Media%20Pro%20Screen%20Shot.tiff
    0
  • rmoorlag
    You can place your screenshots in the public folder of your dropbox:
    - Rightclick the image and copy the public link.
    - Choose in the post reply the Img button and past the copied link
    0
  • NNN634418950439932088
    Thanks for the dropbox tip. The image is too large to view in the blog properly by open it in a new window and you can see everything.
    0
  • Patrick Horn
    Hello!

    I also suffer from this bug since MediaPro v1.4.1. With 1.4.0 it does NOT happen. And I found out and can reproduce this:

    – It only happens with databases created with iView MediaPro (I tested with v3.1.3 and a new database). And most or all of my daily used databases are from iViewMedia Pro ...
    – New databases created with Expression Media oder MediaPro don't have this problem.
    - Very bad: It also affects the seaching for sets, e.g. you cannot find images without sets anymore!!!
    – Tested with OS X 10.8.5 and 10.6.8.

    I will also send a support ticket with screenshots to the support ... they really should improve their testing before publishing new versions ... there are some more things with 1.4.1 which have been OK in 1.4.0 (e.g. database locking on OS X file server is back).

    A little tip for everybody how suffers from this bug:
    - Make a new set with the name "-" (or no name) and put it on top ... this will not help with searching, but the display of set names i the thumb view is much better ...
    – Or go back to v1.4.0 ...

    Here is a screenshot of the problem (made in MediaPro 1.4.1):
    http://www.horn-mueller.de/permanent_images/MediaPro_1_4_1_bug_with_sets.jpg

    Cheers!
    Patrick
    0
  • NNN634418950439932088
    That's interesting. Perhaps we just need to rebuild the database in some way? I'll look at this when I'm home again later this week.
    0
  • Patrick Horn
    I couldn't find a way to "repair" such a database. I think it must be an internal error how MediaPro is handling the hierarchical set tree. Like the support wrote me (see below) they changed something there in v1.4.1 (I'm not sure what is was) and I would say this caused a new error as a side effect – the error we are talking about here ... And because this new error only happens with originally created databases in iViewMediaPro, and that's not part of their test scenario (???), because it's too old maybe, they did not notice this error. But that's only a vague suspicion ... but I have some experiences with software testing and that's not too far away from what often happens ... That's why I wrote, they should improve their testing ...

    The only way seems to be to create a new (empty) database and import all images again (before you could do a "export annotations" with all fields for all images, which is big fun with e.g. 70k+ images ... and perhaps you don't want to have it in all your images ... so it's not the best way). I really really hope this will not stay the only way .....

    But perhaps you have an idea?

    I wrote to the support, but their first answer was that it's not a bug, but a fixed bug of 1.4.0 and that it's correct now how it is. I was very astonished. I think they did not understand the problem and I sent them now 2 MediaPro test databases, one with the error (converted from an iViewMediaPro 3.1.3 database), and one without the problem (created from scratch in MediaPro 1.4.1). There should be no doubt that there's s.th. wrong ... because the two databases show a different behaviour with exactly the same sets and images ... I wait for an answer ...
    0
  • Goldeneyes
    Did this get resolved with any of the newer versions? Sure looks like a bug that needs a fix.
    0
  • Patrick Horn
    I gave up after Oct 15, 2013, because I got the answer of the support: THIS IS NOT A BUG, BUT A FIX OF ANOTHER PROBLEM (which problem was not clear ...). This was too much for me … a little too much ignorance and arrogance. Perhaps I am too thin-skinned … sorry.

    They wrote:
    The change in 1.4.1 has been made to address the lack of that Heirachal Set being properly displayed.
    If you do not like this adjustment, that is certainly something we can take into consideration. However your subjective opinion on the change does not catagorize this as a Bug. I will certainly forward your suggestion for a change to the appropriate department.


    So they completely ignored what I wrote and sent … it was 100% reproducible.

    In v1.4.2 there was NO CHANGE AT ALL – same problem. Now (nearly 1 year after the last small update .... perfect!) we finally have v1.5.0.144 and what happened?

    The display bug seems to be fixed!!! HURRAY!

    But wait ...
    It was not fixed completely. In v1.4.1 and v1.4.2 it was not possible at all to search for items with *no set*.

    A search with „set = is empty“ or „set = is not empty“ did not work anymore, because the (incorrect) displayed sets have also logically been added to the items, so you got wrong search results – not usable results: a search „set = is empty“ never found any item and „set = is not empty“ always found all items. Perfect!

    In v1.5.0 a search for „set = is not empty“ does work correctly – finally!!! VERY VERY GOOD. But a search for „set = is empty“ DOES NOT WORK – it never finds any item (same as in v1.4.1 and v1.4.2). 🤭

    But now it’s at least possible to find items with no sets with a search „set = is not empty“ and exclude these from being displayed …

    [color=#FF0000:p4oddv1e](Please note what I wrote Oct 14, 2013 8:42 pm: It only happens with old databases created with iView MediaPro, databases created with Expression Media oder MediaPro don't have this problem. So this is only a problem for long-term users with old databases … which are too difficult to rebuild completely from scratch in MediaPro …)[/color:p4oddv1e]
    0

Post ist für Kommentare geschlossen.