Known Participant

Question

Problems with 2020 Facial Recognition

Forum|Forum|6 years ago
January 4, 2020
12 replies
3972 views

I too have the issue of Elements 2020 not running facial recognition since it converted my Elements 2015 catalog. It does NOT show "Analysing Faces" in the lower right corner and is not using CPU or Disk while sitting idle in the People tab. Facial tags were not done in Elements 15, so I expected the program to be busy tagging all my videos. Natta!!! I deleted some photos from the catalog, while leaving the files in place in My Pictures folder on disk. It did not retag the photos. So even photo tagging is not being done anymore.

As I said, my prior version Elements 15 didn't do video tagging. Also, I didn't have Premiere Elements 15 installed. So with both Photoshop & Premiere Elements 2020 installed, I decided to delete all videos from the catalog, again while leaving in place on the disk, then reimporting. Still no facial tagging. Nadda!!! It just says "Adobe Catalog" in lower right corner. No CPU and no disk access.

The Preferences are set for both Video and Photo for both People View and Smart Tagging. I have tried turning them off, rebooting, turning them back on, rebooting. I don't want to click the reset recognition data button because I have about 42,000 photos tagged.

I noticed that I have 2 json folders. One in the catalogs folder and another under facial recognition. Many of the json files, dating all the way back to 2016, have 2 bytes. The contents are curly brackets like these:{} Also, it would appear that the Organizer touches them because my Sync.com backup software uploads updated Date Accessed (the files I looked at stayed 2 bytes).

Any suggestions on what log to look in to see why it is not doing analysis would be appreciated.
Thanks

[Message moved and edited by Moderator]

This topic has been closed for replies.

Greg_S.

Community Expert

Charles, I have been contacted by Adobe about your problem. The patch files given to Bill were for a specific problem that only affects a limited number of users. The recommendattion is that you uninstall the program and all of the patch files that were shared with you by Bill. (When you uninstall, there should be an option to remove settings or preferences. Click yes or OK.)

Reinstall the program and if you are still facing the same issues, contact chat support through the Contact Us button on the Adobe.com>Support menu page. They are supposed to gather the auto-analysis logs from you and supply you with assistance based on the log analysis. If you don't get the necessary help, come back here and I will do what I can to escalate it again.

CharlesSBanks

Known Participant

Greg,

For what it is worth, my faith in you has been restored and I really appreciate all the help you have provided. With Adobe and their products I am back to my original feelings. It really bothers me that no one from Adobe would contact and/or work with me directly on this issue. It seems like they would not contact Bill either, only sent him the patches. When I originally had issues back in December I chated with technical support before coming here. The first two attempts I waited over 30 minutes before giving up. When I finally got someone we spent over 45 minutes going over everything I could have possibly done wrong. That is why I was so frustrated by the time I got here. A month later there is still a problem with Elements 2020 and they sent a patch which they claim is only for a "specific" problem that affects "a limited number of users". Please put yourself in my shoes and tell me honestly how you would feel.

Here is what I have done in hopes of being able to talk with someone at Adobe about this issue. I went back and individually restored all patched files. What I found was there was an issue with FaceAnalyzer.dll. After I restored that file elements no longer crashed but my original problem remained. I went ahead and deleted the coverted catalog and un-installed 2020. I then went ahead and re-installed 2020, applied all patches but the FaceAnalyzer.dll and converted my 2019 catalog again. This time after I converted my catalog I saw facial reconizion working, which took about 15 minutes (this did not take place without patching). After that I went into some photos I had not identified and they all had "add name". I could also add a face to one photo. As one last attempt I replaced the FaceAnalyzer.dll and went back into orginizer which did not crash. However, I still am not getting "Is this Charles Banks". In comparision, all of the photos in 2019 come up with "is this Charles Banks". I did all of this with the hope that my work on this would help a technical support rep. understand more about the issue. If I had been contacted I would have more than happy to continue to work on this issue but for now I am done. I am going to un-install 2020 and try to figure out how to get rid of the (how did Bill put it?) crap that is left behind. I will stay with 2019 for now and decide later. Thanks again for your help.

Charles

Greg_S.

Community Expert

Charles said

Is FR simply that the application knows that there is a face in a photo (add name) or is it actually that it possibly matches a face that has already been named (Is this Charles Banks?). At what point is the JSON file created?

