It would be great if this API allowed you to decode video as well. Are you planning on doing this in the future?

Hi, I try to install this crate but I have this error:

error[E0423]: expected function, tuple struct or tuple variant, found struct `ast::Name`
   --> /home/jourdelune/.cargo/registry/src/github.com-1ecc6299db9ec823/syntex_syntax-0.58.1/src/symbol.rs:146:27
    |
146 |                       name: ast::Name($index),
    |                             ^^^^^^^^^
...
165 | / declare_keywords! {
166 | |     // Invalid identifier
167 | |     (0,  Invalid,        "")
168 | |
...   |
231 | |     (56, CrateRoot, "{{root}}")
232 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `declare_keywords` (in Nightly builds, run with -Z macro-backtrace for more info)```
    
Someone can help me?

Hi! Filing this issue because of the comment:

/// Please file an issue if you know what this does, because I have no idea.
pub fn annexb(mut self, annexb: bool) -> Self {

This repo doesn't seem very active anymore, but maybe this helps someone else struggling with the same thing as me.

The way I understand it, "Annex B" start codes are a way to be able to seek to the next/previous NAL unit from anywhere in a stream. The mp4 container does not use Annex B start codes, so if you're trying to use this library in combination with for example the mp4 crate, you need to make sure to turn off the Annex B start codes, because they're enabled by default. For example:

let mut encoder =
    Setup::preset(Preset::Medium, Tune::None, false, true)
        .annexb(false)
        .build(Colorspace::I420, WIDTH as _, HEIGHT as _)
        .unwrap();

(also, make sure to crop off the first 4 bytes of the SPS and PPS headers before passing them to mp4)

As far as I can tell, this crate doesn't give any way to control the I-frame interval, although the underlying x264-sys crate does, with the i_scenecut_threshold and i_keyint_max fields in x264_param_t. Would this be possible?

It seems like this crate is unmaintained. I would be interested in maintaining it, and for now I will publish and maintain my fork of it under the name x264-next. If you would be interested in transferring ownership of this crate or plan to maintain it, just let me know.

Hi @quadrupleslap

Thanks for your kind wrapper. Does any performance comparison available between x264-rs and libx264?

Regards,
Ali