Implement ZegoEffect
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- cli, mobile-dev
Research direction
The request concerns integrating the third-party ZegoEffects SDK for beauty filtering on the Android side, with the I420 processing call shown in the issue body. Nothing in the payload names a RootEncoder file or entry point to start from, so the first step is locating where RootEncoder exposes raw frame hooks in its Android source. Done would mean a working example of feeding frames through the effect processor, which the issue does not define.
Written by the indexing model from the issue text.
Description
I am trying to implement a beauty filter using ZegoEffect. I started with the DeepAR example but I couldn't figure out how to do it.
The methods that can be used to process frames in ZegoEffect are as follows:
Example I420 process code:
ZegoEffectsVideoFrameParam param = new ZegoEffectsVideoFrameParam();
param.setFormat(ZegoEffectsVideoFrameFormat.I420);
param.setWidth(width);
param.setHeight(height);
if (mZegoEffects != null) {
mZegoEffects.processImageBufferYUV(data, dataLength, param);
}
How can I integrate it?
https://docs.zegocloud.com/article/9916
- Dominant language
- Kotlin
- Stars
- 3k
- Forks
- 946
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pedroSG94/RootEncoder
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pedroSG94/RootEncoder#2213 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pedroSG94/RootEncoder#2207 · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pedroSG94/RootEncoder#2203 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pedroSG94/RootEncoder#2192 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pedroSG94/RootEncoder#2177 · 44 comments ·
Maintainers usually reply within 2 days
All issues in pedroSG94/RootEncoder
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
saisaharsh3/Leftovers#13 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
navikt/esyfo-narmesteleder#700 ·
Maintainers usually reply within 1 day
-
A2A agent card served at agent.json, but A2A 0.3.0 uses agent-card.jsonPossibly taken @hadirsa claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
embabel/embabel-agent#2142 ·
Maintainers usually reply within 1 day
-
bug feedback required
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
streetcomplete/StreetComplete#7275 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Kotlin/kotlin-lsp#288 ·