FR not only finds faces but also matches them to faces of the same person which it has found in other photos. That is why you have stacks of multiple photos in the UnNamed People room. The program tries to group faces of the same person in a single stack. So, rather than adding the same name multiple times in the main grid, you can view all of the faces of the same person in a stack and add their name just once. This may not work for you since you apparently require the original photo containing the names in order to identify the people in your scanned files. But, if you select the Media link underneath a face in the UnNamed People room, and then double-click an image thumbnail, all images will appear in a grid (with details) which can be zoomed to help you to identify the image(s) in which the face appears:

Once a found face has been named, the Add Name text box will offer suggestions of who the person is which can cut down on typing. The more photos that have a name of the same person identified, the more accurate the stacks become. But, as I understand it, when you add a photo to the catalog, the FR analysis reviews all previously identified faces for comparison to determine whether the image contains a face that has already been named or is in an UnNamed face stack. On a large catalog, this increases the time for analysis.

The .json file is created as soon as the file has been analyzed. I believe it contains the pixel coordinates of the faces that have been found in the image, and presumably some database information to link it to previously found faces. I'm not sure whether the .json file is updated when a name is added to a face or whether that information is stored in the catalog database itself.

Charles said:

I also want to let you know that I realized something that was missed by me. There are 51 people with names but each one of these people has anywhere from 1 to 70 photos. This brings me to about 447 photos that I have added names to the faces. Even with the number of un-named photos I have this makes me feel better about what I have done. I know you said something about that before but it just now clicked.

I suspected something like this. That's why I was persisting in asking you questions. 😉 I hope my points above will also assist you in understanding the features of the UnNamed People room.

Charles said:

So I applied the fix and now my 2020 Elements keeps crashing. About 20 seconds after opening I get a crash report. Two items to note: 1. I can still move around in Orginizer as long as i don't close the crash report and 2. I can open any photo except for the last one I imported which did not have a reconized face.

Not sure where to go from here.

Did you complete the details of the Adobe Crash Reporter as to what you were doing at the time of the crash? The Adobe team does look at these crash reports. If you have done everything that Bill has suggested with respect to the patch files, I think I would go back to the original files. My other suggestion would be to go through the UnNamed People stacks and see if you can Add Names there. It may well be that, after you go through that process, you will find that FR is working as expected.

Bill said:

Beware that a male with short hair, a black man with afro, a female with long hair, and my 39 year old friend April, and another friend's 6 year old son make be considered the same person. Here I click on the stack with the most faces, identify the face of the person that seems the most numerous in the pics, then select all the other faces or objects and click either Not this person or if the face is a bicycle, door knob, or someone I don't know i click Don't show again.

As I have said, and Bill confirms, FR is not perfect and you can get some really strange results. But, the AI behind face recognition has improved with each version, and the more you use it the better it gets.

Bill said:

When I get tired of doing that, I will go to the Named tab and look for names that have a blue triangle with an exclamation mark in them. Clicking on those it will offer Confirmed Faces at the top and unconformed at the bottom. This is Element's attempt put a name to the face. I Confirm those that are that person, clicking Media to see the face in context if necessary to be sure. Then use Not this Person, Rename (if there are a bunch of faces of the same person), or Don't show again for dogs & cats or another picture of Elvis that I had asked not to show again.

This is all good advice for using FR. (But I add names to the pets in my photos. 😁)

CharlesSBanks

Known Participant

On all of the files which needed to be replaced I renamed the extension with '.org' then copied the new file. On the etc folder I performed a cut and paste to delete the folder and put it in a different folder as a backup. Once the patching was done I rebooted my computer. I did remove the ‘frsdk-9.4.0.dll’ from the folder. I did not stop Elements Auto Creation 2020 prior to making the changes. On the crash report I stated I was working with Greg S. from the Adobe Support Group on an issue with FR in 2020. Also, that there was a patch sent out which I had applied.

Thanks for the explainations Greg. With my Elements 2019 FR was working great and apparently very quickly. As I said I have photos of my great great grandfather as a young man. When I would import another photo of him typically by the time I would open the photo from the grid I would have "Is this Simon P. Meyers" when I hovered over the face. Yes, at times I may be asked if it was the wrong person, but most photos would at least offer a name. When I started working with 2020 this time, every photo I added simply had 'add name'. I even scanned a couple of photos that were already in the cataloge.

