frame offset + num frames to utilize http range header
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 799
- Avg merge
- 58m
- Merged PRs (30d)
- 3
Description
🚀 The feature
If load is called with a url e.g.
torchaudio.load(url, frame_offset=16000, num_frames=16000)
And the url supports range headers, is it not possible to only get the required bytes from the url??
Motivation, pitch
Would make it possible to load sections of large audio files quickly without having to pre cut them.
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
Start by tracing the torchaudio.load(url, frame_offset, num_frames) entry point and how URL-backed audio is currently fetched. Check how HTTP range support would interact with byte offsets and audio formats; done means loading the requested frame section without retrieving the full remote file when the URL supports ranges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100