Is this library maintained? #373

debris · 2018-01-17T10:57:48Z

Latest commit to master was almost 2 years ago, and latest release was over 4 years ago. Is anyone looking after this library? If not, can push access be granted to some volunteers?

jonathancross · 2018-01-22T01:45:24Z

Sadly, looks like the answer is "no". @signal11 isn't doing much on GitHub, 128 open issues, 49 PRs and no commits since 2016.

Youw · 2018-01-29T08:57:01Z

If we don't hear from author within reasonable time - it could mean, that this repo is abandoned.
And it is not good, since there is more and more forks and no true, well maintained library.

On the other hand, there is a comment from author on 15 Nov 2017. At least he's still here.

ulao · 2018-01-31T18:02:36Z

I find this one to work best. I really wish the author would still check in from time to time.

todbot · 2018-02-03T19:48:10Z

This library is sort of a thankless task. I wouldn't mind if more active collaborators were present. I notice this library has a lot of forks with changes. Perhaps some of those people could help out?

ulao · 2018-02-03T20:06:01Z

I asked single11 to come back and he did for a few question. So I'd expect he may come back yet again. Though I agree we just need more activity. This is why I deiced to answer am many questions as I could. I didn't write any of this code but I sure have used it for a long while in a straight run. IMO it is one of the best for c#.

jdk · 2018-02-11T16:53:40Z

Yes, this library is still active. todbot is right.

I've connected with Alan and will be doing my best to join in and help him where I can as another contributor.

There are a lot of branches. One thing to note is that many of them added fixes for their specific situation without doing due diligence for every scenario, kernel, hardware version. But I hope to make this less of an issue as time goes on.

mickeyl · 2018-03-01T11:42:31Z

@jdk Great, thanks for this commitment. It would be a shame to see this library unmaintained, since there are hardly any other cross-platform alternatives.

Be-ing · 2018-06-22T17:48:00Z

@signal11, maybe you could give @jdk write access to this repository?

jdswensen · 2018-08-02T23:41:33Z

If write access was given to someone (@jdk?) and a plan was put in place to begin resolving issues, I would be interested in helping. I need a cross platform HID (mac/win) layer for a work project, so I'll probably be forking this to fix any issues I encounter during that process. I would like to submit contributions/fixes, but it doesn't look like PRs have been merged or rejected in a while. If I'm gonna go through the pain of fixing stuff, I would rather share it on this repo rather than having it live forever on my own fork.

I'd also be willing to perform reviews of the existing PRs and to help manage merging known fixes (or rejecting erroneous ones).

jdk · 2018-08-03T05:35:12Z

@jdswensen unfortunately, I haven't heard from Alan in a while. = (

mcuee · 2018-08-03T05:50:11Z

@jdk Let me try to contact Alan as well. HIDAPI is a great library and we at libusb project recommends HIDAPI over libusb for HID device.

Ref: https://github.com/libusb/libusb/wiki/FAQ#Does_libusb_support_USB_HID_devices

jdswensen · 2018-08-03T16:12:33Z

@mcuee,
If you can't get a hold of Alan, would it be possible for libusb to host a fork? I think the biggest issue for maintaining the library is to have a rally point for discussion and development. If someone can't get access to this one, the community will need something else. libusb seems like a natural choice given that the project already has an established reputation and are actively recommending libusb users to consider using hidapi.

mcuee · 2018-08-04T12:11:49Z

@jdswensen
I do not see a problem using libusb mailing list for discussions related to HIDAPI. In fact, there were quite some HIDAPI related discussions there.

However, I am not so sure about hosting a fork under libusb. I will wait for Alan's response and then check with other libusb admins.

mcuee · 2018-08-10T09:07:16Z

BTW, I've seen the fork with many activities here. Maybe people can start to use this fork to see if it helps.
https://github.com/supercollider/hidapi

On the other hand the intention is a bit different.
supercollider/supercollider#3559

The extensions for SC on the hidapi library are quite substantial,
involving the parsing of the hid descriptor.
The purpose of the original hidapi library was more toward custom-made
devices for which people would write their own software to read, so our
extensions are also unlikely to fit into the purpose of the hidapi library.

Qbicz · 2019-01-10T10:09:21Z

Hi Contributors. It is 2019, if there is no chance to get write access from @signal11 maybe it's time to host the library on libusb and start integrating fixes for known issues? What do you think @mcuee?