The reason I add names from the grid is a matter of procedure because I don't always reconize my ancesters. I inherted thousands of photos from my parents and in-laws. I have been cataloging them for over a year now. Only photos with information on them are scanned and then I store them in specific places. So my procedure is to scan several photos at a time and place them on my desk. After doing a batch of photos, I go into Elements which presents me with a grid of imported photos. One by one I go through them, identify the person(s), change the date and update information. I don't think I could name half the people in my unNamed stack without the actual photo. Even though I have other catalogs with actual photos, I have not worked this much with FR with them yet. Now you can really understand why loosing this catalog and starting over is not an option. The resolution with 2020 has to be that I can bring my catalog over and keep working. If there is an issue with it that is preventing this, then I would like to understand why before making a decision that it cannot be converted (ever).

Thanks for moving the other messages and cleaning this up. I was not sure how to go about starting a new thread while maintaining this information. My plan for now is to keep working in 2019 but leave 2020 as is. That way, we can still work on this issue without impacting my work. I did create a new catalog in 2020 but it continues to crash.

Bill, I really liked you comments and understand what you are saying. Glad we all have some humor about this and I like the idea of naming pets. Thanks for you input on this.

Greg_S.

Community Expert

Thanks for responding to my questions, Charles. I will now try to get somebody from the Adobe staff to contact you.

I know you don't want to be a beta tester for the program but, in the meantime, I see no harm in using the hotfix files that were given to Bill. I have no idea if or when an official update will be released, but when it is, you may have to uninstall/reinstall the program in order to get the latest updated files on your system.

Before applying the hotfix, I suggest you make a full backup of your catalog.

Also, because this thread is so long and contains a mix of issues, it would be helpful if you started a new thread summarizing your problems, and providing the details of your workflow, and everything you have attempted to fix the problem. That way, the Adobe staff can focus on your issue.

To answer your question about the .json files, I agree that when deleting files from the catalog, the .json file should also be deleted. I will report this issue to Adobe. However, I think it would probably be a very low priority bug that doesn't really affect users, so I would not expect a fix until a later version of the program.

With respect to your question about the catalog Repair, when you received the message that there were no errors found, did you proceed with the repair? If not, it is something you can try. And if you didn't Optimize the catalog, you can try that also.

Since it is the start of the weekend, it may take a few days for Adobe to contact you. Hang in there. And please let us know if the hotfix works for you.

billj2029259Author

Known Participant

