[x264-devel] Re: [PATCH] add pps_id option and define sps_id and pps_id as uint8_t

Limin Wang lance.lmwang at gmail.com
Thu Feb 1 03:37:09 CET 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,


* Loren Merritt <lorenm at u.washington.edu> [2007-01-31 15:30:04 -0700]:

> >Now x264 support one SPS and PPS only, so it's ok in this case. If we want
> >to support more than one SPS and PPS, then it's too limited to configure 
> >the
> >both ids the same. I'm also confused why specs limit sps_id and pps_id
> >to different range, any good reason?
> 
> I don't know why they need different ranges (since there's no penalty for 
> having unused numbers), but I can guess why you'd expect more PPSs than 
> SPSs. SPS contains properties of the decoded stream. PPS contains all the 
> settings that only the codec itself needs to know. So I'd expect multiple 
> SPSs only if you're concatenating video from different sources, but PPS 
> could change within each source if different scenes have different optimal 
> settings. (Ok, so the segregation isn't that perfect, but the idea 
> stands.)

Thanks, it sounds reasonable. So I think pps_id and sps_id value should be
decided by encode self instead of user configure. In order to get optimal
encode result, it's necessary to support multiple PPS also. right?



> --Loren Merritt
> 
> -- 
> This is the x264-devel mailing-list
> To unsubscribe, go to: http://developers.videolan.org/lists.html
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEUAwUBRcFSVEztbf7dKiuoAQKCngf1EPihJwG+U7tVme/ti/WdD8qNYngYb4Z0
eY+poKJs7Bfi218QRX75CfCzTq/oDBcNtyj7XKzjzkubYMn4s5zMCNLkPQrf8zMA
tfZ545LQ6fZuOqs1i5FlJ4VxBc0GFiY5tBOzjieHq2N+CATQgJtgf5GaU9pvB3k2
8g/XNBdh+H4BJkjUhYxuaMHqhMEfmAFrKkzPottHYzNieeyRaayQSau6rx4nxkTs
SH725PIvrzwmIQzpjIqtpCIs1wpACxv1dayvNSt4bBs5OhlODQCtwpdGjxTPQM/3
4gTwC5deInMUT+ozo32qU8ofBcm7Joe8Vo42cFJgkdCf3gxri53R
=G9Oi
-----END PGP SIGNATURE-----

-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html



More information about the x264-devel mailing list