conn_jack
Classes for managing jack client connections.
These differ from the JACK Client for Python (jack), in that it makes possible connecting and disconnecting ports which are not "owned" by a client created in your process.
There is also an (optionally installed) QtJackConnectionManager which emits signals when events of interest happen. In order to use the QtJackConnectionManager class, you must install with the "[Qt]" option, like so:
$ pip install conn_jack[Qt]
Using the plain (non-Qt) version
Import JackConnectionManager:
from conn_jack import JackConnectionManager
Create an instance using standard constructor syntax ...
self.conn_man = JackConnectionManager()
... or use it as a context manage:
with JackConnectionManager() as conn_man:
The non-Qt version uses callbacks to inform your program when events of interest happen. Register your functions as callbacks using the "on_" methods:
self.conn_man.on_client_registration(self.jack_client_reg)
self.conn_man.on_port_registration(self.jack_port_reg)
self.conn_man.on_shutdown(self.close)
Using the Qt version:
In order to use the Qt version, you must import "QtJackConnectionManager" from the conn_jack.qt module.
from conn_jack.qt import QtJackConnectionManager
self.conn_man = QtJackConnectionManager(client_name = "DescriptiveClientName")
The Qt version forsakes callbacks for the Qt signal/slot mechanism. To subscribe to signals which are generated on events of interest:
self.conn_man.sig_client_registration.connect(self.slot_client_registration)
self.conn_man.sig_port_registration.connect(self.slot_port_registration)
self.conn_man.sig_shutdown.connect(self.slot_shutdown)
Refer to the help text to determine the function arguments to use in the callbacks or slots.
Help
Refer to the help for conn_jack. From python:
>>> import conn_jack
>>> help(conn_jack)
>>> import conn_jack.qt
>>> help(conn_jack.qt)
Metadata
Release files for conn-jack 1.3.3
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 | |
|---|---|---|---|---|
| conn_jack-1.3.3.tar.gz | 18.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conn_jack-1.3.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 35.6 kB
Release files / conn_jack-1.3.3.tar.gz
| Download URL | conn_jack-1.3.3.tar.gz |
|---|---|
| Size | 18.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e0beb6b0fbe0b3735aad4bf0ea780d8c193182b68414575f39d16affbdc1976
|
|
BLAKE2b-256 checksum How to use checksums |
a7814d9b675aa1e497e16d04611b3731cbf32624f9b181cf60096dc7b16c0574
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / conn_jack-1.3.3-py2.py3-none-any.whl
| Download URL | conn_jack-1.3.3-py2.py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
99363e4a13d740b94d0c4a8635f9376716dd7db7600a0e3ef6929439dbb51fc5
|
|
BLAKE2b-256 checksum How to use checksums |
5ba76ee97ef125ea1845289e5e5dcbe00fbfd85122d3f51c4cc6a1c37bb9dfce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for conn-jack 1.3.3
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.