If you save the original etc directory (i.e. rename etc.old, rename frsdk-9.4.2.dll to frsdk-9.4.2.dll.old, and delete FaceAnalyzer.dll before you do a future update then you shouldn't have to reinstall.

Elements saves off a copy of your old catalog before it does conversion. But it is a good idea to copy the entire directory (json/waldo directories, and all the files in the directory of the catalog) before doing a conversion. I also make a copy of that entire directory every now and then in case corruption occurs it gives me a recovery set.

Having gone thru the registry and seen all the junk that Elements leaves behind, it would not surprise me that deleting photos/videos doesn't cause the json files to be deleted. But like Greg said it does little harm (just waste disk space if you delete a lot of files. That is why I put all my stuff into a directory of stuff to import so that I can go thru and delete the crap before doing an actual import.

Do you still have the link to the files needed for the patch?

Greg_S.

Community Expert

Thanks for the additional information, Bill. I didn't mean to suggest that the hotfix did nothing for you. It sounds like it removed a process blockage or sped up the analysis. Hopefully, that fix will be distributed in an update soon.

Greg_S.

Community Expert

Charles, I have heard back from the development team and they have told me that the issue has nothing to do with the Win 10 Pro environment. As I understand it, Bill's problem with Video FR was solved by leaving the machine idle for some (lengthy) time. Perhaps Bill can comment further on that.

I am asking for further clarification, but I don't think that the 2020 update that rolled out on/about Jan. 13 included any of the hotfix files that Bill received.

Charles said:

Bill suggested I try to re-convert my current 2019 catlog to 2020 which I did. Both of these catlogs show the same numbers which are: 453 media files; 508 files in the JSON folder; 5 files were created after I performed the conversion.

What this suggests to me is that you have deleted some files from the catalog that have already been face recognized. I don't think there should be more .json files than media files. If that is the case, there may be some corruption in the database. In any event, the fact that new files have been created certainly indicates that FR is being performed on the catalog.

Charles said:

What is bothering me is I have 360 people in the UnNamed stack and only 51 in the named.

This means that only 51 people have been named by you via the face recognition tools. While it wouldn't matter if you attached a name to a face via the UnNamed People room or via your preference of naming someone in the grid, I would like you to confirm that you have not named people in your photos by simply dragging a People name tag from the keyword tag hierarchy to the image (or vice versa). If you have named a person in the grid via the Add Name text box, that person will appear in a stack in the Named People room and the photo will be removed from any stack in the UnNamed People room. If you have only added a People tag to the photo in the grid, the name should appear in the Named People room but the photo will be identified with a generic icon, not the face of the person. Similarly, if FR has recognized the face, the photo will remain in a stack in the UnNamed People room because the tag has not been associated with a face.

Charles said:

I do have People Recognition turned on in the view menu but with the old cataloge no circle with Add Name text box comes up. On an image that was already there I was able to search for an existing name.

Are you talking about what is happening with your converted (old) catalog in EO 2020?

What kind of search are you talking about? A search could be revealing results from the name of the photo itself, not just a People tag. (As I understand your previous response, you add names to photos that you have scanned so you can easily name the person in the grid when the face has been recognized by FR.)

Charles said:
Once you add a name, would there be any way for the system to drop it? Also, when you convert a catalog does it affect the original one? I see that it renames the original folder by placing a 1 at the end and I was surprised that when I opened 2019 back up it knew about the renamed folder. I now have "Ancestry" and "Ancestry1" 2020 & 2019.

Names can be deleted from a catalog only by affirmative action of the user. Converting a catalog has no effect on the original. Essentially, it becomes a backup catalog. A catalog can also be converted more than once. So, if my above responses have not led you closer to a solution of your problem, you could repair and optimize your (old) catalog in the Elements 2019 Manage Catalogs dialog, and then convert it again in Elements 2020.

If you are still having problems, I will try to get the development team to contact you.

billj2029259Author

Known Participant

Greg, before the patch I left my PC up with Elements Organizer open, and screen timeout/lock set to never so that it could work nonstop and it found NONE of my over 2,000 faces given about a week to process. (Before going to the Unnamed Tab, go to the media tab and use the Media Type item on the View menu to show only videos. Then only unnamed Videos appear.)

That is when I set up a test bed of only a few videos. After many hours there was FR in only one of the test videos. After the patch it took only minutes to find faces in other videos in the test bed. I then reloaded my full catalog and it went right to work within minutes recognizing faces in videos. I mean within minutes it had recognized quite a few faces. To finish did take quite some time because I had 2,463 videos.

So, I would not agree the patch does nothing (afterall, why would they have a patch that does nothing? The placebo patch? lol). Also, I thought he said the patch was to fix something that changed in version 1909. That yours works in 1909 does not mean there is not a bug that would keep it from working for others (for example when windows is installed it installs tons of drivers that are specific to the motherboard, GPU, & CPU).

Greg_S.

Community Expert

OK, Charles, I have reviewed your responses. Before making any other suggestions, I would like you to look in the JSON folder at this location on your computer: C:\ProgramData\Adobe\Elements Organizer\Catalogs\[Your Catalog Name]\FaceAnalysis\json. Sort the folder by Date Created and see whether the most recent date of the files is after you added new files to your old catalog. If it is, then I believe face recognition is actively working.

One other thing to look at is how many files are in the json catalog? How does this number compare with the total number of media files in your catalog shown in the left side of the status bar in the grid? The status bar only displays the number of files that are visible in the grid. So, to get a more accurate count, expand all stacks in the View menu and also Show All Files in the View>Hidden Files menu.

I have asked the development team about whether the recent update of 2020 included the files given to Bill. I suggest you wait for a response before installing the files that he received.

I agree that you should not have to start a new catalog for FR to work. I am reasonably confident that we will be able to get this working for you. In the meantime, I recommend that you name the People stacks in the UnNamed People room, rather than individulally in the grid. I find it to be a more efficient process. You should also look at the last few stacks in the UnNamed People room. It should display the catalog's most recently added media (but not necessarily if the faces have been grouped in a stack with earlier found faces). BTW, I haven't yet asked how many stacks you have in the UnNamed People room? The number can be found in the lower left status bar. If you had UnNamed stacks in your 2019 catalog, I believe they would be carried over to 2020 when the catalog was converted.

CharlesSBanks

Known Participant

Digging into everything I may have more issues then I realize. The catalog which I converted back in December only had 347 files in the JSON Folder. The oldest date is 11/23/19 which was about two weeks before I updated. There were only 305 media files.

What is bothering me is I have 360 people in the UnNamed stack and only 51 in the named. As I have said, this catlog contains scan photos of my family and that of my husband's. Typically, what I have always done is scan a group of photos, named the file according to who is in the photo and date. Then copy the photos to my ancestry folder that is setup as a watch folder. Once that is done I would go into the organizer and update the information. This included identifing the people in the photo with FR. This is why I was doing it from the grid and and the UnNamed Stack. What I was impressed with is the system would reconize a majority of faces that had already been added; "Is this Charles S. Banks?" On new faces I would already have the information on who it was and would just enter while i was working on the photo. I am now blind-sided that I have so many unNamed faces, some of which I swear I know I added names.

Once you add a name, would there be any way for the system to drop it? Also, when you convert a catalog does it affect the original one? I see that it renames the original folder by placing a 1 at the end and I was surprised that when I opened 2019 back up it knew about the renamed folder. I now have "Ancestry" and "Ancestry1" 2020 & 2019.

Greg_S.

Community Expert

Of the 2370 videos in my library it is now processing 2329 videos

I think I have previously mentioned that analysis will not take place on videos that are 5 seconds or less, or that are longer than 15 minutes. If you have any iPhone live photos that are mov files, they will not be analyzed because they are under 5 seconds.

CharlesSBanks

Known Participant

Greg,

The focus of this conversation has been on facial recognition with video files. One item that came out of this was that there was a common factor surrounding facial reconition issues with at least two people. That factor was having an OS of Windows 10 Pro. We have not heard back from Bill if his issue has been resolved or not but even so, he was sent a patch which got him at least partially working.

We never got as far as to try a patch for my issue, which I am willing to take responsibilty because I got upset with things. What I would like to explore, now, is two-fold: Do we know if that patch will become a fix in a future update? How do I (we) let Adobe know that there may be an issue with Windows 10 Pro and functions of Elements. This isn't the only issue I have had with other versions and I would like to know how to move forward. If there is an issue, then what happens if I update to 2020 and facial recognition dosen't work still?

Thanks

Charles

Greg_S.

Community Expert

As I understand it, Bill had no problems with Facial Recognition on photos, even with his Windows 10 Pro machine. Shortly after Bill received the hotfix from the developers, Elements 2020 was updated. It is not clear to me whether the files sent to Bill were included in the update patch. I will try to find out the status of this issue.

Greg_S.

Community Expert

I have passed this information on to the developers. Win 10 Pro certainly looks to be a leading candidate as a source of the problem. Hopefully, we will get a response from the developers in the next couple of days.

billj2029259Author

Known Participant

Thanks Greg. It would appear that Win 10 version 1909 broke facial recognition for video. Tech support provided a zip file with several changed files and a folder to replace an existing folder (they said it would be released in an upcoming patch).

However, that did not fix the problem for me. Ironically, before I applied the fix Organizer finally analyzed 1 of my 4 videos after several days of running (15 MB file). After I applied the fix it analyzed another video (8 MB) but not the other 2 (68 and 79 MB). I added a 3 more videos to the test bed which my friend's laptop quickly analyzed. Not so much on my Win 10 Pro with the supposed patch. I created a new catalog yesterday to see if maybe the fix needs a fresh catalog to work properly. NONE of the videos have been analyzed even though I left my computer up and logged in overnight.

While waiting on tech support to call back, I am going to uninstall Elements then apply the fix before 1st launch. Then see if that helps.

CharlesSBanks

Known Participant

Bill,

I understand that you are working with videos but I'm curious if you have tried facial recognition for photos? Did you talk with tech. support or did they just send you the files because of Greg contacting them.

Greg_S.

Community Expert

I agree with your assessment of the log file. It is possible that there are some corrupt video files that are hindering the process.

Can you try a new test catalog with just a few mp4 files in it. They are less likely to cause problems than tape-originated files (and use different mp4 files than your other test catalog.

I will try to get the attention of the development team to figure out this issue. Because of time zone differences, it may take a few days for them to get back to you, so please be patient.

billj2029259Author

Known Participant

Thanks Greg. Really appreciate the help. I installed Premiere and the test files on a friend's laptop. After 10 minutes it dutifully went to work and did facial recognition on the video files. So the test video files are Ok. The friend runs Windows 10 whereas I run Windows 10 Pro. Wonder if that could be a factor.

I uninstalled everything Adobe (including reader), ran AVG Tuneup on the system (including registry), manually deleted all the Adobe related entries (excluding, of course, the fonts), and ran Tuneup again. Still doesn't do video tagging on my desktop PC.

Looking forward to finding a way to increase log level. Hopefully, it is just editing something like a Java LogManager properties file to read DEBUG or ERROR instead of INFO.

CharlesSBanks

Known Participant

Bill,

Since I could never get facial reconizition working I was thinking of asking you if you think it could be something with the environment. I am also running Windows 10 PRO, version 1909 on an HP Pavilon Laptop. It is a x64 i7 processor with 16gig. of memory.

Greg_S.

Community Expert

One more thing to try: Filter the grid to just videos by hitting Ctrl+1. This will remove all photos from view.

You asked about the log files. I think the one to look out for is found at C:\users\[name]\AppData\Roaming\Adobe\Elements Organizer\18.0\Organizer\Log.txt. If you can, click and drag it to a post here and I will forward it to the engineering team.

Yes, it would be a good idea to create a new test catalog and add just a few video files to see what happens.

One factor I haven't mentioned before is that video analysis only occurs for videos that are more than 5 seconds and less than 15 minutes duration. Given the variety of video files you have I doubt whether this is an issue for you.

billj2029259Author

Known Participant

Hi Greg. Thanks for the log location. I uninstalled and reinstalled Elements and used a test directory with a m2ts, 4 mp4, 3 mts, a mov, a wmv, and an avi. Nadda. Didn't do any facial recognition. Then I remember the other guy saying he still had an earlier version of Elements installed. So, I uninstalled both Elements 15 and Elements 2019. Adobe left quite a bit behind, so I deleted the directoris in Program Files and ProgramData. I then saw your message about the log location. At this point there was no directory called Organizer in the C:\users\[name]\AppData\Roaming\Adobe\Elements Organizer\18.0\ directory. Suspect that was one of the things the uninstaller removed. There was an empty logs directory. There also was a Elements Home\Logs directory. But the only file was ElementsHubPRELog.txt that contained only the following single line:
[20200104T123116] Error :EliveDataDownload:HbEliveDataManager: Elive cards are not Fetched

I went ahead and renamed the ..\Roaming\Adobe\Elements Organizer to end with .old before reinsalling Elements. This time I only installed Premiere Elements. It is apparent the Adobe Uninstaller also didn't clean out the registry because even with all the Adobe directories deleted or renamed, the first launch after installation it popped up with The 'My Catalog' catalof could not be found. Please open or create a different catalog. Anyhow, I let it create its catalog in its default location (ProgramData directory). Again, nothing gets tagged. 0% CPU and disk drive.

Now there is an Organizer directory with a log file in it. Here is the contents. It didn't log much. Do you know if there is a setting somewhere to enable debug logging? Thanks.
0 Elements Organizer 18.0.0.0 Log (5) started 2020-01-04 23:02:28.516
[20200104T230228] 0 (+ 0) Windows OS Version as reported by Qt: 0xc0
[20200104T230228] 0 (+ 0) Desktop Resolution: 3840 x 2160 Depth: 32
[20200104T230229] 533 (+ 533) Begin AMT Library calls
[20200104T230229] 885 (+ 352) End AMT Library calls
[20200104T230229] 959 (+ 74) problem opening C:\Users\willi\AppData\Roaming\Adobe\Elements Organizer\18.0\Organizer\status.dat for reading, maintaining default values
[20200104T230229] 960 (+ 1) BEGIN PtAppPreferences -> load()...
[20200104T230229] 978 (+ 18) PtAppPreferences::setDefaults m_strRevelDownloadFolder=C:\Users\willi\OneDrive\Pictures\Adobe
[20200104T230229] 978 (+ 0) Error loading .prf(preferences) file
[20200104T230229] 978 (+ 0) PtAppPreferences::load m_strRevelDownloadFolder=C:\Users\willi\OneDrive\Pictures\Adobe
[20200104T230229] 978 (+ 0) PtAppPreferences -> load() :: PRE installed only
[20200104T230229] 978 (+ 0) END PtAppPreferences -> load()
[20200104T230229] 984 (+ 6) Primary Font: Tahoma
[20200104T230229] 984 (+ 0) Loading Bitmaps...
[20200104T230232] 3813 (+2829) Loading Components...
[20200104T230232] 3813 (+ 0) Initializing BIB Host...
[20200104T230232] 3814 (+ 1) Initializing Bravo Components...
[20200104T230232] 3814 (+ 0) Initializing Bravo
[20200104T230232] 3894 (+ 80) Initializing color settings
[20200104T230232] 3971 (+ 77) Monitor color profile: sRGB IEC61966-2.1
[20200104T230232] 3971 (+ 0) Initializing XMP
[20200104T230232] 3971 (+ 0) Initializing Plug-in Host...
[20200104T230232] 3972 (+ 1) Initializing Photoshop Adapter...
[20200104T230232] 3975 (+ 3) Initializing AS Host...
[20200104T230232] 3975 (+ 0) Initializing Plug-ins...
[20200104T230233] 5368 (+1393) BEGIN -> pse_util::add_mime_types
[20200104T230233] 5368 (+ 0) END -> pse_util::add_mime_types
[20200104T230233] 5368 (+ 0) BEGIN PtComponentLoad->InitializeAdvancedComponents()...
[20200104T230233] 5368 (+ 0) Plug-ins found:
[20200104T230233] 5368 (+ 0) C:\Program Files\Adobe\Elements 2020 Organizer\PhotoshopElementsOrganizer.exe (Sweet Pea 2 Adapter Plugin)
[20200104T230233] 5368 (+ 0) C:\Program Files\Common Files\Adobe\Plug-Ins\Elements 18\File Formats\Camera Raw.8bi
[20200104T230233] 5368 (+ 0) C:\Program Files\Common Files\Adobe\Plug-Ins\Elements 18\File Formats\Camera Raw.8bi (Camera Raw)
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf (PNG)
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf (CompuServe GIF)
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf (BMP)
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\Filters\Standard MultiPlugin.8bf
[20200104T230233] 5368 (+ 0) Plug-Ins\File Formats\Pixar.8BI (Pixar)
[20200104T230233] 5369 (+ 1) Plug-Ins\Organizer Only\PhotoshopAdapter.apl (Photoshop Adapter)
[20200104T230233] 5369 (+ 0) File format plug-ins:
[20200104T230233] 5369 (+ 0) Camera Raw (R: tif crw nef raf orf mrw dcr mos raw pef srf dng x3f cr2 erf sr2 kdc mfw mef arw nrw rw2 rwl iiq 3fr fff srw gpr dxo heic arq cr3)
[20200104T230233] 5369 (+ 0) PNG (R: png pns)
[20200104T230233] 5369 (+ 0) CompuServe GIF (R: gif)
[20200104T230233] 5369 (+ 0) BMP (R: bmp rle dib)
[20200104T230233] 5369 (+ 0) Pixar (R: pxr)
[20200104T230233] 5369 (+ 0) Initializing CoolType
[20200104T230233] 5369 (+ 0) END PtComponentLoad->InitializeAdvancedComponents()
[20200104T230233] 5370 (+ 1) System:
[20200104T230233] 5370 (+ 0) System Architecture: AMD CPU Family:15 Model:1 Stepping:0 with MMX, SSE Integer, SSE FP, SSE2
[20200104T230233] 5370 (+ 0) Driver versions:
[20200104T230233] 5370 (+ 0) Microsoft DirectX Version: 9.0
[20200104T230233] 5370 (+ 0) Support application versions:
[20200104T230233] 5370 (+ 0) Adobe Acrobat Reader Version: Not installed
[20200104T230233] 5370 (+ 0) Adobe Acrobat Version: Not installed
[20200104T230233] 5370 (+ 0) Initializing OLS
[20200104T230233] 5394 (+ 24) Cleaning up old email attachments
[20200104T230233] 5395 (+ 1) Initializing Controller...
[20200104T230233] 5396 (+ 1) Initializing Platform...
[20200104T230233] 5396 (+ 0) Initializing Threads...
[20200104T230233] 5397 (+ 1) Initializing Model...
[20200104T230233] 5397 (+ 0) Begin Open Amoc Database
[20200104T230445] 136731 (+131334) End Open Amoc Database
[20200104T230517] 169156 (+32425) StopSynAgentIfConflicts called.
[20200104T230517] 169156 (+ 0) StopSynAgentIfConflicts > SyncEngine exited.
[20200104T230519] 170924 (+1768) StopSynAgentIfConflicts called.
[20200104T230519] 170924 (+ 0) StopSynAgentIfConflicts > SyncEngine exited.
[20200104T230519] 170939 (+ 15) Initializing Main Interface...
[20200104T230519] 171145 (+ 206) Main window visible
[20200104T230519] 171212 (+ 67) Finished UI init.
[20200104T230522] 174396 (+3184) ########CALLING RENDER FILE.#####
[20200104T230522] 174441 (+ 45) ########COMPLETED RENDERING FILE.#####
[20200104T230523] 174570 (+ 128) ########CALLING RENDER FILE.#####
[20200104T230523] 174579 (+ 9) ########COMPLETED RENDERING FILE.#####
[20200104T230523] 174700 (+ 121) ########CALLING RENDER FILE.#####
[20200104T230523] 174709 (+ 9) ########COMPLETED RENDERING FILE.#####
[20200104T230523] 174826 (+ 117) ########CALLING RENDER FILE.#####
[20200104T230523] 174835 (+ 9) ########COMPLETED RENDERING FILE.#####
[20200104T230523] 174957 (+ 122) ########CALLING RENDER FILE.#####
[20200104T230523] 174968 (+ 11) ########COMPLETED RENDERING FILE.#####
[20200104T230523] 175085 (+ 117) ########CALLING RENDER FILE.#####
[20200104T230523] 175093 (+ 😎 ########COMPLETED RENDERING FILE.#####
[20200104T230523] 175207 (+ 114) ########CALLING RENDER FILE.#####
[20200104T230523] 175215 (+ 😎 ########COMPLETED RENDERING FILE.#####
[20200104T230523] 175330 (+ 115) ########CALLING RENDER FILE.#####
[20200104T230523] 175340 (+ 10) ########COMPLETED RENDERING FILE.#####
[20200104T230523] 175457 (+ 117) ########CALLING RENDER FILE.#####
[20200104T230523] 175465 (+ 😎 ########COMPLETED RENDERING FILE.#####
[20200104T230524] 175581 (+ 116) ########CALLING RENDER FILE.#####
[20200104T230524] 175592 (+ 11) ########COMPLETED RENDERING FILE.#####
[20200104T230524] 175708 (+ 116) ########CALLING RENDER FILE.#####
[20200104T230524] 175716 (+ 😎 ########COMPLETED RENDERING FILE.#####
[20200104T230524] 175828 (+ 112) ########CALLING RENDER FILE.#####
[20200104T230524] 175837 (+ 9) ########COMPLETED RENDERING FILE.#####
[20200104T230524] 175952 (+ 115) ########CALLING RENDER FILE.#####
[20200104T230524] 175963 (+ 11) ########COMPLETED RENDERING FILE.#####
[20200104T230524] 175988 (+ 25) reloadNavigatorAndView() initializing for a new Search
[20200104T230532] 183807 (+7819) App is now visible and ready for input...
[20200104T230532] 183809 (+ 2) Begin PtContentbgThread() construction
[20200104T230532] 183809 (+ 0) End PtContentbgThread() construction
[20200104T230613] 225100 (+41291) reloadNavigatorAndView() initializing for a new Search
[20200104T230613] 225197 (+ 97) App is now ready for input...
[20200104T230614] 225709 (+ 512) reloadNavigatorAndView() initializing for a new Search
[20200104T230614] 225728 (+ 19) App is now ready for input...
[20200104T230628] 239513 (+13785) reloadNavigatorAndView() initializing for a new Search
[20200104T230628] 239561 (+ 48) App is now ready for input...
[20200104T231153] 565436 (+30533) preferred width of prefs pane 0 (General) is 565
[20200104T231153] 565438 (+ 2) preferred width of prefs pane 1 (Files) is 741
[20200104T231153] 565439 (+ 1) preferred width of prefs pane 2 (Editing) is 538
[20200104T231153] 565441 (+ 2) preferred width of prefs pane 3 (Camera or Card Reader) is 810
[20200104T231153] 565442 (+ 1) preferred width of prefs pane 4 (Scanner) is 572
[20200104T231153] 565443 (+ 1) preferred width of prefs pane 5 (Keyword Tags and Albums) is 549
[20200104T231153] 565444 (+ 1) preferred width of prefs pane 6 (Email) is 715
[20200104T231153] 565445 (+ 1) preferred width of prefs pane 7 (Adobe Partner Services) is 779
[20200104T231153] 565447 (+ 1) preferred width of prefs pane 8 (Media-Analysis) is 372
[20200104T231153] 565448 (+ 1) preferred width of prefs pane 9 (Application Updates) is 446
[20200104T231153] 565463 (+ 15) preferred width of prefs pane 10 (Country/Region Selection) is 561

billj2029259Author

Known Participant

I had a chance to look closer at the above log and noticed a few suspicious lines.

[20200104T230517] 169156 (+32425) StopSynAgentIfConflicts called.
[20200104T230517] 169156 (+ 0) StopSynAgentIfConflicts > SyncEngine exited.
[20200104T230519] 170924 (+1768) StopSynAgentIfConflicts called.
[20200104T230519] 170924 (+ 0) StopSynAgentIfConflicts > SyncEngine exited.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded