f0detection.m
Go to the documentation of this file.
1 function f0 = f0detection(mX, fs, ploc, pmag, ef0max, minf0, maxf0)
2 % Fundamental frequency detection function
3 % mX: magnitude spectrum, fs: sampling rate, ploc, pmag: peak loc and mag,
4 % ef0max: maximim error allowed, minf0: minimum f0, maxf0: maximum f0
5 % f0: fundamental frequency detected
6 N = length(mX)*2; % size of complex spectrum
7 nPeaks = length(ploc); % number of peaks
8 f0 = 0; % initialize output
9 if(nPeaks>3) % at least 3 peaks in spectrum for trying to find f0
10  nf0peaks = min(50,nPeaks); % use a maximum of 50 peaks
11  [f0,f0error] = TWM(ploc(1:nf0peaks),pmag(1:nf0peaks),N,fs,minf0,maxf0);
12  if (f0>0 && f0error>ef0max) % limit the possible error by ethreshold
13  f0 = 0;
14  end
15 end;
size
int size
Definition: twinvq_data.h:11127
ef0max
function ef0max
Definition: f0detection.m:1
in
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
ploc
function ploc
Definition: f0detection.m:1
mX
FFT of current buffer mX
Definition: stft_peak.m:23
possible
the buffer and buffer reference mechanism is intended to as much as possible
Definition: filter_design.txt:45
N
#define N
Definition: vf_pp7.c:200
magnitude
Plot spectral magnitude
Definition: FFT of a Simple Sinusoid.m:26
spectrum
phase spectrum(unwrapped) ploc
minf0
function minf0
Definition: f0detection.m:1
peaks
use a maximum of peaks[f0, f0error]
Definition: f0detection.m:11
peak
clear max peak[Mmag2, Mloc2]
Definition: extra/TWM.m:16
f0error
pmag f0error
Definition: extra/TWM.m:2
maxf0
function maxf0
Definition: f0detection.m:1
a
float a
Definition: avf_showspectrum.c:88
fs
function fs
Definition: f0detection.m:1
pmag
function pmag
Definition: f0detection.m:1
mag
mag
Definition: lab5.m:14
loc
generate all sine spectral lobes loc
Definition: extra/genspecsines.m:8
f0
function f0
Definition: f0detection.m:1
to
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
nPeaks
size of complex spectrum nPeaks
Definition: f0detection.m:7
output
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
length
const char int length
Definition: avisynth_c.h:668
end
end end
Definition: f0detection.m:15
min
float min
Definition: vorbis_enc_data.h:456
Generated on Tue May 7 2024 06:51:46 for FFmpeg by   doxygen 1.8.11