No fast pitch-shift ratios could be computed for the given sample rate and transpose range.
See original GitHub issueI use PitchShift wih min=-0.9 and max = 1.1, then it raise No fast pitch-shift ratios could be computed for the given sample rate and transpose range.
. I dont face with this error when use cpu version github. Do you have any plan to fix it?
Issue Analytics
- State:
- Created a year ago
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Issues · asteroid-team/torch-audiomentations - GitHub
Fast audio data augmentation in PyTorch. ... No fast pitch-shift ratios could be computed for the given sample rate and transpose range.
Read more >Pitch-shifting algorithm design and applications in music
Pitch-shifting lowers or increases the pitch of an audio recording. This technique has been used in recording studios since the 1960s, many Beatles...
Read more >pitch shifting - Katja
If a frequency is computed this way, it can be simply multiplied by the pitch shift factor to find the new frequency. This...
Read more >Question regarding proper method of real time pitch shifting
My goal is to pitch shift the wave sample (sound) up or down according ... But even with ultra-hifi perfect simple samplerate transposition, ......
Read more >Writing a Pitch Shift MetaSound Node - Epic Games Dev Portal
In this tutorial, I will write a new MetaSound node that performs a Doppler-Delay-based pitch shift on a real-time audio buffer.
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
That’s an interesting use case, AliKarimi95
Note: Although the pitch shift transform in torch-audiomentations can be comparatively fast on GPU, it is slow on CPU. When running pitch shift on CPU, the one in audiomentations is roughly 3x as fast.
Pitch shifts are generally pretty intensive operations so I’m not too surprised about the increase in execution time. Regarding speed issues with some pitch shift factors, unfortunately some factors aren’t ideal for speed, so the rate of data transfer to the GPU becomes the bottleneck. In your specific case, it may be better to apply cpu-based pitch shift instead.