RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[darktable] Reduce MIDI latency over BLE

Reduce latency when connecting a MIDI device over Bluetooth BLE, as it's significantly higher than USB. This affects button light updates and rotor responsiveness. Investigate queue monitoring in portmidi to improve polling updates.

Original Source

@@dterrahe | 0 pts | 12/13/2025

When connecting a midi device over bluetooth BLE (like https://discuss.pixls.us/t/using-a-midi-device-with-darktable/54391/1) latency is much higher than when using USB. This manifests itself with button lights updating only 10secs after the onscreen button it is linked to is toggled and rotors in absolute mode getting jumpy when using shift to take large steps. Possible solutions to investigate: 1. monitor the queue in portmidi if possible. The polling updates for rotors and buttons should be postponed when the queue is still processing the last update. It may be that the actual size of congestion is hidden in a driver level, in which case hopefully we can still monitor throughput and then scale back the volume of updates so that it should be low enough for the driver to catch up. 2. When sending updates remember the previous confirmed level (i.e. _received_ from the device) and then when receiving new data from the device, if it is in between both values, make a best guess whether i

Discussion

Loading comments...