-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experimental windows builds #219
Conversation
Signed-off-by: Edward Z. Yang <ezyang@fb.com>
Signed-off-by: Edward Z. Yang <ezyang@fb.com>
Signed-off-by: Edward Z. Yang <ezyang@fb.com>
Signed-off-by: Edward Z. Yang <ezyang@fb.com>
Signed-off-by: Edward Z. Yang <ezyang@fb.com>
@ezyang I believe this repo is not Windows-ready because it relies on sox that cannot be built statically. |
Yeah, I think I agree |
Maybe use socket of |
This is not a good idea. First, it requires users to install WSL. It's a win 10 only feature. Second, if there's WSL, why don't we just run code in WSL? Nevertheless, it may be helpful if you want to use native libraries with torchaudio. But apparently, this is not something we should do here. |
Because it still has no CUDA support. |
@black-snow They actually announced that several days ago. But the discussion here is rather old. We have torchaudio nightly packages for Windows now. As for torchaudio with sox, you can see #648. |
Thanks for the reply. Yes they did but only for WSL2 and for that you still have to be on insider/fast-ring (although the may update should be out soon). How do I get the nightly? For now, I only need torchaudio.datasets (which uses |
|
Addressed by #1345 |
cc @peterjc123
Signed-off-by: Edward Z. Yang ezyang@fb.com