Fix resampling to support dynamic input lengths for onnx exports.

[bogdanteleaga]

This is a port of adefossez/julius#17 for torchaudio.

Not sure if it's possible/desirable to add tests to test the functionality of ONNX exports, but I did a quick test on my machine to ensure this works. The logic is a bit simpler compared to the other PR because the torchaudio version does not support the additional flags available in julius.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/audio/3473

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures

As of commit 39f34d9:

NEW FAILURES - The following jobs have failed:

• build (3.8) (gh)
• tests (3.10) / linux-job (gh)
• tests (3.8) / linux-job (gh)
• tests (3.9) / linux-job (gh)

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

[mthrok]

Hi @bogdanteleaga

Thanks for the PR. The change looks good to me.

Regard the testing and ONNX support guarantee, in general, we do not make any promise about ONNX compatibility in torchaudio.

I do not anticipate to change resample code anytime soon, but if you can add a test, then we will try out best to not break it.

[facebook-github-bot]

@mthrok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@mthrok merged this pull request in a3b6bfb.

[github-actions]

Hey @mthrok.
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).

[bogdanteleaga]

@mthrok
I don't mind leaving it as is. Adding a test means onnxruntime would have to become a test-time dependency as well so it might break some additional workflows. Let me know if you'd like a test though and I can look into it.