IssueRaiser

Update on TorchAudio’s future

EDIT from 2026/01/22: we just released TorchAudio 2.10, which marks the completion of the migration detailed below. Based on user feedback, one important modification was made to the original plan: lfilter, RNNTLoss, CUCT, forced_align, and overdrive, which were originally slated for deprecation and deletion, **have been preserved**. See https://github.com/pytorch/audio/issues/3902#issuecomment-3779752106. ---- Dear TorchAudio users, TorchAudio is the most popular audio library for PyTorch. It has critical transforms, models and datasets that we know the community relies on. That is why we wanted to let the community know that we have started a refactoring effort to transition TorchAudio into a **maintenance phase**. This process will involve **removal of some user-facing features**. We have three goals we want to achieve with this effort: 1. **Make TorchAudio easier to maintain to ensure long-term reliability.** We plan to eliminate all C++ code so that TorchAudio is a Python-only library. We also plan to reduce external dependencies as much as possible. Both efforts will simplify testing and release. 2. **Reduce redundancies with the rest of the PyTorch ecosystem.** Some of the functionality in TorchAudio is also available in TorchVision and TorchCodec. We are working across all three libraries to ensure a given capability lives in one library. 3. **Focus on TorchAudio’s strengths.** Those strengths are the audio transforms, models and datasets that are integral to user

Posted by scotts on Apr 24, 2025, 2:20 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Software)

Update on TorchAudio’s future

scottsApr 24, 2025, 2:20 PM

EDIT from 2026/01/22: we just released TorchAudio 2.10, which marks the completion of the migration detailed below. Based on user feedback, one important modification was made to the original plan: lfilter, RNNTLoss, CUCT, forced_align, and overdrive, which were originally slated for deprecation and deletion, **have been preserved**. See https://github.com/pytorch/audio/issues/3902#issuecomment-3779752106. ---- Dear TorchAudio users, TorchAudio is the most popular audio library for PyTorch. It has critical transforms, models and datasets that we know the community relies on. That is why we wanted to let the community know that we have started a refactoring effort to transition TorchAudio into a **maintenance phase**. This process will involve **removal of some user-facing features**. We have three goals we want to achieve with this effort: 1. **Make TorchAudio easier to maintain to ensure long-term reliability.** We plan to eliminate all C++ code so that TorchAudio is a Python-only library. We also plan to reduce external dependencies as much as possible. Both efforts will simplify testing and release. 2. **Reduce redundancies with the rest of the PyTorch ecosystem.** Some of the functionality in TorchAudio is also available in TorchVision and TorchCodec. We are working across all three libraries to ensure a given capability lives in one library. 3. **Focus on TorchAudio’s strengths.** Those strengths are the audio transforms, models and datasets that are integral to user

Comments (0)

No comments yet. Start the discussion.

Comment on this issue