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.

[OBS Studio] Use a single DirectX context for GPU encoding with jim-nvenc

OBS currently uses an additional DirectX context for GPU encoding when using jim-nvenc. The user requests that OBS use a single DirectX context, as recommended by Nvidia in their Video SDK samples, to potentially improve performance or reduce resource usage.

Original Source

@@theHamsta | 4 pts | 6/24/2022

### Operating System Info Windows 11 ### Other OS _No response_ ### OBS Studio Version Git ### OBS Studio Version (Other) _No response_ ### OBS Studio Log URL https://obsproject.com/logs/l3JZQfAboldVzSMe ### OBS Studio Crash Log URL _No response_ ### Expected Behavior OBS just uses a single DirectX context when using jim-nvenc (see below). This is the recommendation Nvidia gives in their Video SDK samples (https://developer.nvidia.com/video_codec_sdk/downloads/v11-1-5, Nvidia Developer account necessary for download) ### Current Behavior jim-nvenc, like other GPU encoders, creates a dedicated DirectX context (https://github.com/obsproject/obs-studio/blob/master/plugins/obs-ffmpeg/jim-nvenc.c#L290-L340) that is not shared with the rendering context. This does not follow the recommendation in the official samples https://developer.nvidia.com/video_codec_sdk/downloads/v11-1-5 (Nvidia developer account necessary for download) where GPU encoding

Discussion

Loading comments...