Support compression level in i/o dispatcher backend - Githubissues

pytorch / audio

Data manipulation and transformation for audio signal processing, powered by PyTorch

https://pytorch.org/audio

BSD 2-Clause "Simplified" License

2.5k stars 644 forks source link

Support compression level in i/o dispatcher backend #3662

Closed hwangjeff closed 11 months ago

hwangjeff commented 11 months ago

Differential Revision: D50367721

pytorch-bot[bot] commented 11 months ago

:link: Helpful Links

:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/audio/3662

:page_facing_up: Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

:white_check_mark: No Failures

As of commit 2192ce691b19976a22709cd664fc43ad4fb79ea7 with merge base 671261c39c04a1999c75f9a9a04ffa8ebf1d095d (): :green_heart: Looks good so far! There are no failures yet. :green_heart:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

facebook-github-bot commented 11 months ago

This pull request was exported from Phabricator. Differential Revision: D50367721

facebook-github-bot commented 11 months ago

This pull request was exported from Phabricator. Differential Revision: D50367721

facebook-github-bot commented 11 months ago

This pull request was exported from Phabricator. Differential Revision: D50367721

facebook-github-bot commented 11 months ago

This pull request was exported from Phabricator. Differential Revision: D50367721

facebook-github-bot commented 11 months ago

This pull request was exported from Phabricator. Differential Revision: D50367721

facebook-github-bot commented 11 months ago

This pull request was exported from Phabricator. Differential Revision: D50367721

github-actions[bot] commented 11 months ago

Hey @None. You merged this PR, but labels were not properly added. Please add a primary and secondary label (See https://github.com/pytorch/audio/blob/main/.github/process_commit.py).

Some guidance:

Use 'module: ops' for operations under 'torchaudio/{transforms, functional}', and ML-related components under 'torchaudio/csrc' (e.g. RNN-T loss).

Things in "examples" directory:

'recipe' is applicable to training recipes under the 'examples' folder,
'tutorial' is applicable to tutorials under the “examples/tutorials” folder
'example' is applicable to everything else (e.g. C++ examples)
'module: docs' is applicable to code documentations (not to tutorials).

Regarding examples in code documentations, please also use 'module: docs'.

Please use 'other' tag only when you’re sure the changes are not much relevant to users, or when all other tags are not applicable. Try not to use it often, in order to minimize efforts required when we prepare release notes.

When preparing release notes, please make sure 'documentation' and 'tutorials' occur as the last sub-categories under each primary category like 'new feature', 'improvements' or 'prototype'.

Things related to build are by default excluded from the release note, except when it impacts users. For example:

Drop support of Python 3.7.
Add support of Python 3.X.
Change the way a third party library is bound (so that user needs to install it separately).