Go to the documentation of this file.
23 #ifndef AVDEVICE_DECKLINK_COMMON_H
24 #define AVDEVICE_DECKLINK_COMMON_H
26 #include <DeckLinkAPIVersion.h>
27 #if BLACKMAGIC_DECKLINK_API_VERSION < 0x0b000000
28 #define IID_IDeckLinkProfileAttributes IID_IDeckLinkAttributes
29 #define IDeckLinkProfileAttributes IDeckLinkAttributes
35 #include "libklvanc/vanc.h"
39 #define DECKLINK_BOOL BOOL
41 #define DECKLINK_BOOL bool
48 int l = WideCharToMultiByte(CP_UTF8, 0,
w, -1, 0, 0, 0, 0);
51 WideCharToMultiByte(CP_UTF8, 0,
w, -1,
s, l, 0, 0);
54 #define DECKLINK_STR OLECHAR *
55 #define DECKLINK_STRDUP dup_wchar_to_utf8
56 #define DECKLINK_FREE(s) SysFreeString(s)
57 #elif defined(__APPLE__)
58 static char *dup_cfstring_to_utf8(CFStringRef
w)
61 CFStringGetCString(
w,
s, 255, kCFStringEncodingUTF8);
64 #define DECKLINK_STR const __CFString *
65 #define DECKLINK_STRDUP dup_cfstring_to_utf8
66 #define DECKLINK_FREE(s) CFRelease(s)
68 #define DECKLINK_STR const char *
69 #define DECKLINK_STRDUP av_strdup
71 #define DECKLINK_FREE(s) free((void *) s)
93 IDeckLinkConfiguration *
cfg;
146 struct klvanc_context_s *vanc_ctx;
157 #if BLACKMAGIC_DECKLINK_API_VERSION < 0x0a040000
162 IDeckLinkIterator *CreateDeckLinkIteratorInstance(
void);
168 (BMDAudioConnection)0,
169 bmdAudioConnectionEmbedded,
170 bmdAudioConnectionAESEBU,
171 bmdAudioConnectionAnalog,
172 bmdAudioConnectionAnalogXLR,
173 bmdAudioConnectionAnalogRCA,
174 bmdAudioConnectionMicrophone,
178 (BMDVideoConnection)0,
179 bmdVideoConnectionSDI,
180 bmdVideoConnectionHDMI,
181 bmdVideoConnectionOpticalSDI,
182 bmdVideoConnectionComponent,
183 bmdVideoConnectionComposite,
184 bmdVideoConnectionSVideo,
188 (BMDTimecodeFormat)0,
189 bmdTimecodeRP188VITC1,
190 bmdTimecodeRP188VITC2,
194 bmdTimecodeVITCField2,
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
int frames_buffer_available_spots
DecklinkPtsSource audio_pts_source
IDeckLinkProfileAttributes * attr
int ff_decklink_set_configs(AVFormatContext *avctx, decklink_direction_t direction)
decklink_output_callback * output_callback
static const BMDVideoConnection decklink_video_connection_map[]
static const BMDAudioConnection decklink_audio_connection_map[]
void ff_decklink_list_devices_legacy(AVFormatContext *avctx, int show_inputs, int show_outputs)
int ff_decklink_list_devices(AVFormatContext *avctx, struct AVDeviceInfoList *device_list, int show_inputs, int show_outputs)
static const BMDTimecodeFormat decklink_timecode_format_map[]
IDeckLinkConfiguration * cfg
DecklinkPtsSource video_pts_source
static char * dup_wchar_to_utf8(wchar_t *w)
uint32_t buffercount_type
int ff_decklink_list_formats(AVFormatContext *avctx, decklink_direction_t direction=DIRECTION_OUT)
int ff_decklink_init_device(AVFormatContext *avctx, const char *name)
int ff_decklink_set_format(AVFormatContext *avctx, int width, int height, int tb_num, int tb_den, enum AVFieldOrder field_order, decklink_direction_t direction=DIRECTION_OUT)
#define IDeckLinkProfileAttributes
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 ug o o w
BMDAudioConnection audio_input
uint16_t cdp_sequence_num
char * av_strdup(const char *s)
Duplicate a string.
void ff_decklink_cleanup(AVFormatContext *avctx)
BMDVideoConnection video_input
BMDTimecodeFormat tc_format
BMDPixelFormat raw_format