Re: I420 format used to work with nvh264enc but no longer does
Nicolas Dufresne via gstreamer-devel <[email protected]> Wed, 08 Oct 2025 16:41:20 -0400
| Newsgroups | gmane.comp.video.gstreamer.devel |
|---|---|
| Message-ID | <[email protected]> |
--=-dVLMf1iDEdWEixbjjnWg
Content-Type: multipart/alternative; boundary="=-z+TFqKdcE5H6I3zgsbda"
--=-z+TFqKdcE5H6I3zgsbda
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi,
Le mercredi 08 octobre 2025 =C3=A0 14:59 -0400, Sid Sethupathi via gstreame=
r-devel a
=C3=A9crit=C2=A0:
> Hello,
>=20
> We are in the process of updating some dependencies and in this process w=
e are
> updating from Gstreamer 1.20.3 to 1.26.5.
>=20
> We have a pipeline that looks like the following: "gst-launch-1.0 videote=
stsrc
> ! video/x-raw,width=3D1280,height=3D720,format=3DI420 ! nvh264enc ! fakes=
ink"
>=20
> In 1.20.3, this works even though the sink caps of nvh264enc do not inclu=
de
> I420 as a valid format. The outputted video in our actual pipeline looked
> correct.
>=20
> In 1.26.5, this pipeline does not work: "WARNING: erroneous pipeline: cou=
ld
> not link videotestsrc0 to nvh264enc0, nvh264enc0 can't handle caps video/=
x-
> raw, width=3D(int)1280, height=3D(int)720, format=3D(string)I420".
In 1.20, the encoder was called nvcudah264enc, if you didn't change that wh=
ile
updating, its likely that you where using another implementation. Or perhap=
s it
was a bin with "cudaconvert" implicitly added. The formats you will see on =
the
documentation page are fake, they are place holder, since the actual value =
is
hardware specific. Please give a try to our new forum, where pretty much al=
l the
traffic and exchanges occure these days:=C2=A0https://discourse.gstreamer.o=
rg/
Nicolas
>=20
> It is easy enough for us to switch the format to something that is explic=
itly
> in the capabilities list, but I was just wondering whether the listed for=
mats
> usable by nvh264enc are correct since it used to work, or if it just work=
ed by
> happenstance.=C2=A0
>=20
> Sid
>=20
--=-z+TFqKdcE5H6I3zgsbda
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<html><head><style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head><body><div>Hi,</div><div><br></div><div>Le mercredi 08 octob=
re 2025 =C3=A0 14:59 -0400, Sid Sethupathi via gstreamer-devel a =C3=A9crit=
:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-l=
eft:2px #729fcf solid;padding-left:1ex"><div><div>Hello,</div><div><br></di=
v><div>We are in the process of updating some dependencies and in this proc=
ess we are updating from Gstreamer 1.20.3 to 1.26.5.</div><div><br></div><d=
iv>We have a pipeline that looks like the following: "gst-launch-1.0 videot=
estsrc ! video/x-raw,width=3D1280,height=3D720,format=3DI420 ! nvh264enc ! =
fakesink"</div><div><br></div><div>In 1.20.3, this works even though the si=
nk caps of nvh264enc do not include I420 as a valid format. The outputted v=
ideo in our actual pipeline looked correct.</div><div><br></div><div>In 1.2=
6.5, this pipeline does not work: "WARNING: erroneous pipeline: could not l=
ink videotestsrc0 to nvh264enc0, nvh264enc0 can't handle caps video/x-raw, =
width=3D(int)1280, height=3D(int)720, format=3D(string)I420".<br></div></di=
v></blockquote><div><br></div><div>In 1.20, the encoder was called nvcudah2=
64enc, if you didn't change that while updating, its likely that you where =
using another implementation. Or perhaps it was a bin with "cudaconvert" im=
plicitly added. The formats you will see on the documentation page are fake=
, they are place holder, since the actual value is hardware specific. Pleas=
e give a try to our new forum, where pretty much all the traffic and exchan=
ges occure these days: <a href=3D"https://discourse.gstreamer.org/">ht=
tps://discourse.gstreamer.org/</a></div><div><br></div><div>Nicolas</div><d=
iv><br></div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-l=
eft:2px #729fcf solid;padding-left:1ex"><div><div><br></div><div>It is easy=
enough for us to switch the format to something that is explicitly in the =
capabilities list, but I was just wondering whether the listed formats usab=
le by nvh264enc are correct since it used to work, or if it just worked by =
happenstance. </div><div><div><br>Sid<br><br></div></div></div></block=
quote><div><br></div><div><span></span></div></body></html>
--=-z+TFqKdcE5H6I3zgsbda--
--=-dVLMf1iDEdWEixbjjnWg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQTvDVKBFcTDwhoEbxLZQZRRKWBy9AUCaObMcAAKCRDZQZRRKWBy
9PROAQCjWWWl0fwjSziqYsQ7k2/iKSyh3ytsD4CpIwSYmr6U6wEAwfR5L+ACpt+c
Zd3najOBp+HC1MrDT/75J4t6Kmhv1wU=
=CHCu
-----END PGP SIGNATURE-----
--=-dVLMf1iDEdWEixbjjnWg--