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

Fix MidiJackGetEndpointName() for 64-bit Windows #38

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cdwfs
Copy link

@cdwfs cdwfs commented Feb 9, 2019

The old DeviceIdToHandle() truncated the top 32 bits, yielding an
invalid/unknown handle. The handles are now cached in a lookup map,
accessible by DeviceID.

Fixes #37

The old DeviceIdToHandle() truncated the top 32 bits, yielding an
invalid/unknown handle. The handles are now cached in a lookup map,
accessible by DeviceID.
@cdwfs cdwfs changed the title Fix MidiJackGetEndpointName() for 64-bit Windows (fixes #37) Fix MidiJackGetEndpointName() for 64-bit Windows Feb 9, 2019
@keijiro keijiro self-assigned this Feb 10, 2019
@krovma
Copy link

krovma commented Oct 6, 2019

An easy and ugly fix if you don't want to cache the handles:
MidiJackGetEndpointName((uint)index);

krovma referenced this pull request in krovma/MidiJack Oct 6, 2019
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.

MidiJackGetEndpointName() can return "unknown" for valid handles on 64-bit Windows
3 participants