Read remote audio segments with ffmpeg#257
Open
GaganNarula wants to merge 4 commits into
Open
Conversation
GaganNarula
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We currently allow reading audio by time with
start_timeandend_timeinread_audio. However, this results in actually downloading the entire file first. This utility uses ffmpeg's http range request to only read segments from a large file on a google cloud bucket. Currently only supports gcs, but in principle the approach will also work with s3 buckets.Why do we need it ? This is relation to PR #255 . The problem we're facing is that some datasets like the spanish-carrion-crows dataset contain very large audio files (> 10 hrs). We actually don't need the entire file just segments from it defined by a selection table.
In general, we need to be able to read very long audio from buckets quickly without memory overhead and long download times. It'll be useful for PAM data as an example.. There is a way to do this using filesystem byte range reads without using ffmpeg but that approach works only for uncompressed audio like WAV format.