[GH-ISSUE #281] Black Screen on Odd, High Definition Resolutions #198

New issue

Closed

opened 2026-10-15 12:58:06 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-15 12:58:06 +00:00

Owner

Originally created by @bradsk88 on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/281

Note

Apologies if this is a server-side thing.
It's not obvious to me from the logs, and I'm hoping to start the journey of solving the problem somewhere 😅

I have an (admittedly weird) LG DualUp Ergo 16:18 monitor and I'm trying to use wolf to access my gaming server on it.

The native resolution is 2560x2880. When I set moonlight to stream at this resolution, I see a black screen.

I can confirm the stream is "working" because I can hear the test ball sound.

When I set moonlight to use half-pixel resolution (1280x1440), everything works. But, of course, the quality is significantly reduced.

Logs when connecting at native resolution:

ERROR           GST_PIPELINE subprojects/gstreamer/gst/parse/grammar.y:1191:gst_parse_pe

rform_link: could not link vapostproc10 to vah265enc9, vah265enc9 can't handle caps video/x-raw(memory:VAMemory), format=(strin

g)NV12, chroma-site=(string)mpeg2, width=(int)2560, height=(int)2880, colorimetry=(string)bt601, pixel-aspect-ratio=(fraction)1

/1

WARN  | [GSTREAMER] Pipeline parse error (recovered): could not link vapostproc10 to vah265enc9, vah265enc9

can't handle caps video/x-raw(memory:VAMemory), format=(string)NV12, chroma-site=(string)mpeg2, width=(int)2560, height=(int)28

80, colorimetry=(string)bt601, pixel-aspect-ratio=(fraction)1/1

WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc10

> segment format mismatched, ignore

WARN                 basesrc gstbasesrc.c:3187:gst_base_src_loop:<interpipesrc10> error:

Internal data stream error.

WARN                 basesrc gstbasesrc.c:3187:gst_base_src_loop:<interpipesrc10> error:

streaming stopped, reason not-linked (-1)

ERROR | [GSTREAMER] Pipeline error: Internal data stream error.

WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc11

> segment format mismatched, ignore

Originally created by @bradsk88 on GitHub (Oct 27, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/281 > [!NOTE] > Apologies if this is a server-side thing. > It's not obvious to me from the logs, and I'm hoping to start the journey of solving the problem somewhere 😅 I have an (admittedly weird) [LG DualUp Ergo](https://www.lg.com/ca_en/monitors/ergo-monitors/28mq780-b/?srsltid=AfmBOopQAaWbq41pgI-GHhEoUI90IeTP1pThZtFfYHEBqnaNbhrLr-5T) 16:18 monitor and I'm trying to use wolf to access my gaming server on it. The native resolution is 2560x2880. When I set moonlight to stream at this resolution, I see a black screen. I can confirm the stream is "working" because I can hear the test ball sound. When I set moonlight to use half-pixel resolution (1280x1440), everything works. But, of course, the quality is significantly reduced. <img width="315" height="357" alt="Image" src="https://github.com/user-attachments/assets/6e3c90d9-17fe-4c54-96f1-890b28a03db0" /> --- Logs when connecting at native resolution: ``` ERROR GST_PIPELINE subprojects/gstreamer/gst/parse/grammar.y:1191:gst_parse_pe rform_link: could not link vapostproc10 to vah265enc9, vah265enc9 can't handle caps video/x-raw(memory:VAMemory), format=(strin g)NV12, chroma-site=(string)mpeg2, width=(int)2560, height=(int)2880, colorimetry=(string)bt601, pixel-aspect-ratio=(fraction)1 /1 WARN | [GSTREAMER] Pipeline parse error (recovered): could not link vapostproc10 to vah265enc9, vah265enc9 can't handle caps video/x-raw(memory:VAMemory), format=(string)NV12, chroma-site=(string)mpeg2, width=(int)2560, height=(int)28 80, colorimetry=(string)bt601, pixel-aspect-ratio=(fraction)1/1 WARN basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc10 > segment format mismatched, ignore WARN basesrc gstbasesrc.c:3187:gst_base_src_loop:<interpipesrc10> error: Internal data stream error. WARN basesrc gstbasesrc.c:3187:gst_base_src_loop:<interpipesrc10> error: streaming stopped, reason not-linked (-1) ERROR | [GSTREAMER] Pipeline error: Internal data stream error. WARN basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc11 > segment format mismatched, ignore ```

bsakaguchi

2026-10-15 12:58:06 +00:00

closed this issue
added the
AMD
label

bsakaguchi commented

2026-10-15 12:58:07 +00:00

Author

Owner

@ABeltramo commented on GitHub (Oct 27, 2025):

Interesting, from the logs it sounds like an issue with the GPU video encoder (vah265enc) that doesn't support that resolution.. Which GPU do you have?

If it turns out to be the VAAPI encoder I'm not sure there's much we can do on Wolf side; you can try setting any custom resolution in Moonlight too see exactly what works and what doesn't..

@ABeltramo commented on GitHub (Oct 27, 2025): Interesting, from the logs it sounds like an issue with the GPU video encoder (`vah265enc`) that doesn't support that resolution.. Which GPU do you have? If it turns out to be the VAAPI encoder I'm not sure there's much we can do on Wolf side; you can try setting any custom resolution in Moonlight too see exactly what works and what doesn't..

bsakaguchi commented

2026-10-15 12:58:07 +00:00

Author

Owner

@bradsk88 commented on GitHub (Oct 29, 2025):

I'm running a Radeon RX Vega 56.

I tried an additional strange resolution (1500x1000) and it ran no problem. It was also able to handle 4K.

Are there any specific tests I can do to determine if it's the VAAPI encoder or not?

@bradsk88 commented on GitHub (Oct 29, 2025): I'm running a Radeon RX Vega 56. I tried an additional strange resolution (1500x1000) and it ran no problem. It was also able to handle 4K. Are there any specific tests I can do to determine if it's the VAAPI encoder or not?

bsakaguchi commented

2026-10-15 12:58:07 +00:00

Author

Owner

@bradsk88 commented on GitHub (Oct 29, 2025):

Strangely, I was able to get it to render all the way up to 2560 x 2305. Even 3840x2305 worked.

But 256x2306 did not work.

I wonder what the significance of that vertical count is.

@bradsk88 commented on GitHub (Oct 29, 2025): Strangely, I was able to get it to render all the way up to 2560 x 2305. Even 3840x2305 worked. But 256x2306 **did not work**. I wonder what the significance of that vertical count is.

bsakaguchi commented

2026-10-15 12:58:07 +00:00

Author

Owner

@bradsk88 commented on GitHub (Jan 29, 2026):

Not sure what happened, but this seems to have resolved itself.

@bradsk88 commented on GitHub (Jan 29, 2026): Not sure what happened, but this seems to have resolved itself.