From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Rick Huijzer" <ikbenrickhuyzer@gmail.com>, 72142@debbugs.gnu.org
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
Rick Huijzer <ikbenrickhuyzer@gmail.com>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Lars-Dominik Braun <lars@6xq.net>, Marius Bakke <marius@gnu.org>,
Tanguy Le Carrour <tanguy@bioneland.org>
Subject: [bug#72142] [PATCH v1] Fix formatting, boost not needed in python-rtmidi
Date: Thu, 18 Jul 2024 16:38:54 +0000 [thread overview]
Message-ID: <4db0c6bee26cf01e8c72bed6d3a2c53df6a8781e@dismail.de> (raw)
In-Reply-To: <09a92b6a22245646ca2b51ac5059c5fca54ee0f7.1721315431.git.ikbenrickhuyzer@gmail.com>
> + (inputs (list glibc python-cffi jack-2 rtmidi))
Hi, since this is a Python library, do we want to make the Python inputs propagated?
Were you able to test in a shell that the following works fine when run from a script or repl?
If not, can you test that and report back on the results. I'll give it a try after.
Or, how have you gone about testing that this package works in a Guix environment with all the system audio requirements?
```python
import time
import rtmidi
midiout = rtmidi.MidiOut()
available_ports = midiout.get_ports()
if available_ports:
midiout.open_port(0)
else:
midiout.open_virtual_port("My virtual output")
with midiout:
note_on = [0x90, 60, 112] # channel 1, middle C, velocity 112
note_off = [0x80, 60, 0]
midiout.send_message(note_on)
time.sleep(0.5)
midiout.send_message(note_off)
time.sleep(0.1)
del midiout
```
all best,
jgart
next prev parent reply other threads:[~2024-07-18 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:23 [bug#72142] [PATCH] add python-rtmidi Rick Huijzer
2024-07-18 15:10 ` [bug#72142] [PATCH v1] Fix formatting, boost not needed in python-rtmidi Rick Huijzer
2024-07-18 16:38 ` jgart via Guix-patches via [this message]
2024-07-18 20:54 ` [bug#72142] [PATCH] add python-rtmidi Rick Huijzer
2024-08-06 13:28 ` Rick Huijzer
2024-09-02 20:07 ` Rick Huijzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4db0c6bee26cf01e8c72bed6d3a2c53df6a8781e@dismail.de \
--to=guix-patches@gnu.org \
--cc=72142@debbugs.gnu.org \
--cc=ikbenrickhuyzer@gmail.com \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.