File: index.rst

package info (click to toggle)
python-mido 1.3.3-0.2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 920 kB
  • sloc: python: 4,006; makefile: 127; sh: 4
file content (120 lines) | stat: -rw-r--r-- 3,041 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
.. SPDX-FileCopyrightText: 2017 Ole Martin Bjorndalen <ombdalen@gmail.com>
..
.. SPDX-License-Identifier: CC-BY-4.0

Backends
========

A backend provides the interface between Mido and the operating system level
MIDI stack.

Some Mido features are only available with select backends.

Mido's backend subsystem has been designed to be extensible so you can add
your own backends if required. See :doc:`custom`.

Providing platform specific Python-native backends is currently evaluated.
See: https://github.com/mido/mido/issues/506

.. todo:: Insert a stack diagram to clear things up.


Choice
------

Mido comes with five backends:

* :doc:`RtMidi <rtmidi>` is the *default* and *recommended* backend. It has all
  the features of the other ones and more plus it is usually easier to install.

* :doc:`PortMidi <portmidi>` was the default backend up until version 1.2. It
  uses the ``portmidi`` shared library and can be difficult to install on some
  systems.

* :doc:`Pygame <pygame>` uses the ``pygame.midi`` module.

* :doc:`rtmidi-python <rtmidi_python>` uses the ``rtmidi_python`` package, an
  alternative wrapper for PortMidi. It is currently very basic but
  easier to install on some Windows systems.

* :doc:`Amidi <amidi>` is an experimental backend for Linux/ALSA
  that uses the command ``amidi`` to send and receive messages.

You can set the backend using an environment variable: See :ref:`env_vars`.

Alternatively, you can set the backend from within your program::

    >>> mido.set_backend('mido.backends.portmidi')
    >>> mido.backend
    <backend mido.backends.portmidi (not loaded)>

.. note::

    This will override the environment variable.

If you want to use more than one backend at a time, you can do::

    rtmidi = mido.Backend('mido.backends.rtmidi')
    portmidi = mido.Backend('mido.backends.portmidi')

    input = rtmidi.open_input()
    output = portmidi.open_output()
    for message in input:
        output.send(message)

The backend will not be loaded until you call one of the ``open_`` or
``get_`` methods. You can pass ``load=True`` to have it loaded right
away.

If you pass ``use_environ=True``, the module will use the environment
variables ``MIDO_DEFAULT_INPUT`` etc. for default ports.


.. _env_vars:

Environment Variables
---------------------


Select Backend
^^^^^^^^^^^^^^

If you want to use a backend other than RtMidi you can override this with
the ``MIDO_BACKEND`` environment variable, for example::

    $ MIDO_BACKEND=mido.backends.portmidi ./program.py


Set Default ports
^^^^^^^^^^^^^^^^^

You can override the backend's choice of default ports with these
three environment variables::

    MIDO_DEFAULT_INPUT
    MIDO_DEFAULT_OUTPUT
    MIDO_DEFAULT_IOPORT

For example::

    $ MIDO_DEFAULT_INPUT='SH-201' python3 program.py

or::

    $ export MIDO_DEFAULT_OUTPUT='Integra-7'
    $ python3 program1.py
    $ python3 program2.py


Available Backends
------------------

.. toctree::

   rtmidi
   portmidi
   pygame
   rtmidi_python
   amidi

.. include:: custom.rst