This is a great cross-platform library used by a lot of people and it would be good to clean up the situation of many forks fixing different issues.

I'm also willing to help in fixing/reviews.

jonathancross · 2019-01-10T13:09:09Z

Here is contact info if someone wants to give him a call: http://www.signal11.us/contact.html

mcuee · 2019-01-17T13:14:55Z

@Qbicz
You may want to ask in libusb-devel mailing list to see how others look at this.

Qbicz · 2019-06-03T11:58:41Z

Hello again! I have asked on libusb mailing list if libusb can host this project. We received positive response from @LudovicRousseau.

Now we need a list of volunteers who would like to help in maintaining the library. @mcuee @jdk @jdswensen @jonathancross @todbot @ulao @debris @Youw, please confirm if you would like to volunteer.

Qbicz · 2019-06-03T12:02:19Z

Also if you know about other contributors who would like to join maintainers, please tell.

Youw · 2019-06-03T17:03:59Z

I don't mind helping out from time to time.

todbot · 2019-06-03T18:04:06Z

@Qbicz Confirm I would like to volunteer on maintaining hidapi. I'm a maintainer of node-hid (a dependent of hidapi) and have a product that uses hidapi. So I'm motivated to make hidapi work. Just this weekend I was considering forking and adding all the PRs just to see what would happen.

I have a small collection of USB HID devices I currently test against. If there are specific ones that are a concern to the community (and they're not prohibitively expensive), I'd be happy to expand that collection.

z3ntu · 2019-06-03T18:32:29Z

Just to add my 2 cents: I consider these PRs top-priority once a new tree emerges :) : #335 #380 #219

Thanks in advance!

kloczek · 2019-06-04T07:59:23Z

Maybe someone commenting here can clone repo and start maintain fork?

LudovicRousseau · 2019-06-04T20:46:00Z

Done.
See https://github.com/libusb/hidapi

This release was taken over by the libusb team. See <signal11/hidapi#373>. * gnu/packages/libusb.scm (hidapi): Update to 0.9.0. [source, home-page]: Switch to new upstream.

mcuee · 2021-01-26T05:27:45Z

Just popping up this one. This repo is not longer maintained. Please use the new one. Thanks.
https://github.com/libusb/hidapi

kloczek · 2021-01-26T13:04:07Z

OK thx.

