-
All replies
-
Helpful answers
-
Aug 29, 2014 12:44 PM in response to epinosby LarryHN,★HelpfulBest bet - just ignore it - there is not supported way
There is a Hack using Terminal posted in these forums - I do not recommend it but several have used it and claim it worked fine for them - be sure you have good backups prior to doing this
LN
-
Aug 29, 2014 12:46 PM in response to epinosby Old Toad,Do you still want to use the Faces feature but just want to exclude some faces? If that's what you want I don't think you can.
If you want to disable the Faces feature entirely try the following method posted by lopezio:
Re: Iphoto 11 -How to turn off faces?
Dec 30, 2013 9:06 AM (in response to mkmichaelmk)
Start of solution:
I did some digging in the prefs of iPhoto and found out the following. This is how you can disable (turn off) Face detection, without deleting faces found so far (just in case you want to restart processing at another time):
1. Quit iPhoto
2. Open Terminal Application (Applications/Utilities/Terminal.app)
3. Type the following (exactly as is):
defaults write com.apple.iPhoto PKFaceDetectionEnabled 0
(then return)
4. - Start iPhoto - Faces stops getting on your nerves...
If you ever need to re-enable faces, just do the same again and replace the 0 with 1.
Many users posted back that it worked as advertised.
-
Aug 29, 2014 12:52 PM in response to LarryHNby léonie,I do not recommend it but several have used it and claim it worked fine for them - be sure you have good backups prior to doing this
I tried it on a test library, and it caused problems, when opened the library in aperture. I would not do it,i f you are using the library as a unified library in Aperture and iPhoto.
-
Aug 29, 2014 2:10 PM in response to léonieby LarryHN,★HelpfulGood to know - personally I would not do it at all - and i recommend people do not - but some people want it are claim to be happy with the result - and sometimes it gets posted with no warnings so I try to want people that it is unsupported and should be used at their own risk
and being unsupported not only does it cause problems with Aperture now but it may (r may not) cause even larger problems in a future update
LN