I recently noticed that in some of my photos, the album is not displaying all of the face regions defined for a photo. I'm using jAlbum v20 and Tiger 2.13.6. I've created a single-image test album at http://www.zeleznik-klein.com/facetest/html/index.html to illustrate the problem. The album also includes the image's metadata that I exported using exiv2. The photo in question has 21 regions defined and these all display correctly in jAlbum when I right click and select "Set area tags". So jAlbum "sees" all 21 regions, but only 6 are getting output to the album. Indeed when I look at data1.json, there are only 6 regions listed in
If you refresh the album in your browser, I added a download-originals option to the album. BTW, I think I may have spotted the problem. I have several face regions that are currently unnamed and it looks like maybe data1.json stops generating regions when it hits the first region without a name? This is very common in Lightroom which will auto-detect faces, but many will remain unnamed.
It seems the names weren't simply empty, but were completely missing from those face tags. I thought that was a complimentary part of a face tag. Now I modified the code so it checks only the x coordinate. Hopefully that's always present
Nagyon köszönöm! I went back to some old photos processed with earlier versions of lightroom and this seems to be a long-standing behavior when LR has detected face regions that remain unidentified. Having used jAlbum and LR together for over 10 years, hard to believe I only noticed this recently. I will definitely rebuild all my albums once you push out the fix.
Am I missing something? I still see that the last update to Tiger was v2.13.6 released on April 3 over 6 months ago: https://jalbum.net/en/skins/skin/Tiger. This is the same version that I reported the problem on. I also don't see any skin upgrade notification within jAlbum. Have there been Tiger updates that I have somehow missed? Thanks!
I apologize, but I don't quite understand your question. In the previous version of Tiger (ie. 2.13.6) the face regions were iteratively parsed from the metadata until a name did not exist. Therefore, by definition all the face regions that were successfully parsed had names and were displayed in the lightbox. The flaw was that in a mix of named and unnamed regions, any named regions that followed the first unnamed region were skipped.
In the updated util.js, face regions are parsed from the metadata until an x-coord is not found. The region are pushed onto the "sb" array and are displayed in the lightbox whether or not a name is parsed for the region. The result is that unnamed regions are displayed with blank labels. I was asking if it was possible to skip pushing an unnamed region onto "sb" and being displayed, not to stop parsing all region metadata at this point since there may be named regions that follow. Since I don't think displaying regions with blank labels was a possible use case before, I am not sure how my request would break backward compatibility. But if it does, maybe my requested behavior could be enabled via a variable.
I hope I am clear on how my request is not the same as the previous behavior, thanks!
...I was asking if it was possible to skip pushing an unnamed region onto "sb" and being displayed, not to stop parsing all region metadata at this point since there may be named regions that follow. Since I don't think displaying regions with blank labels was a possible use case before, I am not sure how my request would break backward compatibility. But if it does, maybe my requested behavior could be enabled via a variable.
I added region support, based on Laza's original code, to one of my skins. When I saw this post I updated my code to give the option of including, or not, un-named regions. My thought was that some users might like other (family?) people to look and possibly identify those unknowns. I made it so if unknowns were included they were identified as unknown, but with sequential identifier numbers.