github/DeepFaceLive
1
0
Fork 0
mirror of https://github.com/iperov/DeepFaceLive synced 2025-08-14 02:37:01 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

add developer FAQ

Browse source
This commit is contained in:
iperov 2021-08-28 19:17:19 +04:00
commit c86305718d
2 changed files with 21 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -69,7 +69,9 @@ Windows 10
## Documentation
<a href="doc/faq/faq.md">Frequently Asked Questions</a>
<a href="doc/faq/faq.md">User FAQ</a>
<a href="doc/developer_faq/developer_faq.md">Developer FAQ</a>
</td></tr>
<tr><td colspan=2 align="center">

18
doc/developer_faq/developer_faq.md Normal file
View file

@ -0,0 +1,18 @@
<table align="center" border="0">
<tr><td colspan=2 align="center">
## Why Python for such high load software and not C++?
All CPU-intensive tasks are done by native libraries compiled for Python, such as OpenCV, NumPy, PyQt, onnxruntime. Python is more like a command processor that tells what to do. All you need is to organize such commands properly.
## What does the internal architecture look like?
It consists of backend modules that work in separate processes. The modules work like a conveyor belt. CameraSource(FileSource) generates the frame and sends it to the next module for processing. The final output module outputs the stream to the screen with the desired delay. Backend modules manage the abstract controls that are implemented in the UI. Thus, the Model-View-Controller pattern is implemented. To reduce latency, some custom interprocess communication elements are implemented.
</td></tr>
</table>