https://bugs.kde.org/show_bug.cgi?id=426481
--- Comment #18 from Minh Nghia Duong ---
(In reply to Chris from comment #17)
> Tried again with latest build of 20201008.
>
> Reset the faces database in maintenance
> waited till it finished rebuilding the faces database
> confirme
https://bugs.kde.org/show_bug.cgi?id=426309
--- Comment #11 from Minh Nghia Duong ---
Hi all,
About different detection models, could you give me the link to some models
that you're having in mind? I would like to dig into the different models to
see their implementation with opencv in ord
https://bugs.kde.org/show_bug.cgi?id=426888
--- Comment #6 from Minh Nghia Duong ---
Hi,
It crashed in function readNetFromTorch() so the data file for neural net is
not found. Can you see the location of neural net files in the debug message
while digikam is loading?
And is the data files
https://bugs.kde.org/show_bug.cgi?id=426309
--- Comment #10 from Minh Nghia Duong ---
(In reply to princeanthony.tiago from comment #9)
> Just wondering if you'd had any further thoughts on this topic. Given that
> the limitations of the current face detection model are basically
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #155 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #154)
Yes, only one FaceExtractor is allocated at the init sequence of digikam. After
that, the multi-threading only envoked in the recognition process.
--
You are
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #153 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #151)
> Marcel,
>
> You lost memory a little bit, but the infamous crash in Preview thread
> disappear. Right ?
>
> If yes, we will trying to disc
https://bugs.kde.org/show_bug.cgi?id=426309
--- Comment #7 from Minh Nghia Duong ---
(In reply to Rob D from comment #6)
Hi Rob,
I agree with your concern. Normally, for the current CNN models of object
detection, the pre-processing and post-processing are nearly the same between
different
https://bugs.kde.org/show_bug.cgi?id=426309
--- Comment #5 from Minh Nghia Duong ---
Hi all,
Say that we can support customized face detection backend. How do you intend to
use it after importing the data files?
For example, how would you like to configure it and the DNN would be another
pre
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #105 from Minh Nghia Duong ---
(In reply to Maik Qualmann from comment #104)
> This backreace is not from the current head of master. Please try the
> current master version.
>
> Maik
This is the new back trace :
Threa
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #103 from Minh Nghia Duong ---
Created attachment 131496
--> https://bugs.kde.org/attachment.cgi?id=131496&action=edit
BackTrace after fixing FaceExtractor memory consumtion
Hi Maik,
Here the backtrace. It's still the same e
https://bugs.kde.org/show_bug.cgi?id=426309
--- Comment #4 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #1)
> Nghia,
>
> Look the topic of this entry, this is what we talk together last winter
> about the capability to download data model on demand.
>
&g
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #98 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #97)
> Marcel,
>
> See my comment:
>
> https://bugs.kde.org/show_bug.cgi?id=426185#c4
>
> The huge memory allocation at startup is now
https://bugs.kde.org/show_bug.cgi?id=426185
--- Comment #2 from Minh Nghia Duong ---
Hi Maik,
This issue has been fixed by implementing a shared private static pointer,
under commit
https://invent.kde.org/graphics/digikam/-/commit/28027b21d9fa4368eb2f2ad26dbb1cb33e274cce
Nghia
--
You are
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #92 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #91)
> Nghia,
>
> It still a pending Q in my mind. Currently, all digiKAm bundle still
> compiled with OpenCV LTS version 3.4.11.
>
> There is an a
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #88 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #86)
> Nghia,
>
> well, this is not what's a read. depending of OpenCV version, especially the
> 4.x, opencv try to use GPU optimizations every
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #83 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #82)
> Hi all,
>
> Reading the OpenCV document, that i try to understand, we have this
> envirronement variable which can be changed
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #80 from Minh Nghia Duong ---
I implement singleton on FacialRecognitionWrapper so that it initiated only
once. I also reduce the number of FaceExtractor to 1, which is the same as the
previous version of faces engine. However, this error
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #72 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #70)
> This is a desktop video capture under Kubuntu 20.04 VM session running
> compiled digiKam 7.2.0-beta1 while face detection inside valgrind. Look well
> t
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #69 from Minh Nghia Duong ---
(In reply to Maik Qualmann from comment #66)
> The main problem is the "shapepredictor.dat", this file is also loaded 40
> times into the memory.
>
> Maik
shapepredictor.dat is loa
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #65 from Minh Nghia Duong ---
Yes, it has to be 4 times but I found only 3 instances in FacesManagement. But
either way, the solution to this problem can be making this class a singleton
since it is nothing but an interface to the
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #63 from Minh Nghia Duong ---
(In reply to Maik Qualmann from comment #60)
> The cause of the high memory consumption at the beginning in digiKam-7.2.0
> is bug 426185. We load the file
> "/usr/share/digikam/facesengine/openf
https://bugs.kde.org/show_bug.cgi?id=426185
--- Comment #1 from Minh Nghia Duong ---
(In reply to Maik Qualmann from comment #0)
> The file "/usr/share/digikam/facesengine/openface_nn4.small2.v1.t7" is
> loaded 10 times per RecognitionPreprocessor. A total of about 40 times a
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #12 from Minh Nghia Duong ---
I will go through this problem while reform faces management in preparation for
the portage to DPlugin. I hope I will fund somethings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #10 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #9)
How large is your collection? I found that it crashes after found about 3000
faces.
Nghia
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #8 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #7)
> Hi Nghia,
>
> Do you use also a Ubuntu like Linux ?
>
Yes, I use Ubuntu 18.4.
> Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #6 from Minh Nghia Duong ---
Hi Gilles,
Yes, I can reproduce it with a huge trunk of images. I am investigating it. I
suspect that somewhere in faces pipeline where I changed QImage to QImage*
could cause the problem. As I remember, it
https://bugs.kde.org/show_bug.cgi?id=423113
--- Comment #8 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #7)
Thank Gilles,
Is there any conflicts that worth noticing?
Best,
Nghia
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426003
--- Comment #8 from Minh Nghia Duong ---
Hi Markd,
As Trung said, for now, both the pre-trained YOLO and SSD models can recognize
basic objects. In order to apply recognition on a specific set of objects,
users might need to find a specific pre
https://bugs.kde.org/show_bug.cgi?id=426003
--- Comment #5 from Minh Nghia Duong ---
Implementing DNN detection is simple, but we also need to define the use-cases
and workflow for object detection.
We can just choose an image and then return the image with bounding boxes and
the name of the
https://bugs.kde.org/show_bug.cgi?id=426003
--- Comment #3 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #2)
Yes, I did. Actually, I tried it and it works wonderfully with the existing SSD
and YOLO faces detection of faces engine. All we need to do is to download the
https://bugs.kde.org/show_bug.cgi?id=425981
--- Comment #2 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #1)
> Nghia,
>
> This new entry in bugzilla can be considerate are solved with the new faces
> clustering implementation from your project.
>
> Best r
https://bugs.kde.org/show_bug.cgi?id=409995
Minh Nghia Duong changed:
What|Removed |Added
CC||minhnghiaduong...@gmail.com
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=423113
--- Comment #6 from Minh Nghia Duong ---
(In reply to Kartik from comment #5)
> Hi Nghia,
>
> The Top Level Connections for the Deleting button are done in
> DigikamItemView. The Delete Button forms part of a FaceRejectionOverlay, and
>
https://bugs.kde.org/show_bug.cgi?id=423113
Minh Nghia Duong changed:
What|Removed |Added
CC||minhnghiaduong...@gmail.com
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=416630
--- Comment #4 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #3)
Hi,
The K-Nearest search has been implemented and tested. It gives the best result
so far.
Nghia
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=416988
--- Comment #6 from Minh Nghia Duong ---
(In reply to caulier.gilles from comment #5)
> Nghia,
>
> Just look my previous comment #4...
>
> Gilles
Hello Gilles,
It's a very interesting feature. What is the name of the model use
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #25 from Minh Nghia Duong ---
(In reply to griffiths_andy from comment #22)
> Since the slideshow preferences have moved in 7.0.0-beta3 to within the
> slideshow screen itself as part of the progress indicator buttons, it is
> obse
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #24 from Minh Nghia Duong ---
Hello,
Yes, sure. I will try
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=38
--- Comment #6 from Minh Nghia Duong ---
Hello Jens,
I am not familiar with the Clarifai platform. Could you help me clarify some
points, please?
Firstly, As in your description, when you import an image to Clarifai, it will
return an output with the
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #18 from Minh Nghia Duong ---
Hello,
I have completed the plugin slideshow and here is the link to my merge request:
https://invent.kde.org/kde/digikam/-/merge_requests/11
Thank you in advance for reviewing it for me.
Nghia
--
You are
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #16 from Minh Nghia Duong ---
I am adding these updating functionalities to setItemInfo of DBInfoIface but
one thing a little bit weird appears to me. It is that the method toggleTag of
SlideShow is used nowhere. This method only emit a
https://bugs.kde.org/show_bug.cgi?id=414055
Minh Nghia Duong changed:
What|Removed |Added
Attachment #126428|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #10 from Minh Nghia Duong ---
Hello Gilles,
I am finalizing it. I will deliver to you the patch tomorrow.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #7 from Minh Nghia Duong ---
Thanks Gilles,
It has been clearer to me.
Could you point me to the function or the file where the slideshow is initiated
from the main interface? Because I have only found codes in app/view/stack
where some
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #5 from Minh Nghia Duong ---
Gilles,
Actually Yes,
It's still unclear to me how the information is passed between DInfoIterfaces
and what is the link of classes SlideShowBuilder and SlideShow except that they
use SlideShowSettin
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #3 from Minh Nghia Duong ---
Thanks Maik,
I will try it.
Nghia
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414055
--- Comment #1 from Minh Nghia Duong ---
Created attachment 126428
--> https://bugs.kde.org/attachment.cgi?id=126428&action=edit
Patch for slideshow plugin
I have created a copy of slideshow utilities in dplugin for slideshow. It's all
https://bugs.kde.org/show_bug.cgi?id=414055
Minh Nghia Duong changed:
What|Removed |Added
CC||minhnghiaduong...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=414284
--- Comment #1 from Minh Nghia Duong ---
Hello,
Here is the merge request of the patch:
https://invent.kde.org/kde/digikam/merge_requests/8
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392758
--- Comment #9 from Minh Nghia Duong ---
Created attachment 124002
--> https://bugs.kde.org/attachment.cgi?id=124002&action=edit
Patch for random slideshow
Here is the patch that adds suffle functionality to slideshow. Use can activa
https://bugs.kde.org/show_bug.cgi?id=392758
--- Comment #7 from Minh Nghia Duong ---
Sorry, my bad. I thought it was to assign the job.
By the way, I have add an option to show images in random order. The images are
suffled at the beginning at each slideshow. Is it ok to you or you need the
https://bugs.kde.org/show_bug.cgi?id=392758
Minh Nghia Duong changed:
What|Removed |Added
CC||minhnghiaduong...@gmail.com
52 matches
Mail list logo
