Open abavisani opened 11 months ago
The source code of soundfile clearly does have the SoundFileRuntimeError
defined. You could check what version of soundfile you received.
I just ran across this error myself. I mistakenly installed pysoundfile
rather than soundfile
. The old package name is at version 0.9.0 and SoundFileRuntimeError
was added in 0.11.
It's a tough call. I could replace pysoundcard with an incompatible stub to get people to update to soundcard. But I hate breaking other peoples' code for no reason.
Maybe put in a deprecation warning?
Deprecation warnings are hidden by default, which is a bit of a shame really. Or we just wait it out. Usage of pysoundfile has been slowly declining, so it's not a huge problem.
I could replace pysoundcard with an incompatible stub to get people to update to soundcard.
How about updating pysoundfile to be an empty package that depends on soundfile? If people need the old package, they could pin the version number, otherwise, they would get the recent version.
The reason, why I am suggesting this is: When you install first soundfile and then pysoundfile, pip says you have soundfile installed, but the source code is from pysoundfile (i.e., the old code). The first time, when I hit this issue, it took me some time to figure out, that the source code from soundfile was replaced by pysoundfile.
I am receiving the above error while using
librosa.load()
. Any thought on what's the root of the issue?