Bug: AddBackgroundNoise does not support CUDA.
See original GitHub issueI am getting RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:2 and cpu!
.
I send my audio to cuda:2 and pass it to the augmentor and I get the error above. Same problem with Rirs. I also tried to send the augmentor itself to GPU, but this did not help. Is this a known issue?
`
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
asteroid-team/torch-audiomentations: Fast audio data ... - GitHub
PitchShift does not support small pitch shifts, especially for low sample rates ... Fix a bug where AddBackgroundNoise did not work on CUDA;...
Read more >CUDA Compatibility :: NVIDIA Data Center GPU Driver ...
This error indicates that the system was upgraded to run with forward compatibility but the visible hardware detected by CUDA does not support...
Read more >Install TensorFlow with pip
Note: TensorFlow binaries use AVX instructions which may not run on older CPUs. The following GPU-enabled devices are supported: NVIDIA® GPU card with...
Read more >Why `torch.cuda.is_available()` returns False even after ...
Your graphics card does not support CUDA 9.0. Since I've seen a lot of questions that refer to issues like this I'm writing...
Read more >Bug with Julia 1.7.1 and CUDA 3.3 - GPU
Unfortunately this is not the case with the latest version of Julia 1.7.1. ... CUDA 11.2.0) Toolchain: - Julia: 1.6.5 - LLVM: 11.0.1...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
v0.5.1 is released on PyPI
Hey thanks for swift response! 😃 I double checked the RIRs and the problem was on my side. Sorry for the chaos. Are you going to do a new pip release with the fix soon? If no, is it possible to simply install master with
pip install <this repo installable url>
?