FFmpeg  4.3
Data Structures | Macros | Typedefs | Enumerations | Functions | Variables
mxf.h File Reference
#include "avformat.h"
#include "libavcodec/avcodec.h"
#include <stdint.h>

Go to the source code of this file.

Data Structures

struct  MXFContentPackageRate
 
struct  KLVPacket
 
struct  MXFCodecUL
 

Macros

#define PRIxUID
 
#define UID_ARG(x)
 
#define PRINT_KEY(pc, s, x)
 

Typedefs

typedef uint8_t UID[16]
 

Enumerations

enum  MXFMetadataSetType {
  AnyType, MaterialPackage, SourcePackage, SourceClip,
  TimecodeComponent, PulldownComponent, Sequence, MultipleDescriptor,
  Descriptor, Track, CryptoContext, Preface,
  Identification, ContentStorage, SubDescriptor, IndexTableSegment,
  EssenceContainerData, EssenceGroup, TaggedValue, TapeDescriptor,
  AVCSubDescriptor
}
 
enum  MXFFrameLayout {
  FullFrame = 0, SeparateFields, OneField, MixedFields,
  SegmentedFrame
}
 
enum  MXFWrappingIndicatorType { NormalWrap = 0, D10D11Wrap, RawAWrap, RawVWrap }
 

Functions

int ff_mxf_decode_pixel_layout (const char pixel_layout[16], enum AVPixelFormat *pix_fmt)
 
int ff_mxf_get_content_package_rate (AVRational time_base)
 

Variables

const MXFCodecUL ff_mxf_data_definition_uls []
 SMPTE RP224 http://www.smpte-ra.org/mdd/index.html. More...
 
const MXFCodecUL ff_mxf_codec_uls []
 
const MXFCodecUL ff_mxf_pixel_format_uls []
 
const MXFCodecUL ff_mxf_codec_tag_uls []
 

Macro Definition Documentation

◆ PRIxUID

#define PRIxUID
Value:
"%02x.%02x.%02x.%02x." \
"%02x.%02x.%02x.%02x." \
"%02x.%02x.%02x.%02x." \
"%02x.%02x.%02x.%02x"

Definition at line 99 of file mxf.h.

◆ UID_ARG

#define UID_ARG (   x)
Value:
(x)[0], (x)[1], (x)[2], (x)[3], \
(x)[4], (x)[5], (x)[6], (x)[7], \
(x)[8], (x)[9], (x)[10], (x)[11], \
(x)[12], (x)[13], (x)[14], (x)[15] \

Definition at line 105 of file mxf.h.

◆ PRINT_KEY

#define PRINT_KEY (   pc,
  s,
  x 
)
Value:
do { if(0) \
av_log(pc, AV_LOG_VERBOSE, \
"%s " \
"0x%02x,0x%02x,0x%02x,0x%02x," \
"0x%02x,0x%02x,0x%02x,0x%02x," \
"0x%02x,0x%02x,0x%02x,0x%02x," \
"0x%02x,0x%02x,0x%02x,0x%02x ", \
s, UID_ARG(x)); \
}while(0)

Definition at line 128 of file mxf.h.

Typedef Documentation

◆ UID

typedef uint8_t UID[16]

Definition at line 28 of file mxf.h.

Enumeration Type Documentation

◆ MXFMetadataSetType

Enumerator
AnyType 
MaterialPackage 
SourcePackage 
SourceClip 
TimecodeComponent 
PulldownComponent 
Sequence 
MultipleDescriptor 
Descriptor 
Track 
CryptoContext 
Preface 
Identification 
ContentStorage 
SubDescriptor 
IndexTableSegment 
EssenceContainerData 
EssenceGroup 
TaggedValue 
TapeDescriptor 
AVCSubDescriptor 

Definition at line 30 of file mxf.h.

◆ MXFFrameLayout

Enumerator
FullFrame 
SeparateFields 
OneField 
MixedFields 
SegmentedFrame 

Definition at line 54 of file mxf.h.

◆ MXFWrappingIndicatorType

Enumerator
NormalWrap 
D10D11Wrap 
RawAWrap 
RawVWrap 

Definition at line 74 of file mxf.h.

Function Documentation

◆ ff_mxf_decode_pixel_layout()

int ff_mxf_decode_pixel_layout ( const char  pixel_layout[16],
enum AVPixelFormat pix_fmt 
)

Definition at line 120 of file mxf.c.

Referenced by mxf_read_pixel_layout().

◆ ff_mxf_get_content_package_rate()

int ff_mxf_get_content_package_rate ( AVRational  time_base)

Definition at line 162 of file mxf.c.

Referenced by mxf_init_timecode(), and mxf_write_header().

Variable Documentation

◆ ff_mxf_data_definition_uls

const MXFCodecUL ff_mxf_data_definition_uls[]

◆ ff_mxf_codec_uls

const MXFCodecUL ff_mxf_codec_uls[]

Definition at line 37 of file mxf.c.

Referenced by mxf_parse_structural_metadata().

◆ ff_mxf_pixel_format_uls

const MXFCodecUL ff_mxf_pixel_format_uls[]

Definition at line 78 of file mxf.c.

Referenced by mxf_parse_structural_metadata().

◆ ff_mxf_codec_tag_uls

const MXFCodecUL ff_mxf_codec_tag_uls[]

Definition at line 84 of file mxf.c.

Referenced by mxf_parse_structural_metadata().

AV_LOG_VERBOSE
#define AV_LOG_VERBOSE
Detailed information.
Definition: log.h:192
x
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script ‘tests fate sh’ from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ v’ options You should get detailed output concerning your SSH configuration and the authentication process The only thing left is to automate the execution of the fate sh script and the synchronisation of the samples directory Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo x
Definition: fate.txt:150
UID_ARG
#define UID_ARG(x)
Definition: mxf.h:105
s
#define s(width, name)
Definition: cbs_vp9.c:257