|
FFmpeg
|
Go to the source code of this file.
Functions | |
| x | length () |
| overlap indexes | sw (ovidx) |
Variables | |
| function [y, yh, ys] | |
| analysis window size | Ns = 1024 |
| FFT size for synthesis | H = 256 |
| hop size for analysis and synthesis | N2 = N/2+1 |
| length of input sound array | hNs = Ns/2 |
| half synthesis window size | hM = (M-1)/2 |
| half analysis window size | pin |
| last sample to start a frame | fftbuffer = zeros(N,1) |
| initialize buffer for FFT | yh = zeros(soundlength+Ns/2,1) |
| output sine component | ys = zeros(soundlength+Ns/2,1) |
| output residual component | w = w/sum(w) |
| normalize analysis window | sw = zeros(Ns,1) |
| ow = triang(2*H-1) | |
| overlapping window | ovidx = Ns/2+1-H+1:Ns/2+H |
| bh = blackmanharris(Ns) | |
| normalize synthesis window | wr = bh |
| sws = H*hanning(Ns)/2 | |
| synthesis window for stochastic | lastysloc = zeros(maxnS,1) |
| initialize synthesis harmonic locations | ysphase = 2*pi*rand(maxnS,1) |
| initialize synthesis harmonic phases | fridx = 0 |
Function Documentation
|
virtual |
| overlap indexes sw | ( | ovidx | ) |
Variable Documentation
Definition at line 25 of file spsmodel.m.
Definition at line 32 of file spsmodel.m.
Initial value:
% maxnS: maximum number of sinusoids,
About Git write you should know how to use GIT properly Luckily Git comes with excellent documentation git help man git shows you the available git< command > help man git< command > shows information about the subcommand< command > The most comprehensive manual is the website Git Reference visit they are quite exhaustive You do not need a special username or password All you need is to provide a ssh public key to the Git server admin What follows now is a basic introduction to Git and some FFmpeg specific guidelines Read it at least if you are granted commit privileges to the FFmpeg project you are expected to be familiar with these rules I if not You can get git from etc no matter how small Every one of them has been saved from looking like a fool by this many times It s very easy for stray debug output or cosmetic modifications to slip in
Definition: git-howto.txt:5
FFT size for synthesis(even) H
these buffered frames must be flushed immediately if a new input produces new the filter must not call request_frame to get more It must just process the frame or queue it The task of requesting more frames is left to the filter s request_frame method or the application If a filter has several the filter must be ready for frames arriving randomly on any input any filter with several inputs will most likely require some kind of queuing mechanism It is perfectly acceptable to have a limited queue and to drop frames when the inputs are too unbalanced request_frame This method is called when a frame is wanted on an output For an input
Definition: filter_design.txt:216
phase spectrum(unwrapped) ploc
overlapping window(triangular window to avoid too much overlapping) ovidx
sound(x3, Fs)
these buffered frames must be flushed immediately if a new input produces new output(Example:frame rate-doubling filter:filter_frame must(1) flush the second copy of the previous frame, if it is still there,(2) push the first copy of the incoming frame,(3) keep the second copy for later.) If the input frame is not enough to produce output
x length()
Definition at line 1 of file spsmodel.m.
Definition at line 10 of file spsmodel.m.
Definition at line 30 of file spsmodel.m.
Definition at line 9 of file spsmodel.m.
| ow = triang(2*H-1) |
Definition at line 22 of file spsmodel.m.
Initial value:
if max(w)>1 w=0.9 *w/max(w)
overlapping window(triangular window to avoid too much overlapping) ovidx
sound(x3, Fs)
FFmpeg Automated Testing Environment ************************************Table of Contents *****************FFmpeg Automated Testing Environment Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server 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 FATE makefile targets and variables *************************************Makefile can be set to
Definition: fate.txt:142
Definition at line 15 of file spsmodel.m.
Definition at line 21 of file spsmodel.m.
Definition at line 29 of file spsmodel.m.
| output residual component w = w/sum(w) |
Definition at line 20 of file spsmodel.m.
Definition at line 27 of file spsmodel.m.
| initialize buffer for FFT yh = zeros(soundlength+Ns/2,1) |
Definition at line 18 of file spsmodel.m.
| output sine component ys = zeros(soundlength+Ns/2,1) |
Definition at line 19 of file spsmodel.m.
Definition at line 31 of file spsmodel.m.
Generated on Wed May 8 2024 06:52:20 for FFmpeg by
1.8.11