Mido is a library for working with MIDI messages and ports:
>>> import mido
>>> msg = mido.Message('note_on', note=60)
>>> msg.type
'note_on'
>>> msg.note
60
>>> msg.bytes()
[144, 60, 64]
>>> msg.copy(channel=2)
Message('note_on', channel=2, note=60, velocity=64, time=0)port = mido.open_output('Port Name')
port.send(msg)with mido.open_input() as inport:
for msg in inport:
print(msg)mid = mido.MidiFile('song.mid')
for msg in mid.play():
port.send(msg)Full documentation at https://mido.readthedocs.io/
Main Features
works in Python 3.
convenient message objects.
supports RtMidi, PortMidi and Pygame. New backends are easy to write.
full support for all 18 messages defined by the MIDI standard.
standard port API allows all kinds of input and output ports to be used interchangeably. New port types can be written by subclassing and overriding a few methods.
includes a reusable MIDI stream parser.
full support for MIDI files (read, write, create and play) with complete access to every message in the file, including all common meta messages.
can read and write SYX files (binary and plain text).
implements (somewhat experimental) MIDI over TCP/IP with socket ports. This allows for example wireless MIDI between two computers.
includes programs for playing MIDI files, listing ports and serving and forwarding ports over a network.
Status
1.2 is the third stable release.
Requirements
Mido requires Python 3.7 or higher.
Installing
python3 -m pip install mido
If you want to use ports:
python3 -m pip install python-rtmidi
See docs/backends/ for other backends.
Source Code
License
Mido is released under the terms of the MIT license.
Questions and suggestions
For questions and proposals which may not fit into issues or pull requests, we recommend to ask and discuss on Discussions.
Release files for midoTrim 1.2.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| midoTrim-1.2.10.tar.gz | 104.6 kB | Without provenance | Details for midoTrim-1.2.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| midoTrim-1.2.10-py3-none-any.whl | Python 3 | none | any | Details for midoTrim-1.2.10-py3-none-any.whl |
Total release size: 154.7 kB
Release files / midoTrim-1.2.10.tar.gz
| Download URL | midoTrim-1.2.10.tar.gz |
|---|---|
| Size | 104.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67644db43b3fb69d1d3c1204f3730c2cfa586a1fd410e42984bb517c76ee2539
|
|
BLAKE2b-256 checksum How to use checksums |
089022390bfab2dac39dc7f27bf55929645629d20b122ba0f95b2cf5214e22fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Release files / midoTrim-1.2.10-py3-none-any.whl
| Download URL | midoTrim-1.2.10-py3-none-any.whl |
|---|---|
| Size | 50.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef7657f8ea70699f9fad576c96dcc7a401bd2885cc73097e3ed65b24c7fb4336
|
|
BLAKE2b-256 checksum How to use checksums |
cd33f664f6d646fcc86116cb4a5bfa9689d184a5d4b44755a62a28f2d23cb88e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Security for midoTrim 1.2.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
