Stuck on an issue?
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.
data format in write docstring
See original GitHub issueWhen using write, I was getting a RuntimeError: Error opening 'output.wav': Format not recognised.. I think this was because I had arranged my data as (channels, frames), based on my reading of the docstring (which says “Usually two-dimensional (channels x frames)”). It seems to expect the data in (frames, channels) format instead.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Python Docstrings Tutorial : Examples & Format for Pydoc ...
See Python Docstrings. Learn about the different types of docstrings & various docstring formats like Sphinx, Numpy, and Pydoc with examples now.
Read more >How to Use Python Docstrings for Effective Code Documentation
Documenting your code is a critical skill for any data scientist or software engineer. This tutorial will show you how using docstrings.
Read more >Writing docstrings — Sphinx-RTD-Tutorial documentation
For this tutorial we will use the Sphinx format, since, as the name suggests, it is the standard format used with Sphinx.
Read more >Python Docstrings (With Examples) - Programiz
Python docstrings are the string literals that appear right after the definition of a function, method, class, or module. Let's take an example....
Read more >Python Docstring: Documenting And Introspecting Functions
The docstring format used above is the NumPy/SciPy-style format. Other formats also exist, we can also create our format to be used by...
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 Free
Top 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
Thanks, Bastian! Version that Colab imports is 0.10.3
Using audio2 = audio.transpose() fixes the issue. This may just be a problem with what Colab is importing?
Audio data can be frame x channels or channels x frames. Different shapes for different applications.