![]() Even better, if at some time in the past you embedded the metadata in the dropped files, then that now re-populates the database. If, for some reason, there were some folders that you dropped from the old database, this information won’t be on the new database, but it could be if you manually catalog those folders or ACDSee automatically catalogs them when they are referenced. If your old database was good and in sync with all your images, converting your old database will get you where you want to be. One is: Tools | Metadata | Embed ACDSee Metadata. ![]() There are several ways to embed metadata. ![]() While some metadata may get stored on the file – I haven’t bothered to do a lot of research on which is stored and which not – the proprietary ACDSee data is ONLY in the database UNTIL and UNLESS you embed it back into the image file or sidecar file. When you add ACDSee metadata (category, keyword, label etc.) to an image, this is stored in the database. Now ACDSee can do magic with all this data very quickly, because it is reading well organized data in a database, not hunting around, opening image files one at a time. Cataloging is copying meta-data in the file and the. ACDSee “catalogs” any folder initially specified, and then any folder you browse to later. Here’s my understanding of how the database works. Now your database is no longer empty! Database background Tell it about one insignificant folder to keep it happy, and then go to Tools | database | Convert database and follow the wizard to convert your old DB. I think what would normally happen would be that ACDSee (after asking which folders you want to include) starts to catalog everything in those folders. That’s because you’re using an empty database. This is the part of the install process where there is a moment of panic, because none of your keywords, categories, options and so on are there. However, if you move some folders or images in one version, you’ll create orphans in the other version, so by all means keep the old version for reference, but I wouldn’t DO anything with the old one unless you are clear about what the implications are. You can run both (new and old) versions independently. (But if you don’t have a regular backup routine, I’d do a total backup before that install, as a normal precaution.) Any previous versions, databases, registry settings etc. You download a file (for pre-purchase, there is an email to tell you it’s ready) and when that’s run, it downloads the rest and sets up a default installation. That’s a great deal, but you have to wait a while for the new features, and if you buy that deal, it doesn’t qualify for an upgrade price. Then there are the summer package deals, which are best if you want to have multiple copies and/or multiple products (like Gemstone). The flaw in my plan is that I almost always do. My theory is that I can choose each year whether to do it or not. The next is to pre-purchase in September. I’m not sure what happens if you stop subscribing. The absolute cheapest way is to subscribe to an annual plan – so long as you want to upgrade every year. You know, if people find it’s a pain in the butt, maybe they won’t upgrade as often. I’m writing this with two hopes in mind: to help others get their upgrade done more easily, and to suggest that ACDSee developers pay some attention to the upgrade process. I’ve just upgraded to ACDSee Photo Studio Ultimate 2023 and then needed probably a couple of hours of experimenting, updating my documentation and manual re-entry to get to what I hope is an installation that is customized the way I like it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |