https://bugs.kde.org/show_bug.cgi?id=451440
Michael Miller changed:
What|Removed |Added
CC||mbmiller1...@outlook.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=456613
Bug ID: 456613
Summary: Widgets never retain position after logout/reboot
Product: plasmashell
Version: 5.25.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #32 from Michael Miller ---
Hi Gilles,
I've been continuing to work on a Homebrew based arm64 build of digiKam. I'm
still struggling with setting the runtime paths to libraries, plugins,
translations, and other correctly. I&#x
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #34 from Michael Miller ---
Hi Gilles,
I got most of the Qt paths working in the past hour. It's now picking up the
values in the ./Resources/qt.conf file, so that's fixed. I'm working on
QtWebEngine and ImageMagick p
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #37 from Michael Miller ---
Final update for today. App package and package installed DK starts. DK is
finding most of the libraries. Running the app from the installer works.
ImageMagick works, as do most of the tools. It's almost u
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #42 from Michael Miller ---
Hi Gilles,
>Install the current digiKam Qt5 X86 PKG and look like the rc files are
>installed here in the bundle :
>/Applications/digiKam.org/digikam.app/Contents/Resources/kxmlgui5/digikam
Yes, I
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #43 from Michael Miller ---
I meant to say to the PATCH_COMMAND, not CONFIGURE_COMMAND.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #44 from Michael Miller ---
I created a new branch from digikam master to update the ext_kf6 CMakeFile.txt
so it includes fixbundledatapath.sh, but I'm unable to push my new branch
because I'm not a project member. Any chance y
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #46 from Michael Miller ---
Hi Gilles,
I saw your comment over on bug https://bugs.kde.org/show_bug.cgi?id=491857. I
wanted to let you know about a week ago I spent about 1.5 days on the Orbit2
bug and could not figure it out, so I went
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #50 from Michael Miller ---
Hi Gilles,
Your suggestions sound good. I’ll wait until later to work on the spell checker
and the icons. Since I have a working build, I’ll start doing pull requests of
my changes small pieces at a time to get
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #52 from Michael Miller ---
Hi Gilles,
>Do not try to build an universal version, this will bloat the bundles for
>nothing as a x86_64 version already exists.
No, my plan is to do at least 3 different builds Mac ARM64, Mac x86-64,
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #53 from Michael Miller ---
Hi Gilles,
I submitted the first MR. It's for calling fixbundledatapath.sh as part of
patching ext_kf6. Please take a look and accept when you can, it should help
you with Macports when you get to this
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #24 from Michael Miller ---
I think got the same thing a few weeks ago. If you're getting the same thing I
did, it's bug possibly in solid where it's doing a cfrelease on a null pointer.
I have a patch in my repo that
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #26 from Michael Miller ---
That looks EXACTLY like mine. Same issues with the UI.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #29 from Michael Miller ---
I have these in Homebrew. Are these all files what we need for QtCurve?
>/opt/homebrew/share/QtCurve
>/opt/homebrew/share/QtCurve/Breeze.qtcurve
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #31 from Michael Miller ---
Hi Gilles,
Thanks for the info about QtCurves. I now have the UI looking the way it
should.
https://imgur.com/a/ego6gvf
digiKam Homebrew issues:
* Mac menu bar doesn't work
* MariaDB - this is just m
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #32 from Michael Miller ---
Hi Maik and Gilles,
It looks like changing to KF 6.5.0 breaks some ext_breeze patches. Also, I
tried using 8.5.0 and I still get the same cfrelease error in solid.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=491857
Bug ID: 491857
Summary: Unable to build on MaOS: ERROR: Unmodified ffmpeg >=
5.0 is not supported.
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: Compi
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #2 from Michael Miller ---
Thank you for the reply. After hitting too many issues, I gave up on using
Macports, and I'm much further using Homebrew. I'm going to close the ticket.
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=491857
Michael Miller changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #12 from Michael Miller ---
I'm working on a MacOS ARM build of digiKam using Homebrew instead of Macports.
I'll post updates here as my work progresses.
Current Status: I have an almost clean build using v8.4.0 tag. The
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #14 from Michael Miller ---
I agree. The directory structure for Homebrew is a challenge when packaging
the libraries. I think I might have found a solution, though. I'll be able to
test it in a day or two.
Quick update: I am ab
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #15 from Michael Miller ---
Gilles,
Do you mind if I assign this issue to myself?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #19 from Michael Miller ---
I think the biggest blocker to using Craft package manager was I wasn't aware
it existed. :) I'll take a look at it tonight.
Thank you for the suggestion.
Cheers,
Mike
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #22 from Michael Miller ---
Thank you Gilles. I've stopped exploring Craft, and I'm continuing with
Homebrew.
Update: I've given up trying to pin to a specific package variant with
Homebrew, and I'm now using the la
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #24 from Michael Miller ---
Hi Gilles,
Here's a list of libs I've found so far. These are either missing or unable to
be found by @rpath/[optional dir/]:
1. QtDBus.framework/Versions/A/QtDBus: Not found. Should be in ./opt
https://bugs.kde.org/show_bug.cgi?id=491857
--- Comment #7 from Michael Miller ---
Alternatively, you could create patch files and keep Valadoc. See
https://trac.macports.org/ticket/70547
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #25 from Michael Miller ---
I have a (mostly) working build using Homebrew. I've just been struggling with
creating a good bundle. The 2 items I had to comment out was the dark-icons
and gmic. I'll revisit them once I figure
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #27 from Michael Miller ---
Good to know about gmic. I'll post error logs of the gmic build tomorrow.
The biggest problem I'm running into is Qt not finding the plugins. If I run
digikam without relocating the libraries (
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #30 from Michael Miller ---
Hi Gilles,
> It's normal as you use directly the pre-compiled version of the packages. But
> in fact we cannot do it as the Qt6Mysql plugin is not provided in precompiled
> version (at leas
https://bugs.kde.org/show_bug.cgi?id=350446
--- Comment #28 from Michael Miller ---
A forked the project into my own repo. I changed about 15 or 16 files, so I
thought this might be easier for you to take a look. I'm still having path
issues with Qt. Maybe you will have better luck.
https://bugs.kde.org/show_bug.cgi?id=490828
Bug ID: 490828
Summary: Unable to delete workflow
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: macOS (DMG)
OS: macOS
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=350446
Michael Miller changed:
What|Removed |Added
CC||michael_mil...@msn.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=491040
Bug ID: 491040
Summary: Unable to use Darktable for demosaicing on MacOS ARM
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: macOS (DMG)
OS: macOS
https://bugs.kde.org/show_bug.cgi?id=491040
Michael Miller changed:
What|Removed |Added
CC||michael_mil...@msn.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=491042
Bug ID: 491042
Summary: MariaDB (MySQL) embedded files missing in fresh
install
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: macOS (DMG)
https://bugs.kde.org/show_bug.cgi?id=491042
Michael Miller changed:
What|Removed |Added
CC||michael_mil...@msn.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=491040
--- Comment #2 from Michael Miller ---
Using the darktable.dmg for installation puts the binaries in
/Applications/darktable.app/Contents/MacOS.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491042
--- Comment #1 from Michael Miller ---
Created attachment 172139
--> https://bugs.kde.org/attachment.cgi?id=172139&action=edit
symlinks pointing to nowhere
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491040
--- Comment #4 from Michael Miller ---
There's a minor bug in the PR. The path for RawTherapee is:
/Applications/RawTherapee.app/Contents/MacOS
The default MacOS file system is case sensitive. I'll install the other raw
processors and
https://bugs.kde.org/show_bug.cgi?id=491040
--- Comment #7 from Michael Miller ---
Yes, the binaries are all lower case.
I couldn't find an MacOS installation package for ART, and I don't have time to
set up a build environment. Sorry.
Thank you for doing this. I appreciate it.
Ch
https://bugs.kde.org/show_bug.cgi?id=475488
--- Comment #5 from Michael Miller ---
Thank Gilles. Yes. Adding a quality measurement such as eDifFIQA(T) to
determine if the face thumbnail is usable for recognition is an option I'm
exploring to improve accuracy. My testing with SFace, howeve
https://bugs.kde.org/show_bug.cgi?id=425263
--- Comment #6 from Michael Miller ---
Adding facial detection and recognition is a large effort, but is a
possibility. First we could generate a list of jpegs from the key frames of a
video, and run the existing face pipeline on the jpegs. FFMpeg
https://bugs.kde.org/show_bug.cgi?id=425263
--- Comment #5 from Michael Miller ---
YuNet is much more accurate at detecting a blurred face. SFace is also more
accurate at matching pixelated or blurred faces. I believe the issue is
significantly improved by moving to the new models.
I
https://bugs.kde.org/show_bug.cgi?id=436527
Michael Miller changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=485992
--- Comment #20 from Michael Miller ---
Hi Andy,
For face recognition, set the accuracy to about 60%. You should get almost 0
false positives if the people you’ve tagged are all correct. I will be updating
the documentation soon.
Cheers,
Mike
--
You
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #16 from Michael Miller ---
Hi Jonathan,
Can you please tell us what settings you’re using? Which face detection model,
detection accuracy %, face size setting, face recognition model, and face
recognition accuracy %?
Cheers,
Mike
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #18 from Michael Miller ---
Hi Jonathan,
First, please make sure you have the latest build from yesterday.
Try these settings:
Detection accuracy: 60%
Model: YuNet
Face Size: Large
Recognition Accuracy: 60%
Model: SFace
Uncheck Work on
https://bugs.kde.org/show_bug.cgi?id=485992
--- Comment #22 from Michael Miller ---
I'm working on updating the defaults for the models. Hopefully I'll have
something in a few days. For now, try this:
Low false-positive rate, but will miss some faces and matches
YuNet: 60%
Large f
https://bugs.kde.org/show_bug.cgi?id=389046
--- Comment #36 from Michael Miller ---
(In reply to nonobio from comment #35)
> Thank you, good luck :)
Hi nonobio,
This definitely a UI issue, and not related to the detection and recognition
engine. I've experienced it, too.
@Gilles a
https://bugs.kde.org/show_bug.cgi?id=436727
Michael Miller changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=429230
--- Comment #8 from Michael Miller ---
Yes. This can probably be closed with the next release. This due to do an
issue with the KDTree/KDNode findClosestNeighbor search function that I fixed
today. Additional testing is needed before I can confirm
https://bugs.kde.org/show_bug.cgi?id=472266
Michael Miller changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=431797
--- Comment #16 from Michael Miller ---
The new facial models coming in digiKam 8.5.0 are over 10x more accurate at
recognizing the correct face when used with the proper settings and there
aren't any accidentally confirmed bad faces assigned
https://bugs.kde.org/show_bug.cgi?id=469178
Michael Miller changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469178
Michael Miller changed:
What|Removed |Added
Version Fixed In||8.5.0
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=478557
Michael Miller changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=437896
Michael Miller changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|digikam-bugs-n
https://bugs.kde.org/show_bug.cgi?id=431797
Michael Miller changed:
What|Removed |Added
Assignee|digikam-bugs-n...@kde.org |michael_mil...@msn.com
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #14 from Michael Miller ---
Thanks Gilles,
Yes, the accuracy rate of the new system in 8.5.0 is at least an order of
magnitude better than before.
Jonathan, the new face detection system (YuNet) is up to 30 times faster than
YOLO. The new
https://bugs.kde.org/show_bug.cgi?id=444160
Michael Miller changed:
What|Removed |Added
Assignee|digikam-bugs-n...@kde.org |michael_mil...@msn.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=485992
--- Comment #17 from Michael Miller ---
I did a little research, and I was wrong. YuNet was added to OpenCV in v4.5.1,
and updated in 4.5.4. I'll update the checks tonight to check for a minimum
OpenCV version of 4.6 for YuNet. SFace is the
https://bugs.kde.org/show_bug.cgi?id=444394
--- Comment #10 from Michael Miller ---
Yes, this is a known issue. The problem is digiKam doesn't save which
suggestion has been rejected as a match for a tagged face. It's something I'm
researching for the next rewrite of the Fac
https://bugs.kde.org/show_bug.cgi?id=423113
--- Comment #12 from Michael Miller ---
Yes, as Maik says, you need to rebuild the training database using the
maintenance tool. I'm planning to fix this issue when I rewrite the entire
facial recognition system after then 8.5.0 release.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=485992
--- Comment #18 from Michael Miller ---
Hi Andy,
It looks like there is a new build of digiKam from today. It should have both
YuNet and SFace detection and recognition models enabled on Windows. Can you
give it a try, please?
Cheers,
Mike
--
You
https://bugs.kde.org/show_bug.cgi?id=447767
--- Comment #27 from Michael Miller ---
Gilles,
I shoot Sony (a7R III). Face regions are detected correctly in my RAW .ARW
files. I have verified over 300 files.
Igor, what model of Sony do you have?
Cheers,
Mike
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=436727
--- Comment #4 from Michael Miller ---
*** Bug 436527 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485029
--- Comment #11 from Michael Miller ---
I like the YOLO models for general object detection and identification
(classification). I plan on looking at the new YOLO models along with updated
taxonomies for better auto-tagging of images when I'm fin
https://bugs.kde.org/show_bug.cgi?id=485979
Michael Miller changed:
What|Removed |Added
Assignee|digikam-bugs-n...@kde.org |michael_mil...@msn.com
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=485979
Michael Miller changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=430251
--- Comment #5 from Michael Miller ---
Hi Chris,
Yes. Scanning a RAW file, and your case a .CR2 will take longer because we have
to convert the RAW to jpeg for face recognition. The issue is that the JPEG
image may or may not be exactly the same size
https://bugs.kde.org/show_bug.cgi?id=430251
--- Comment #3 from Michael Miller ---
Hi Gilles,
I agree with @Maik that this request is problematic. I think the correct
solution is to make face detection and recognition faster for each image
individually. Using other images to try to identify
https://bugs.kde.org/show_bug.cgi?id=485979
--- Comment #9 from Michael Miller ---
This is already included in new YuNet implementation and YuNet UI. It is the
"face size" setting. When the use selects "large" or "extra large" faces, the
code resizes the orig
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #36 from Michael Miller ---
I'm using an M1 MacBook Pro, so we have that covered. Linux would be good,
especially if it has an NVidia CUDA capable GPU.
It's really whatever you want. The code is all the same for each platfor
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #42 from Michael Miller ---
(In reply to caulier.gilles from comment #41)
> Look also this comment :
>
> https://bugs.kde.org/show_bug.cgi?id=495014#c3
>
> Typically, to be able to use opencl with opencv in digiKam, Mesa pa
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #28 from Michael Miller ---
Hi Jonathan,
Yes, many, many things have changed. First, we've introduced 2 new models in
8.5.0. YuNet is now the preferred face detection model. It is much faster
than YOLO and SSD. Second, we have
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #31 from Michael Miller ---
Also, to speed things up, try using "Extra Large" as the face size settings.
"Large" is good, too. "Large" will be the default starting tomorrow.
Cheers,
Mike
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #33 from Michael Miller ---
(In reply to atoms from comment #32)
> That sounds really good. I have a huge collection, do you want me to help
> you test / build anything?
Hi Atoms,
Yes! Tuning the models isn't an exact scie
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #34 from Michael Miller ---
Hi Jonathan,
There is a bug in the code I just discovered. Face detection is ok. Face
recognition is not working right now. I'll let you know as soon as I fix the
bug.
Cheers,
Mike
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #30 from Michael Miller ---
Hi Jonathan,
Please download a new build. I made some updates to the models yesterday.
Cheers,
Mike
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #26 from Michael Miller ---
Hi Jonathan,
When was the last time you downloaded digiKam? There was an issue in a build
from last week. The issue was even if you selected SFace in the settings, it
would still use OpenFace. Please download
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #39 from Michael Miller ---
(In reply to Jonathan from comment #38)
> I only have a AMD CPU so CUDA is useless to me.
Hi Jonanathan,
That's ok. AMD can use OpenCL which will still allow for GPU offloading and
speedup. Follow the
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #44 from Michael Miller ---
(In reply to Jonathan from comment #43)
> I believe I have OpenCL but even though its on, it doesn't seem to help as
> just face detection alone took around 16 hours.
> I have a 7900xtx, and if it
https://bugs.kde.org/show_bug.cgi?id=401458
Michael Miller changed:
What|Removed |Added
CC||michael_mil...@msn.com
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=401458
Michael Miller changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=484743
Michael Miller changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=485029
Michael Miller changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=425981
Michael Miller changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=437896
--- Comment #8 from Michael Miller ---
(In reply to caulier.gilles from comment #7)
> Michael,
>
> I reopen 449310, as the topic sounds like different.
>
> Gilles
Yes, I agree. They are different suggestions.
Cheers,
Mike
--
Yo
https://bugs.kde.org/show_bug.cgi?id=494284
Michael Miller changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=437896
--- Comment #5 from Michael Miller ---
My testing shows this can probably be closed.
Cheers,
Mike
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472416
--- Comment #2 from Michael Miller ---
I looked into this idea when implementing YuNet and SFace. There are 2
concerns with it. First, there is a significantly greater than 0 probability
that 2 faces found in the same image could be the same person
https://bugs.kde.org/show_bug.cgi?id=435146
--- Comment #4 from Michael Miller ---
Hi Gilles,
I think we can close this. The workflow now will clear a suggestion for a
face/image if it's not suggested in the most recent recognition run.
Cheers,
Mike
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #47 from Michael Miller ---
(In reply to Jonathan from comment #45)
> So I installed the newest version from today, and cleared the training data.
> The recognition seems to be better. The false positives seemed to drop
> sign
https://bugs.kde.org/show_bug.cgi?id=469178
--- Comment #7 from Michael Miller ---
Thanks Andy, we appreciate your help! It looks like we're moving in the right
direction.
Lowering the accuracy a little more should pick up most of the other faces. I
strongly recommend that you when dro
https://bugs.kde.org/show_bug.cgi?id=469178
--- Comment #9 from Michael Miller ---
Hallo Andy,
Bitte!
Thank you for your patience, and my limited German. I'm happy this is working
for you now.
Cheers,
Mike
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #24 from Michael Miller ---
Hi Jonathan,
Let's start from the beginning.
You should be using YuNet to find the faces, 65% accuracy, and medium or large
face size.
After the faces are found, you should be using SFace to recognize (
https://bugs.kde.org/show_bug.cgi?id=485992
Michael Miller changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|digikam-bugs-n
https://bugs.kde.org/show_bug.cgi?id=429230
Michael Miller changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|digikam-bugs-n
https://bugs.kde.org/show_bug.cgi?id=436544
Michael Miller changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
1 - 100 of 290 matches
Mail list logo