…pen_path (signal11#373) Fixes a segfault that happens when hid_open_path is called on a previously disconnected device. This is a regression caused by: b600727 - Win32: Fix memory leak in `free_hid_device` (signal11#361) Co-authored-by: Megamouse <studienricky89@googlemail.de>

todbot mentioned this issue Apr 17, 2018

Is this repo being actively maintained? #391

Open

debris mentioned this issue Jul 10, 2018

use parity fork of hidapi paritytech/hidapi-rs#5

Merged

duncan-bayne mentioned this issue Nov 15, 2018

Build produces compiler warning on FreeBSD 11.2 todbot/blink1-tool#16

Closed

s-light mentioned this issue May 3, 2019

[featurerequest] cross-platform support?! jnweiger/led-name-badge-ls32#2

Closed

z3ntu mentioned this issue Jun 3, 2019

Any plans to make new release soon? #429

Open

Youw mentioned this issue Jun 4, 2019

Explicit cast from void* to corresponding type #430

Open

Youw mentioned this issue Jul 25, 2019

Why did the call to hid_open () fail? #437

Open

This was referenced Aug 9, 2019

Switch to libusb branch of hidapi trezor/cython-hidapi#64

Merged

mac: fix behaviour of hid_get_feature_report #219

Open

Youw mentioned this issue Aug 20, 2019

Please target new pull requests to libusb/hidapi #431

Open

Youw mentioned this issue Sep 11, 2019

Is the project still under maintenance #441

Closed

Youw mentioned this issue Oct 28, 2019

hidDevice.open() return NULL #442

Open

This was referenced Nov 8, 2019

licensing: How can hidapi be used in a lgpl program? #444

Open

Not able to open device (in dynamic mode) #445

Open

Youw mentioned this issue Nov 18, 2019

libusb: allow hidapi to be configured without using iconv #447

Open

This was referenced Dec 5, 2019

Windows: enumerate a specific list of vendor/product ids #448

Closed

unable to use hid in kivy python mobile application #449

Open

This was referenced Jan 5, 2020

Unable to open device (access denied) #450

Closed

hid_write return -1 on linux #451

Open

mbakke pushed a commit to guix-mirror/guix that referenced this issue Jan 18, 2020

gnu: hidapi: Update to 0.9.0.

7f6592c

This release was taken over by the libusb team. See <signal11/hidapi#373>. * gnu/packages/libusb.scm (hidapi): Update to 0.9.0. [source, home-page]: Switch to new upstream.

Youw mentioned this issue Feb 11, 2020

Add MacOS Entitlments info to readme #452

Closed

This was referenced Mar 8, 2020

failed to open the device #454

Closed

hid_read returns 0 on Windows Platforms, on Mac and Linux works fine #350

Closed

Youw mentioned this issue Apr 30, 2020

some HID messages sent by the device are missing on windows #457

Open

todbot mentioned this issue May 13, 2020

Hardened runtime using hidapi under macOS Catalina #458

Open

Youw mentioned this issue Jun 13, 2020

hid_read hang in linux, but hid_write and hid_read work fine in window10 #459

Closed

Youw mentioned this issue Oct 23, 2020

Converting to HANDLE from hid_device #463

Open

Youw mentioned this issue Nov 15, 2020

Mac: hid_open_path in non exclusive mode #453

Open

Youw mentioned this issue Nov 22, 2020

Failed to compile openocd due to missing void parameter in prototypes #464

Open

Youw mentioned this issue Dec 18, 2020

Segmentation Fault when using hidapi with MCP2111a #465

Closed

Youw mentioned this issue Jan 20, 2021

Windows version doesn't enumerate devices when exactly one is connected #466

Closed

Qbicz mentioned this issue May 11, 2021

REPO NOT MAINTAINED - please see libusb/hidapi #468

Open

liamjm mentioned this issue Oct 29, 2021

Migrate hidapi to its new github location google/u2f-ref-code#186

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Is this library maintained? #373

Is this library maintained? #373

debris commented Jan 17, 2018

jonathancross commented Jan 22, 2018 •

edited

Loading

Youw commented Jan 29, 2018 •

edited

Loading

ulao commented Jan 31, 2018

todbot commented Feb 3, 2018

ulao commented Feb 3, 2018 •

edited

Loading

jdk commented Feb 11, 2018

mickeyl commented Mar 1, 2018

Be-ing commented Jun 22, 2018

jdswensen commented Aug 2, 2018

jdk commented Aug 3, 2018

mcuee commented Aug 3, 2018

jdswensen commented Aug 3, 2018

mcuee commented Aug 4, 2018

mcuee commented Aug 10, 2018

Qbicz commented Jan 10, 2019

jonathancross commented Jan 10, 2019

mcuee commented Jan 17, 2019

Qbicz commented Jun 3, 2019

Qbicz commented Jun 3, 2019

Youw commented Jun 3, 2019

todbot commented Jun 3, 2019

z3ntu commented Jun 3, 2019

kloczek commented Jun 4, 2019

LudovicRousseau commented Jun 4, 2019

mcuee commented Jan 26, 2021

kloczek commented Jan 26, 2021

Is this library maintained? #373

Is this library maintained? #373

Comments

debris commented Jan 17, 2018

jonathancross commented Jan 22, 2018 • edited Loading

Youw commented Jan 29, 2018 • edited Loading

ulao commented Jan 31, 2018

todbot commented Feb 3, 2018

ulao commented Feb 3, 2018 • edited Loading

jdk commented Feb 11, 2018

mickeyl commented Mar 1, 2018

Be-ing commented Jun 22, 2018

jdswensen commented Aug 2, 2018

jdk commented Aug 3, 2018

mcuee commented Aug 3, 2018

jdswensen commented Aug 3, 2018

mcuee commented Aug 4, 2018

mcuee commented Aug 10, 2018

Qbicz commented Jan 10, 2019

jonathancross commented Jan 10, 2019

mcuee commented Jan 17, 2019

Qbicz commented Jun 3, 2019

Qbicz commented Jun 3, 2019

Youw commented Jun 3, 2019

todbot commented Jun 3, 2019

z3ntu commented Jun 3, 2019

kloczek commented Jun 4, 2019

LudovicRousseau commented Jun 4, 2019

mcuee commented Jan 26, 2021

kloczek commented Jan 26, 2021

jonathancross commented Jan 22, 2018 •

edited

Loading

Youw commented Jan 29, 2018 •

edited

Loading

ulao commented Feb 3, 2018 •

edited

Loading