TeamNewPipe / TeamNewPipe/NewPipeExtractor

Add all Itags

Open
#71 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement YouTube
Dominant language
Java
Stars
2k
Forks
602
Avg merge
3d 6h
Merged PRs (30d)
6

Description

Currently the NewPipeExtractor doesn't handle all Itags. Some because "it's not well supported in older devices" (e.g. Opus). Some because we "Don't add VideoOnly streams that have normal variants". Some because we don't have added HDR support. Some others are just missing. IMHO we should just add all Itags, since NewPipeExtractor is just an extractor. We should let the frontend (e.g. NewPipe most of the time) handle choosing the stream from the available ones. Also the FPS is often incorrect (30 instead of 24).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the NewPipeExtractor stream extraction paths and the existing Itag handling. Identify which Itags are omitted, including Opus, video-only variants, and HDR streams, and verify how FPS values are assigned. Done means the extractor exposes all supported Itags with corrected FPS values while leaving stream selection to the frontend.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.