I am having trouble with my gstreamer pipeline. I am using jetpack 4.2.3 on Xavier dev kit. The following pipeline works and shows the video correctly in X :-
BUT, the following pipeline does not work, prints no errors (actually it prints identical output). It opens a window and just shows black frames,… pure blackness. The only difference is the winsys param on the sink at the end. According to gst-inspect, winsys defaults to x11 anyway.
I need the winsys param to work because I need to get this running as a wayland client in weston. In my testing, using winsys=wayland fails in exactly the same way - it creates a black window.
I may not be able to help further, but running these commands one can see that even if winsys default is x11, specifying it makes a difference for VBO setup:
GST_DEBUG=nveglglessink:4 gst-launch-1.0 -v videotestsrc ! nvvidconv ! nvegltransform ! nveglglessink
...
0:00:00.133156165 13674 0x5579af70a0 INFO nveglglessink gsteglglessink.c:946:gst_eglglessink_setup_vbo:<eglglessink0> VBO setup. have_vbo:0
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
...
GST_DEBUG=nveglglessink:4 gst-launch-1.0 -v videotestsrc ! nvvidconv ! nvegltransform ! nveglglessink winsys=x11
...
0:00:00.112795433 13690 0x558fffb0a0 INFO nveglglessink gsteglglessink.c:946:gst_eglglessink_setup_vbo:<eglglessink0> VBO setup. have_vbo:0
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[b]0:00:00.126737885 13690 0x558fffb0a0 INFO nveglglessink gsteglglessink.c:946:gst_eglglessink_setup_vbo:<eglglessink0> VBO setup. have_vbo:1
0:00:00.160003905 13690 0x558fffb0a0 INFO nveglglessink gsteglglessink.c:946:gst_eglglessink_setup_vbo:<eglglessink0> VBO setup. have_vbo:1
0:00:00.193446288 13690 0x558fffb0a0 INFO nveglglessink gsteglglessink.c:946:gst_eglglessink_setup_vbo:<eglglessink0> VBO setup. have_vbo:1
0:00:00.226907104 13690 0x558fffb0a0 INFO nveglglessink gsteglglessink.c:946:gst_eglglessink_setup_vbo:<eglglessink0> VBO setup. have_vbo:1[/b]
May not be related, but in the latter case it also issues this message:
Hi, thanks for the tips… it does look like there are differences between the winsys and non-winsys invocations. I will give this a go with the GST_DEBUG set like you have tomorrow when I get back into work.
nVidia, does this extra info help at all diagnosing the potential issue with your sink plugin? Did you run the gstreamer pipelines? Did you get the same results as I did?
I cannot discuss the project in detail in a public forum, but can say that we are currently evaluating the jetson xavier platform to see if it suits our intended application.
One of our requirements relating to this issue is efficient hardware accelerated decoding of h264 and h265 @ UHD @ 60 in wayland.
Do you have a date for the next release? If it is this week I think our deadlines will probably be unaffected. Otherwise, how can I get a binary or source patch from you guys?