1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82

#![allow(unused)]
#![allow(non_snake_case)]
#![allow(non_upper_case_globals)]
#![allow(non_camel_case_types)]

include!(concat!(env!("OUT_DIR"), "/bindings.rs"));


///////////////////////////////////////////////////////////////////////////////
// EXTRAS (FROM LIBVMAF SOURCE CODE)
///////////////////////////////////////////////////////////////////////////////

/// Extra stuff from the libvmaf git repo that you’ll probably need.
pub mod extras {
    const buildtype_docs_only_stub_msg: &'static str =
        "stub for docs.rs only (when cargo feature = 'buildtype-docs-only')";
    
    /// Returns the string contents of the VMAF 'default' model that this library
    /// was compiled with. 
    /// 
    /// Regarding the return tuple. I have no idea what the first is, in
    /// relation to the second. Yet the first component (in the tuple) is
    /// what you give VMAF (dumped to a file).
    /// 
    /// The second is also for VMAF, but it looks for it with the same file
    /// path as the first, except ending with a `.model` extension. There is
    /// no documentation about this, yet it seems to be what it wants at
    /// runtime. 
    #[cfg(not(feature="buildtype-docs-only"))]
    pub fn get_vmaf_def_model() -> (&'static str, &'static str) {
        let x = include_str!(concat!(env!("OUT_DIR"), "/vmaf/release/vmaf_v0.6.1.pkl"));
        let y = include_str!(concat!(env!("OUT_DIR"), "/vmaf/release/vmaf_v0.6.1.pkl.model"));
        (x, y)
    }

    /// Returns the string contents of the VMAF '4K' model that this library
    /// was compiled with. 
    /// 
    /// Regarding the return tuple. I have no idea what the first is, in
    /// relation to the second. Yet the first component (in the tuple) is
    /// what you give VMAF (dumped to a file).
    /// 
    /// The second is also for VMAF, but it looks for it with the same file
    /// path as the first, except ending with a `.model` extension. There is
    /// no documentation about this, yet it seems to be what it wants at
    /// runtime. 
    #[cfg(not(feature="buildtype-docs-only"))]
    pub fn get_vmaf_4k_model() -> (&'static str, &'static str) {
        let x = include_str!(concat!(env!("OUT_DIR"), "/vmaf/release/vmaf_4k_v0.6.1.pkl"));
        let y = include_str!(concat!(env!("OUT_DIR"), "/vmaf/release/vmaf_4k_v0.6.1.pkl.model"));
        (x, y)
    }

    /// Returns the string contents of the VMAF 'default' model that this library
    /// was compiled with. 
    /// 
    /// Regarding the return tuple. I have no idea what the first is, in
    /// relation to the second. Yet the first component (in the tuple) is
    /// what you give VMAF (dumped to a file).
    /// 
    /// The second is also for VMAF, but it looks for it with the same file
    /// path as the first, except ending with a `.model` extension. There is
    /// no documentation about this, yet it seems to be what it wants at
    /// runtime. 
    #[cfg(feature="buildtype-docs-only")]
    pub fn get_vmaf_def_model() -> (&'static str, &'static str) {panic!(buildtype_docs_only_stub_msg)}


    /// Returns the string contents of the VMAF '4K' model that this library
    /// was compiled with. 
    /// 
    /// Regarding the return tuple. I have no idea what the first is, in
    /// relation to the second. Yet the first component (in the tuple) is
    /// what you give VMAF (dumped to a file).
    /// 
    /// The second is also for VMAF, but it looks for it with the same file
    /// path as the first, except ending with a `.model` extension. There is
    /// no documentation about this, yet it seems to be what it wants at
    /// runtime. 
    #[cfg(feature="buildtype-docs-only")]
    pub fn get_vmaf_4k_model() -> (&'static str, &'static str) {panic!(buildtype_docs_only_stub_msg)}
}