![]() It would imply that you cannot do a search in PSu using a space? Almost all of my keywords have spaces, some include hyphens. Even if these are used regularly in SQLite search statements good programming should take care of that. #Photo supreme hangs up verifying folders windowsI have no idea why deleting a folder or files would not be just as snappy inside PSu as inside Windows File Explorer - both are, after all, only databases of the file system.īesides, I doubt that using hyphens or spaces should have an impact. So, this is clearly a PSu database problem. Even if I delete folders and files on the hard drive using Windows File Explorer, deleting them from PSu is still extremely slow. Ironically it does not even matter if these folders still exist on the hard drive. It is excruciatingly slow, if the images have been deleted. Įven though I am not using spaces " " or hyphens "-" and even though I never ran into problems deleting a file, in myexperience deleting folders is a REAL pain! It doesn't work at all, if the folder still contains images. For my folders I also use underscores "_" instead of hyphens "-", e.g., "2010_11_12". I have not experienced any problems deleting files and ALL my file names have underscores "_" as part of the file names, e.g., "PX_1254.jpg". It is about deleting images (and folders). Maybe by then Adobe will support custom metadata in some form or other.This is not about searching. But that could be several years from now. Netting it out, if I want to induce others to adopt my custom XMP I will probably have to write some sort of Lightroom plug-in. I've worked with MS Access, as well as most of the MS Office applications, and I don't like Access. In the meantime, to capture custom metadata I'm going to use Photo Supreme. Only then can I consider writing Lightroom plug-ins. I probably have the skills to learn Lua, but first I have to cull/catalog about 15K digital images and scan/catalog about 20K Kodachrome slides and about 4K B&W negatives. Not even to allow a plug-in to add custom metadata fields. That all said, I am very disappointed that Adobe, which after all, invented XMP, hasn't done more with it. For this hobby, photography serves for documentation, and details, lots of them, count. #Photo supreme hangs up verifying folders how toI worked at Sun Microsystems during the heady days of Java rollouts, and I have an idea of how to get "my" community (a hobby interest) to accept the idea of custom metadata. I fully understand the "community acceptance" issues. I was hoping they would respond to my post.Ībout custom metadata. I guess those people aren't currently active on the board. I know that people use both Photo Supreme and IDimager because I've done searches on the names of these applications and found a bunch of postings in this forum that include these application names in their posts. I might have developed an Access or VB front end too, but I preferred the excruciating torture of learning Lua (OK, I learnt far more than I needed). No one seems to use those two apps you mention, and in general few Lr users use a second cataloguing app. Unfortunately they don't store data in classic relational tables but dump chunks of Lua text that you'd need to parse. The catalogue needs to be closed (single user access) and it would still be difficult to use Lightroom-entered data effectively. For example, you could create a database application in Ms Access to contain your custom data and build nice UIs, connecting to a Lightroom catalogue via the open source ODBC driver. Fine if you like putting data into a silo - let's hope you don't want to get it out of there!Ī similar approach is to use ODBC. But the trouble with custom xmp is no-one else knows it's there, and few apps ever allow you to read or display it in their own UI. I haven't looked at Bridge's File Info panels for a few years, but it might be easier to extend those, if you are determined to have custom xmp fields. One advantage is that it would be in-Lightroom, so you can take advantage of the metadata filter and smart collections, as well as the obvious benefit of only needing to know or workaround two apps' quirks. From our discussions you are probably in that group, but I think you'd be better rewarded off with the other route of creating your own plugin. You can make such processes work if you are disciplined and understand xmp metadata. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |