Announcement

Collapse
No announcement yet.

Survey for catalog size

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MBangert
    replied
    I can try this if I have some spare time.

    It is best not to use cataloging images at all.

    Before ACDSee I used IDImager - this program was discontinued. These were years of lost time, now I have lost more years of my life with ACDSee with no prospect of a functional program after one year E-Mail contact with the Support.

    But there's now a great facial recognition that I don't know how to integrate it into my workflow anyway. It is nice to see what the facial recognition can do, but not more. The programme is completely useless anyway.

    Maybe at some point I will deal with the programs of real companies like Corel or Adobe and no longer ACDSee.

    At the moment I think it's the best way to simply put the images in directories on the hard drive with no Special Programm with a oneway database that could not exported or imported to another program.

    Just be careful before working with ACDSee and look for an alternative easy way!

    If you are fixed at ACDSee with no way out, please stay with Ultimate 2018. It is a stable running Programm with no limits.
    Last edited by MBangert; 11-04-2019, 11:34 PM.

    Leave a comment:


  • GusPanella
    replied
    I don't have a quick fix as I haven't experienced the same. Here is something to try....

    Starting with a new database.... >>do not<< use File > Import; instead, try the following....

    Tools > Options > ACDSee Indexer > Add Folder

    Add the folders that you would like to have indexed, check "include sub-folders" when appropriate.

    Then, click OK


    50k images may take a while. As a reference point, 150k images would probably take a day if indexed across a fast wireless network.

    Leave a comment:


  • MBangert
    replied
    Here is my current Situation with Ultimate 2020:

    Ultimate 2020 with a small database looks ok.

    Import my 50.000+ pictures.

    Entering View Mode -> Immediate crash
    Entering Develop Mode -> Immediate crash
    Entering Edit Mode -> Immediate crash
    The Map with the GPS Positions is not displayed. It shows only ?Loading?.
    The Menus on the top left do not open. (I can't believe why the menus are linked to the database ?????)

    Deleting the database and re-open Ultimate ? all is ok, because Ultimate creates a new small database

    Leave a comment:


  • MBangert
    replied
    Of course, very often. I have also created a new database by recataloging the Images. I have done all Things what the support has written. I am in contact since one year and the support has confirmed the Problem.


    Thanks for the follow up.

    Our QA team has reproduced the problem, and the bug wass entered into their Software internal tracking system. These items are reviewed and investigated for inclusion in patches, updates and future versions. Thanks for your patience.

    Regards,

    Leave a comment:


  • GusPanella
    replied
    Have you tried
    Tools > Database > Optimize Database > [check_both_options]

    Leave a comment:


  • MBangert
    replied
    The support of ACDSee has not explained the detailed Problem. This is what I have found out.

    The support is not really active to solve such a Problem, but I will not stop my e-Mailing until the Problem is solved (except where is a alternativ Programm that could read the ACDSee Keywords).

    The mystery is, that the easy ACDSee Home 2019 has no Problem. This is maybe using a different database engine.
    Last edited by MBangert; 10-31-2019, 04:37 AM.

    Leave a comment:


  • GusPanella
    replied
    Originally posted by MBangert View Post
    I have about 50.000 Pictures in my database. If I enter the Develop-Mode Ultimate 2019 and 2020 will crash.

    ...

    The support from ACDSee has confirmed this Problem for Ultimate 2019, but they have no solution.
    This is interesting. I am well over 160k images in the database without a crash. Can you share what was the reason of the fail at 50k images?

    Leave a comment:


  • MBangert
    replied
    I have about 50.000 Pictures in my database. If I enter the Develop-Mode Ultimate 2019 and 2020 will crash.

    This depends on the size of the database. With less than 15.00 Pictures in the database is Ultimate 2019 stable..

    The support from ACDSee has confirmed this Problem for Ultimate 2019, but they have no solution.

    Ultimate 2018 is working great with this 50.000 Pictures with Keywords and about 150.000 other Pictures. Currently I will stay at this Version, but what is in the future? For example with Windows 2025 ;-).

    Yes, the Programm needs several seconds for a mode switch, this should be improved.
    Last edited by MBangert; 10-29-2019, 09:37 AM.

    Leave a comment:


  • GusPanella
    replied
    I downloaded your Python script; generated a text file from an edited config.ini; created a new database; imported the text file.
    The text file was a tiny 1.8MB so you wouldn't expect any issues.

    Although I don't believe hardware is the case, it may be reasonable to rule out hardware configuration differences between the two systems. Is there a config.ini that will created a txt file large enough to duplicate the problem on your system? If yes, I could run the same config.ini. When the problem is duplicated, I think we can rule out any hardware difference between our two systems.


    Leave a comment:


  • Emil
    replied
    Originally posted by GusPanella View Post
    This is a tough one Emil.
    Yepp!

    I am guessing you've already grabbed the low hanging fruit like OS, application, cache, database on NVMe on the PCIe bus for storage....
    Yes, both apps are installed on the same physical machine. All user config is set to defaults except FR and both use the same db. AC 2020 is using a converted copy of course.

    As there is something strange going on with the database transactions and us mortals don't have access to schema, raw database, or other developer style hooks, this is a tricky problem.
    Yes, but we can bang it! So I decided to create a script to stuff the db with lots of data a see how things go. The script can be found on github. It's brand new and not yet finished, but it works; at least for me :-) I plan to do some stress tests with it and report.
    Last edited by Emil; 10-30-2019, 11:50 PM.

    Leave a comment:


  • GusPanella
    replied
    This is a tough one Emil. You've helped so many people on this forum, myself included, I certainly wish I could return the favors.

    70,000 db operations when switching between modes certainly seems excessive. I am guessing you've already grabbed the low hanging fruit like OS, application, cache, database on NVMe on the PCIe bus for storage.... database optimization and the like. Obviously, these only treat the symptom and not the root cause.

    I've read that it seems like latest versions of windows can fight a bit with VMware. If you are running in a VM instance, it may be worth trying a native Win installation.

    ‚ÄčAs there is something strange going on with the database transactions and us mortals don't have access to schema, raw database, or other developer style hooks, this is a tricky problem.

    So I get out my shotgun and look for things that could possibly cause db transactions so I can turn things off (hopefully without killing good functionality).... Not knowing anything other than trying to remove transactions, maybe one (or more) of these could help.

    Warning: I have very LOW confidence any of these will work as I am only working of guess of things that _may_ cause a transaction when switching modes.

    Options > Database > [uncheck_set_database_date_to_EXIF_date]
    Options > Database > Metadata > [uncheck_ImportExifAndIptcMeatadataFromCatalog]; in case ACD is trying to update 70000 dates for some unknown reason
    Options > Database > Metadata > [uncheck_ImportExifAndIptcMeatadataFromCatalog]; so ACD doesn't need to link IPTX/EXIF to the datalog
    Options > Database > IPTC COnflicts > [uncheck_both_of these_so_ACD_has no_reason_to double_check_anything]
    Options > View Mode > uncheck_ACDQuickView; in case it is the quickview that triggers a bunch of transactions ( I have had problems with QuickView, so I tend to disable it anyway)
    Options > ACDSee Pica view > disable; in case it is this feature that wants to reload keywords for some strange reason

    Leave a comment:


  • Emil
    replied
    You're right Gus shooting indian summer photos is much more fun then debugging a poorly maintained app. But I also have to run AC several hours a day, as it helps me to make a living!

    I actually don't really need the AC-keywords. As you, I'm fine with the IPTC-keywords. The 9,000 existing AC-keywords are just many years old remains. But what am I going to do if ACDSystems decides to foul the handling of IPTC meta data too? So, I keep on digging and post what I find. Perhaps someone becomes smart of it . . .

    I wonder why AC does actually need to read all AC-keywords from the db just to show a single image w/o any assigned keyword in view mode.
    Last edited by Emil; 10-10-2019, 02:09 AM.

    Leave a comment:


  • GusPanella
    replied
    I may be able to help confirm somethings to help you get out and take pictures of the fall colors instead of troubleshooting AC databases.

    I have no where near 9000 keywords. Actually, I have zero AC-Keywords. I may have 400 IPTC Keywords at most. Maybe you are on to something with that keyword test. I would expect 9000 items should be a quick read/sort for a modern database. Preferably one that could operate off of a standalone database. Maybe v2021 will have an updated back-end.

    (I also have FR turned off.)

    Leave a comment:


  • Emil
    replied
    Hi Ben,
    Thanks for the suggestion but this doesn't help. I did even more than that and removed "HKCU\ACD Systems" to have everything reset with one exception: I disabled FR which was eating up my CPU.

    As one of the first steps I compared accesses to files and registry with "Process Monitor" and found that AC Pro 8 needs 4 "ReadFile" operations for Keywords.dbf and Keywords.cdx, while AC Ulti 2020 needs over 70,000 operations when switching from manage mode to view mode. A closer look also tells that AC reads the same portion several times.

    Both installations are as identical as possible: (almost) identical DBs and default user settings. Both dBs contain 9,000 different AC-keywords, but none is assigned to the selected image.

    For a short test I replaced Keyword.cdx and Keyword.dbf with copies from a fresh and empty db. With this the change a mode switch takes less then 3 seconds. But this of course isn't a solution; I need the keywords. So I'll keep on drilling :-)

    Leave a comment:


  • Ben_H
    replied
    Hi Emil,
    Have you tried resetting your layout? In Manage mode, View | Reset Layout, there were a couple of people on the forum saying that improved their mode switching performance.

    Leave a comment:

Working...
X