Go to the documentation of this file.
22 #ifndef AVCODEC_ASS_SPLIT_H
23 #define AVCODEC_ASS_SPLIT_H
126 int cache,
int *number);
160 void (*new_line)(
void *priv,
int forced);
162 void (*
color)(
void *priv,
unsigned int ,
unsigned int color_id);
167 void (*cancel_overrides)(
void *priv,
const char *style);
174 void (*move)(
void *priv,
int x1,
int y1,
int x2,
int y2,
int t1,
int t2);
175 void (*origin)(
void *priv,
int x,
int y);
float timer
time multiplier to apply to SSA clock (in %)
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf default minimum maximum flags name is the option name
Set of callback functions corresponding to each override codes that can be encountered in a "Dialogue...
int end
end time of the dialog in centiseconds
int alignment
position of the text (left, center, top...), defined after the layout of the numpad (1-3 sub,...
static av_cold int end(AVCodecContext *avctx)
static const OMX_CALLBACKTYPE callbacks
ASSStyle * styles
array of split out styles
void(* style)(void *priv, char style, int close)
ASSStyle * ff_ass_style_get(ASSSplitContext *ctx, const char *style)
Find an ASSStyle structure by its name.
char * style
name of the ASSStyle to use with this dialog
char * font_name
font face (case sensitive)
void ff_ass_split_free(ASSSplitContext *ctx)
Free all the memory allocated for an ASSSplitContext.
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
ASSDialog * dialogs
array of split out dialogs
int start
start time of the dialog in centiseconds
ASSDialog * ff_ass_split_dialog(ASSSplitContext *ctx, const char *buf, int cache, int *number)
Split one or several ASS "Dialogue" lines from a string buffer and store them in an already initializ...
int play_res_y
video height that ASS coords are referring to
int ff_ass_split_override_codes(const ASSCodesCallbacks *callbacks, void *priv, const char *buf)
Split override codes out of a ASS "Dialogue" Text field.
structure containing the whole split ASS data
int play_res_x
video width that ASS coords are referring to
ASSSplitContext * ff_ass_split(const char *buf)
Split a full ASS file or a ASS header from a string buffer and store the split structure in a newly a...
int primary_color
color that a subtitle will normally appear in
void(* alpha)(void *priv, int alpha, int alpha_id)
fields extracted from the [Script Info] section
char * script_type
SSA script format version (eg.
This struct can be casted to ASS to access to the split data.
fields extracted from the [V4(+) Styles] section
ASSDialog * ff_ass_split_dialog2(ASSSplitContext *ctx, const char *buf)
Split one ASS Dialogue line from a string buffer.
int underline
whether text is underlined (1) or not (0)
char * text
actual text which will be displayed as a subtitle, can include style override control codes (see ff_a...
char * name
name of the tyle (case sensitive)
int italic
whether text is italic (1) or not (0)
char * collisions
how subtitles are moved to prevent collisions
void ff_ass_free_dialog(ASSDialog **dialogp)
Free a dialogue obtained from ff_ass_split_dialog2().
int back_color
color of the subtitle outline or shadow
int styles_count
number of ASSStyle in the styles array
int dialogs_count
number of ASSDialog in the dialogs array
typedef void(RENAME(mix_any_func_type))
int outline_color
color for outline in ASS, called tertiary in SSA
fields extracted from the [Events] section
static const int16_t alpha[]
void(* alignment)(void *priv, int alignment)
int layer
higher numbered layers are drawn over lower numbered
int bold
whether text is bold (1) or not (0)
void(* text)(void *priv, const char *text, int len)
ASSScriptInfo script_info
general information about the SSA script