Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No port names on ALSA #88

Closed
aib opened this issue Sep 14, 2016 · 3 comments
Closed

No port names on ALSA #88

aib opened this issue Sep 14, 2016 · 3 comments

Comments

@aib
Copy link
Contributor

aib commented Sep 14, 2016

On ALSA (asound), port names returned are of the form <client name> <client id>:<port id>. The cid:pid pair is unique, but this makes it hard to look for ports by name. Mentioned in #54, but I thought it would be better to move the discussion here.

@aib
Copy link
Contributor Author

aib commented Sep 14, 2016

Using these samples:

RtMidiOut midiOut;
midiOut.openVirtualPort("Testing123");
RtMidiIn midiIn;
for (unsigned int i=0; i<midiIn.getPortCount(); ++i) {
    std::cout << midiIn.getPortName(i) << std::endl;
}

I get,
on Jack: RtMidi Output Client:Testing123
on ALSA: RtMidi Output Client 129:0

By the way, what do the outputs look like in Windows and Mac OSX?

@jeffreykog
Copy link

Can confirm that the names on OSX are the same names as entered when creating the virtual device. Looks like it's only an alsa issue

@radarsat1
Copy link
Contributor

Just tested on ALSA and it seems for me that midiprobe is able to detect the virtual port opened in another process without issues. Assuming fixed.

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

No branches or pull requests

3 participants