Fix apply_codec to use named file

[mthrok]

Follow-up #3386 The intended change was to use path of temporary file, instead of file-like object

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 5 New Failures

As of commit 15c24e3:

NEW FAILURES - The following jobs have failed:

• build (3.8) (gh)
• Check whether the docstring parameters are in-sync (gh)
• Stylecheck (gh)
• tests / macos-job (gh)
• unittests-windows-gpu / windows-job (gh)

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

[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]

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

[facebook-github-bot]

@mthrok merged this pull request in 1dfac46.

[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).

[vadimkantorov]

Would it be possible to introduce some sort of backend= argument for this function? If I understand, SoX is going to be gradually replaced by ffmpeg in torchaudio, so letting a way for being explicit is a good thing (same as specifying backend for torchaudio.load)

Ah, I see that it's now deprecated in favor of AudioEffector which only supports ffmpeg: #3386

If still SoX has useful effects/codecs, adding explicit backend= option to AudioEffector would be great

[mthrok]

If still SoX has useful effects/codecs, adding explicit backend= option to AudioEffector would be great

The syntax and semantics of those sox effect chain and FFmpeg's filter graph are different, so unifying them is not straightforward. I think users can create such wrapper that suit their requirement and constraints if necessary.