Transcode duration similar with turned off audio transcoding
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 663
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
Hi.
I'm using your library for a project and I have a question about the track transformation durations.
I have 2 scenarios:
1. Transcode video and audio track.
2. Transcode video track only.
Test device: Pixel 5
Scenario1: video track transformation: 32213 ms, audio track transformation: 19693 ms = 51906ms
Scenario2: video track transformation: 48814 ms, audio track transformation: 3206 ms = 52020ms
Test device: Huawei P20 Pro
Scenario1: video track transformation: 84594 ms, audio track transformation: 21813 ms = 106407ms
Scenario2: video track transformation: 102020 ms, audio track transformation: 4584 ms = 106604ms
I used your demo app, and I got these numbers which was surprising, because I expected less transcoding time if I turn off the audio track transcode.
How can be this possible? What is the reason behind this?
Contributor guide
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.
Research direction
The report only identifies the demo app and test devices; it names no source file or test. Reproduce both audio-enabled and video-only scenarios on the Pixel 5 and Huawei P20 Pro, compare the reported durations, and document the cause or confirm the behavior is expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100