Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Writing to ogg crashes Python
See original GitHub issueWindows 10 x64, Python 3.8.1. PySoundFile installed with pip install pysoundfile.
With Python’s interactive interpreter from the command line (directly typing python in cmd), I opened an ogg file (about 37 seconds long, sample rate 48000, 6 channels), and wrote the same data back to another ogg. This caused python to exit without printing any error message. Writing the same data to a wav file does not cause any error whatsoever.
If there is any other information I need to provide to help solve the issue, please let me know 😕
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Does the problem occur for any kind of ogg file, or is it specific to this data or sample rate or number of channels?
At any rate, this problem is likely a bug in libsndfile, not SoundFile.
This sounds like there is a conflict between a version of libvorbis loaded by Qt and by libsndfile. Conflicts such as these are colloquially known as “DLL Hell”. Essentially, C libraries export a list of symbols (functions, constants, etc), and if you load a C library twice, only one set of symbols can be active. If you load two different versions of the library, you have a problem.