Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

frame offset + num frames to utilize http range header #3783

Open
mogwai opened this issue May 3, 2024 · 1 comment
Open

frame offset + num frames to utilize http range header #3783

mogwai opened this issue May 3, 2024 · 1 comment

Comments

@mogwai
Copy link

mogwai commented May 3, 2024

🚀 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.

@ae99
Copy link

ae99 commented Jul 1, 2024

When using FFMPEG backend (and passing a URL or FileLike) and interacting with the underlying StreamingMediaDecoder, FFMPEG only ends up reading first n bytes to get num_frames. As far I can tell it also can use range requests on the underlying URL if it knows the framelength or has an index, but most variable bitrate formats it ends up just manually seeking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants