Skip to content

Add support for get_client_name() and get_client_id() to engine#17

Open
MaurizioB wants to merge 1 commit intodsacre:masterfrom
MaurizioB:master
Open

Add support for get_client_name() and get_client_id() to engine#17
MaurizioB wants to merge 1 commit intodsacre:masterfrom
MaurizioB:master

Conversation

@MaurizioB
Copy link

I added support for mididings.engine.get_client_name() which returns the unique name of the mididings
sequencer engine (useful for unique jack names) and mididings.engine.get_client_id() which returns the client port number (ALSA) or client UUID (JACK) which in turn is useful for ALSA non-unique nature.
This is obviously not very useful for mididings only scripts, but for programs which use it as a module.
I have to make an apology: I know very little about programming, and, most important, I know almost nothing about c++. The code added looks "clean" and it works (at least on my machine), but I might have done things in a unorthodox way...

mididings.engine.get_client_name() will return the unique name of the mididings
sequencer engine, expecially useful for jack, which uses unique names for
clients and thus will add "-01" (02, 03, ...) to the client_name set in the
mididings.config().

mididings.engine.get_client_id() will return the client port number (ALSA) or
client UUID (JACK), which is useful for ALSA, which instead allows clients with
the same name. The result is an integer for ALSA, while for JACK is usually a
(long) integer, but there's support for strings too (jack returns the UUID as
a string, I actually don't know why).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant