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

Unable to specify BGR24 video format on BGR32-capable capture card #11676

Open
notonetotalk opened this issue Dec 28, 2024 · 1 comment
Open

Comments

@notonetotalk
Copy link

notonetotalk commented Dec 28, 2024

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

31.0.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/KhWPOSjeYQKKXBje

OBS Studio Crash Log URL

No response

Expected Behavior

Selectable video formats for my video capture device should include BRG24 and BRG32 options.

Current Behavior

Only "XRGB" is selectable as an option for RGB/BRG capture, and defaults to BRG 32-bit with no option to specify BRG 24-bit capture.

Screenshot 2024-12-27 at 11 26 19 AM

Steps to Reproduce

  1. Add new Video Capture Device source
  2. In the device's Properties window select a BGR24/BGR32-capable capture card device under "Device"
  3. Select "Custom" for "Resolution/FPS Type"
  4. Specify a resolution size for "Resolution"
  5. Under "Video Format" only "XRGB" is shown as an option for RGB capture.

Anything else we should know?

My capture card is a Magewell Pro Capture HDMI. Being able to specify between the formats matters as the increased bandwidth requirements for BGR 32-bit capture does not allow for 1920x1080p 60 fps recording without frame drops. The alternative broadcasting software XSplit allows me to capture in BRG 24-bit and I do not experience any frame drops when capturing at 1920x1080p 60fps in that mode. Setting my capture format to BRG 32-bit in XSplit gives me the same amount of frame drops as it does in OBS Studio.

@derrod
Copy link
Member

derrod commented Dec 29, 2024

Technically a duplicate of #4176 but that one was closed as stale so we can leave this one open. Due to the niche nature of these devices, and nobody of the dev team having one, this just has never been addressed.

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

2 participants