🔗 Helpful Links

🧪 See artifacts and rendered test results athud.pytorch.org/pr/pytorch/audio/3916

• 📄 PreviewPython docs built from this PR

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

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

hi@seemethere, can we get a review on this one as well? thanks!

@seemethere ,@malfet - can you please help us close on the workflow? Or do you know somebody that can help us approve the changes?

Sorry folks I don't think we'll be able to merge this anytime soon. We're in the process of a large re-factoring of torchaudio, and we won't be able to add new CI jobs or platforms support in the short-medium term (#3902)

Hi@NicolasHug, thanks for the update. Now that PyTorch for Windows on Arm is officially supported, we're working on expanding the ecosystem by adding support for vision and audio as well. We prioritized these two packages because they are included in the installation commands on the official PyTorch website. Since torchaudio is going to be refactored, we wanted to check if there’s a timeline or expected completion date for that work. Also, during the refactoring period, will torchaudio still be included in the installation instructions, or will users be directed to use torchcodec or some other alternative instead? Our goal is to ensure that the same packages are available for Windows Arm64 as on the other platforms, so we'd like to identify which ones need additional support for that.

We aim to complete the migration by the end of 2025. We will probably remove torchaudio from the official installing instructions, but that's still in discussion.

thanks@NicolasHug for the follow up. As@alinpahontu2912 mentioned above, our goal is to ensure that same packages are available on Windows Arm64 as on the other platforms on the default PyTorch installation. We published PyTorch support for Windows on Arm64 inApril this year, and the remaining work was to have TorchVision and TorchAudio supported there as well, as they are listed as default packages for installation and critical libs for community.

We spend a lot of effort for this work to have it ready, and the only remaining item now is to merge the workflow here, to integrate in the CI. Do you think this can be something that is possible to be approved now?

Hi@alinpahontu2912@aalina23 , we'll try to remove torchaudio from the official installation instructions (https://pytorch.org/get-started/locally/) for the next 2.8 release planned this summer. Does this allow you to re-consider whether you'll need to support torchaudio?

Hi@alinpahontu2912@aalina23 , we'll try to remove torchaudio from the official installation instructions (https://pytorch.org/get-started/locally/) for the next 2.8 release planned this summer. Does this allow you to re-consider whether you'll need to support torchaudio?

Yes@NicolasHug - this will help us, thank you :)