[x264-devel] answer to 'How to set level programmatically'

Fri May 24 22:49:49 CEST 2013

Level is like any other parameter for the libx264, you can set it by using
the
int x264_param_parse( x264_param_t *, const char *name, const char *value )

name = "level"
value = "4.0" or whatever

On Fri, May 24, 2013 at 3:00 AM, <x264-devel-request at videolan.org> wrote:

> Send x264-devel mailing list submissions to
>         x264-devel at videolan.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mailman.videolan.org/listinfo/x264-devel
> or, via email, send a message with subject or body 'help' to
>         x264-devel-request at videolan.org
>
> You can reach the person managing the list at
>         x264-devel-owner at videolan.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of x264-devel digest..."
>
>
> Today's Topics:
>
>    1. How to set level programmatically (YIRAN LI)
>    2. Re: How to set level programmatically (Sergio Garcia Murillo)
>    3. Re: Different pic_init_qp_minus26 cause stitching to fail.
>       (Anders Rein)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 24 May 2013 10:49:48 +1000
> From: YIRAN LI <mrfun.china at gmail.com>
> To: x264-devel at videolan.org
> Subject: [x264-devel] How to set level programmatically
> Message-ID:
>         <
> CAN16yyMd_DVEHVem4aRnJYuKK4g+2qjUhffteBQdjU-oHTLmfg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Guys,
>
> I'm writing a application to convert videos into iPhone/iPad supported
> format. So I know the profile and highest level I can convert to.
>
> I know there's an API x264_param_apply_profile to set profile, but I
> couldn't find where can I set level in x264_param_t.
>
> Another question is, if I couldn't set level programmatically, could I
> achieve the same result by supplying max resolution, max frame size, and
> other params?
>
> Great thanks!
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mailman.videolan.org/pipermail/x264-devel/attachments/20130524/e9b3ea90/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 24 May 2013 10:47:58 +0200
> From: Sergio Garcia Murillo <sergio.garcia.murillo at gmail.com>
> To: x264-devel at videolan.org
> Subject: Re: [x264-devel] How to set level programmatically
> Message-ID: <519F293E.9060907 at gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> +1
>
> Some conferencing equipment matches the level in the SPS with the
> profile-level-id negotiated via SDP and reject it if they don't match
> (even if the h264 stream comply with the level constrains). So currently
> I have to check all output nals for SPS ones and rewrite the value.
>
> Best regards
> Sergio
>
> El 24/05/2013 2:49, YIRAN LI escribi?:
> > Hi Guys,
> >
> > I'm writing a application to convert videos into iPhone/iPad supported
> > format. So I know the profile and highest level I can convert to.
> >
> > I know there's an API x264_param_apply_profile to set profile, but I
> > couldn't find where can I set level in x264_param_t.
> >
> > Another question is, if I couldn't set level programmatically, could I
> > achieve the same result by supplying max resolution, max frame size,
> > and other params?
> >
> > Great thanks!
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > x264-devel mailing list
> > x264-devel at videolan.org
> > http://mailman.videolan.org/listinfo/x264-devel
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mailman.videolan.org/pipermail/x264-devel/attachments/20130524/47903b52/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Fri, 24 May 2013 11:15:38 +0200
> From: Anders Rein <are at vizrt.com>
> To: Mailing list for x264 developers <x264-devel at videolan.org>
> Subject: Re: [x264-devel] Different pic_init_qp_minus26 cause
>         stitching to fail.
> Message-ID: <519F2FBA.3010103 at vizrt.com>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Hi,
>
> Thanks for your reply!
>
> Changing the SPS/PPS ID of one of the clips and then having both
> SPS/PPS' in the video would be the more correct solution, but
> unfortunately this is not widely supported by decoders/players. Since we
> are delivering content to various mobile device it is important that it
> works on as many phones as possible.
>
> I think something like --stitchable would be exactly what we are looking
> for.
>
> Anders
> On 05/22/2013 05:29 PM, Jason Garrett-Glaser wrote:
> > On Wed, May 22, 2013 at 2:02 AM, Anders Rein <are at vizrt.com> wrote:
> >> Hi,
> >>
> >> I am working on a software which transcodes clips and commercial to
> >> different resolution and serve the correct content to various media
> devices.
> >> We've been using x264 via ffmpeg for encoding h264. Recently we updated
> x264
> >> from snapshot-20120705 to snapshot-20130303. This caused our stitching
> of
> >> commercial and video content to fail.
> >>
> >> The stitching fails because the pic_init_qp_minus26 in the
> >> picture_parameter_set differs between the clips. The results vary from
> foggy
> >> and saturate results to complete crash (depending on the decoder).
> > Is the video not allowed to keep the PPS and SPSs from each of the
> > stitched sections?
> >
> > If not, maybe I could add a --stitchable option?
> >
> > Jason
> > _______________________________________________
> > x264-devel mailing list
> > x264-devel at videolan.org
> > http://mailman.videolan.org/listinfo/x264-devel
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mailman.videolan.org/pipermail/x264-devel/attachments/20130524/e9da99d5/attachment-0001.html
> >
>
> ------------------------------
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
>
> End of x264-devel Digest, Vol 72, Issue 15
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20130524/958e03bf/attachment-0001.html>